(The article below is specifically for customers running on Lite Speed. For general information about Threadloom and timeouts, view this article.)
To avoid Lite Speed server timeouts when communicating with Threadloom, you need to make sure there is enough headroom with LSAPI_MAX_PROCESS_TIME and your connection timeout.
By default, the LSAPI_MAX_PROCESS_TIME environment variable is set to 3600 seconds, which is sufficient for Threadloom to sync your index. However, if you've set this to a low value, we recommend changing this value back to the default value of 3600 seconds. You can find this in WebAdmin CP > Configuration > Server (or Vhost) > External App > <your external application> > Environments. The value should be set as follows:
LSWS LSAPI_MAX_PROCESS_TIME = 3600
Configure Connection Timeout
If you are running Lite Speed, you can set a longer timeout in WebAdmin CP > Configuration > Server > Tuning > Connection Timeout (secs).
If you prefer to set the connection timeout specifically for Threadloom, you can either add a virtualhost directive or update your .htaccess files.
Alternate option 1: Add a virtualhost directive
Add the following HTTP and HTTPS directives to your virtualhost configuration file:
RewriteRule ^/deferred\.php - [E=noabort:1, E=noconntimeout:1]
RewriteRule ^/library/Threadloom/.* - [E=noabort:1, E=noconntimeout:1]
Alternate option 2: Update your .htaccess files
Update the .htaccess files in the following 3 locations:
/<path to forum home folder>
RewriteRule deferred.php - [E=noabort:1, E=noconntimeout:1]
/<path to forum home folder>/library/Threadloom
RewriteRule Sync.php - [E=noabort:1, E=noconntimeout:1]
/<path to forum home folder>/library/Threadloom/common
RewriteRule Syncer.php - [E=noabort:1, E=noconntimeout:1]
Note: On servers with very limited resources, it is possible that making these .htaccess changes may impact server load/capacity.