New here? Create a new account!

Any way to change the Send/Receive timeout delay?

0 votes
537 views

We’re on a very slow (satellite-based) connection with minimal outgoing bandwidth (~750kbps for 20-30 people). I’ve prioritized traffic to the Paratext Send/Receiver server (archives.paratext.org), but even when I can confirm that a connection has been made to the server, the S/R frequently times out. Is there any configuration change that can be made in Paratext to extend that timeout delay? Alternatively, is there anything the server maintainers would be willing or able to do to extend that timeout from the server side? I’m also open to other suggestions at the firewall level, but that’s a little off-topic here.

Paratext by (298 points) | 537 views

1 Answer

0 votes
Best answer

The timeout we use is 100 seconds when creating the client connection to the server and we don’t have a way to change that.

I would be interested in seeing which call to the server is timing out - please send a problem report the next time it happens.

John+Wickberg
Paratext support

by [Administrator]
(3.4k points)
reshown

Okay, thanks. I’ll see if I can get one to you tomorrow (but, of course, I’d much rather our connection work better instead!).

by (298 points)

I’m still working on getting a problem report out. It of course couldn’t be sent at the moment, because the connection wasn’t good enough. But here is some output from my computer more or less confirming that the connection is made to the Send/Receive server, but that it just goes away after about 100 seconds, which would confirm the timeout theory.

The connection was initiated at 10:55:21 and established at 10:55:32. Then it goes away when Paratext gives a server error at 10:56:44. That’s 83 sec. after the initial packet is sent and 72 sec. after the connection is established. So not quite 100 sec., but close.

ven. 07 oct. 2022 10:55:12 WAT
ven. 07 oct. 2022 10:55:13 WAT
ven. 07 oct. 2022 10:55:14 WAT
ven. 07 oct. 2022 10:55:15 WAT
ven. 07 oct. 2022 10:55:16 WAT
ven. 07 oct. 2022 10:55:17 WAT
ven. 07 oct. 2022 10:55:19 WAT
ven. 07 oct. 2022 10:55:20 WAT
ven. 07 oct. 2022 10:55:21 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:22 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:23 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:24 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:25 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:26 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:27 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:28 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:30 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:31 WAT
SYN-SENT    0       1         172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:32 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:33 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:34 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:35 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:36 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:37 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:38 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:40 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:41 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:42 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:43 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:44 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:45 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:46 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:47 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:48 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:49 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:51 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:52 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:53 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:54 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:55 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:56 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:57 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:58 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:55:59 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:01 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:02 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:03 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:04 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:05 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:06 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:07 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:08 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:09 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:11 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:12 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:13 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:14 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:15 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:16 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:17 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https         users:(("mono",pid=667138,fd=52))                                              
ven. 07 oct. 2022 10:56:18 WAT
ESTAB       0       191       172.16.1.239:36006      54.235.68.98:https
by (298 points)

Here’s the connection status later from home when it was successful. (The initial connection seen below must be the Problem report going out.) The S/R connection seems to be initiated and established at 11:37:39 and comes and goes a couple of times until 11:38:50, so the whole S/R seems to complete in 71 sec.:

ven. 07 oct. 2022 11:37:37 WAT
ESTAB       0       161752     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:37:38 WAT
ESTAB       0       221760     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:37:39 WAT
ESTAB       0       195052     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:40 WAT
ESTAB       0       178912     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:41 WAT
ESTAB       0       153832     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:42 WAT
ESTAB       0       215352     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:43 WAT
ESTAB       0       209932     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:44 WAT
ESTAB       0       197428     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:45 WAT
ESTAB       0       190380     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:46 WAT
ESTAB       0       175596     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:47 WAT
ESTAB       0       153912     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:49 WAT
ESTAB       0       135094     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:50 WAT
ESTAB       0       221760     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:51 WAT
ESTAB       0       203914     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:52 WAT
ESTAB       0       178228     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:53 WAT
ESTAB       0       160788     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:54 WAT
ESTAB       0       164739     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:55 WAT
ESTAB       0       140029     192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:56 WAT
ESTAB       0       88759      192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       0       0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:57 WAT
ESTAB       0       70719      192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ESTAB       8250    0          192.168.1.3:38192      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:37:58 WAT
ESTAB       0       38019      192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:37:59 WAT
ESTAB       0       13627      192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:00 WAT
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:02 WAT
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:03 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:04 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:05 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:06 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:07 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:08 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ESTAB       0       0          192.168.1.3:42366    54.247.124.205:https         users:(("mono",pid=691637,fd=88))                                              
ven. 07 oct. 2022 11:38:09 WAT
ESTAB      0      0             192.168.1.3:38194      54.235.68.98:https        users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:38:10 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:38:11 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:38:13 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:38:14 WAT
ESTAB       0       0          192.168.1.3:38194      54.235.68.98:https         users:(("mono",pid=691637,fd=106))                                             
ven. 07 oct. 2022 11:38:15 WAT
ven. 07 oct. 2022 11:38:16 WAT
ESTAB
by (298 points)

A send/receive for a project is made up of multiple requests to the server - the 100 second timeout will apply to each request. When we are pulling changes from the server, a single request will be limited to 20K.

I looked at the server logs and found a few sessions done by you - a couple of which were incomplete. Since all the commands on the server complete, only a client log would show where the failure is occurring.

I do see that you are using Linux, I’ll have to check to see if we can create a new release for Linux at this time. Our last Linux release was for Paratext 9.0.

John+Wickberg

by [Administrator]
(3.4k points)
reshown

In the meantime I’ve seen the same problem on multiple Windows installations at our office. I’ve had some of the users send problem reports. But lately the problem seems to have been less frequent, so I guess we’ll just wait and see if it happens more down the road.

by (298 points)

Related questions

0 votes
1 answer 456 views
Does Paratext Live, even on a local server, require access to the internet?
We have a team that has been attempting to use Paratext live on a local server and finding it difficult. They are on ... when the internet drops, or is out for a few days?
MSEAIT_LT 478 asked Nov 15, 2022
Paratext
0 votes
2 answers 401 views
The send/receive window doesn't find any projects
Hi, The send/receive window (under File - Send/receive Projects) suddenly doesn't find any projects, even the MTT ... Win 10, latest version. Any help will be appreciated Thanks
anon984740 109 asked Feb 8, 2018
Paratext
0 votes
0 answers 24 views
How does this advice change (or not) if the testing and training requires the use of Send/Receive?
Some of the testing I'm doing with users must include Send/Receive. Methods that require avoiding Send/Receive are not ... meant to include it in my original question and forgot.
Mercado 203 asked May 21, 2025
Paratext
0 votes
1 answer 311 views
Any way to fix a bad date in history (future) messing up the history display?
A colleague's computer did weird things to the date about 10 years ago as his project was getting started using ... the sort order of the history display might be worthwhile?
rowbory 510 asked May 16, 2022
Paratext
0 votes
1 answer 45 views
1-minute Send/Receive timeout is a problem on a slow connection
I've tried send/receive a few times with a test project that I'm sure has minimal if any actual changes to synchronize ... synchronize, which I often have to do as a project admin.
n8_in_car 298 asked May 12, 2025
Paratext 10
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
I appeal to you, brothers and sisters, in the name of our Lord Jesus Christ, that all of you agree with one another in what you say and that there be no divisions among you, but that you be perfectly united in mind and thought.
1 Corinthians 1:10

Categories

3,046 questions
6,006 answers
5,671 comments
2,027 users