For about the last 12 hours, all of my computers have been having trouble contacting the project to download tasks and upload results. Most of the time, the BOINC clients have to make multiple retry attempts before they are able to successfully upload results. And as long as any of the result uploads are stuck, they also cannot download any new work. It is happening on all of my computers at two different physical locations with two different ISPs.

Also, the web site is taking a very long time to load. It just took me about five minutes to load the home page, then come here to the message boards to see if anyone else had already mentioned this problem.

Me too. I think their server is at the limit due to the short work units.
https://www.sidock.si/sidock/forum_thread.php?id=171&postid=1429#

Thank you for confirming that it's not just me. Everything was fine until last night, but I'm tired of constantly clicking the Update button on my clients just to get them to download a few tasks, so I'm switching everything over to a different project until the problem is resolved.

Hi, I am recently seeing some slow connection problem with both boinc and web browser when trying to access this website.
From my Linux, I ran this command a few times on my computer:
nmap -p 80,443 sidock.si
80/tcp http 100% open.
443/tcp https 58% filtered, 42% open, this is random chance. Looks like there something wrong with this port number. Possibly this port number is overloaded.

I have found some possible ways to reduce this problem.

For Windows 10 clients users, this TCP connection adjustments got me higher connection success chance at a cost of taking longer to timeout if it doesn't connect. Open command prompt (cmd) and try these commands.
netsh interface tcp show global
netsh interface tcp set global initialrto=300
netsh interface tcp set global maxsynretransmissions=7
Can go back to initialrto=1000 maxsynretransmissions=4 if you don't like extra long timeout for no connection.

------
For server owner or admin, this can possibly help allow more connections to work when using Apache web server.
/etc/apache2/conf-enabled/custom.conf (can make a new file)
MaxRequestWorkers 1000
ServerLimit 1000
ListenBackLog 10000

service apache2 restart

; Can stress test own web server to check speed.
ab -n 10000 -c 1000 http://127.0.0.1/

Hi folks! We plan to transfer part of the load from HDD's to SSD's.

I have noticed that when the web browser slowly and eventually loads sidock website, then the website then load very fast for the rest of the time, until you stop clicking on links and idle for more then 5 seconds. Looks like this is keep-alive connection stuff. Probably the server's limited connection limit is configured too low and/or have reached the limit. I have to reload page (F5 button), copy and paste then hit post, all in less then 5 seconds.

For BOINC clients, limit to 1 file transfer at a time does help due to 5 second keep-alive using the same connection.
cc_config.xml
<cc_config><options>
<max_file_xfers_per_project>1</max_file_xfers_per_project>
</options></cc_config>

I found sched_reply_www.sidock.si_sidock.xml in BOINC files, shows:
<request_delay>7</request_delay>
Other BOINC project servers have request_delay set to 31, 121, or 181. Too low can cause server can get overloaded more easily. Server owner/admin can raise this number to see if this helps. I still believe the problem is mostly hitting the limit of TCP web server limited connections.

hoarfrost - what is going on with your servers lately?
they go down sporadically for 18 hours at a time or something, usually the webserver is down as well so I can't even access the page to see what if any news or lack of news there is about the problem.

Maybe when you go down and take your webservers offline you can post on your unused Twitter page.

Hello Greg!

Last server maintenance was at March'14, for hour. Sometimes we perform server parameters adjusting with short (about 1 .. 5 minutes) project server shutdown. Sometimes we see a wave of load and project website can reply slow for several minutes also. If you see long-time unavailability, it's not related to project server.

Thank you for participation!

From 1141 until 1835 your project had numerous comms errors.
4/9/2022 11:41:17 AM | SiDock@home | Started upload of corona_PLpro_v3_sidock_00810349_-15_0_r1812609183_0
4/9/2022 11:41:17 AM | SiDock@home | Started upload of corona_PLpro_v3_sidock_00810349_-15_0_r1812609183_1
4/9/2022 11:41:39 AM | SiDock@home | Temporarily failed upload of corona_PLpro_v3_sidock_00810349_-15_0_r1812609183_0: connect() failed
4/9/2022 11:41:39 AM | SiDock@home | Backing off 00:02:30 on upload of corona_PLpro_v3_sidock_00810349_-15_0_r1812609183_0
4/9/2022 11:41:40 AM | | Project communication failed: attempting access to reference site
4/9/2022 11:41:42 AM | | Internet access OK - project servers may be temporarily down.
4/9/2022 11:41:50 AM | SiDock@home | Finished upload of corona_PLpro_v3_sidock_00810349_-15_0_r1812609183_1

This error repeated every hour or so until the end time reported.
None of my other projects had this problem. So its not my end.

Temporary upload problems can be, it's related to server load whole and "waves" of this load. You can ignore them.

So its not my end.

Yes. Looks like some limitations in network infrastructure. From some cities all works fine, from some - not.

Still difficult, from Italy, to upload wus...