Hello!

I downloaded World Community Grid client (from here: https://www.worldcommunitygrid.org/ms/viewDownloadAgain.action , I believe it is the same as a regular BOINC client), of course, it connected to World Community Grid project. WCG tasks download and are processed nicely.

Then, in the same interface, I connected to rosetta@home. So the 2 projects are 50%-50% now.

But the rosetta tasks don't download. They appear in the tasks list (some Rosetta 4.07, some Rosetta Mini 3.78), in "download" status, but remains 0% for days.

We are behind a corporate firewall. (On my home PC, rosetta tasks download perfectly with - I believe - the same settings.) Are there any special settings I need to ask for on the firewall?

Anyone could help us with this please?

Assuming you have permission to run BOINC & BOINC-based applications on what would appear to be a "company owned and managed" computer you will have to ask for the Rossetta servers to be white listed on the corporate firewall and any associated security applications that may be running. It is not unknown for firewalls to allow an "initial sniff" of data through from an "unknown" source, then to pull the drawbridge hard and fast once a lot of data is being transferred.

Thank you!

Are there any information anywhere about these servers that I should ask to be whitelisted?

---


I see such lines in stdoutdae.txt (Program Data folder):

05-Jul-2019 20:03:54 [Rosetta@home] Started download of minirosetta_database_1a38360_n_methyl.zip
05-Jul-2019 20:03:54 [Rosetta@home] Started download of minirosetta_database_d0bf94b.zip
05-Jul-2019 20:08:56 [Rosetta@home] Temporarily failed download of minirosetta_database_1a38360_n_methyl.zip: transient HTTP error
05-Jul-2019 20:08:56 [Rosetta@home] Backing off 05:29:02 on download of minirosetta_database_1a38360_n_methyl.zip
05-Jul-2019 20:08:56 [Rosetta@home] Temporarily failed download of minirosetta_database_d0bf94b.zip: transient HTTP error
05-Jul-2019 20:08:56 [Rosetta@home] Backing off 05:05:44 on download of minirosetta_database_d0bf94b.zip

You should enable the <http_debug> event log flag (Ctrl+Shift+F). That will give you the urls accessed, and the server to-and-fro leading up to the error.