| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Unable to upload |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm currently using BOINC 5.4.11 and ever since the 3rd I've been unable to upload workunits, at the time it was getting this message when it would try to upload...
"8/3/2007 10:08:38 AM||Access to reference site succeeded - project servers may be temporarily down." Later in the same day I started getting this message as well... "8/6/2007 6:58:59 PM|World Community Grid|Scheduler request failed: couldn't connect to server" (It's the exact same message, I just copied the most recent one to include in this post hence the difference in date) Nothing has changed on my end and I have noticed that it seems as if I'm pretty much the only one having this problem. Any suggestions will definitely be appreciated. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Let's ask the obvious questions:
What operating system? Have you changed, added, installed, updated or upgraded anything in the last couple of weeks? What firewall do you use? Do you use a proxy server or corporate network? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Heh sorry, forgot about the OS part, I'm using Windows XP, nothing has been changed, added, installed, updated or upgraded within the last couple of weeks, using Trend Micro PC-cillin Internet Security 2007, no proxy server or corporate network. I do use a router but I know that's not it, nothing has been updated on it and given that nothing has been updated on it then if it was the router I would've been having this problem from the moment I hooked it up.
The only thing I know of that's changed was the updates they did on the 3rd for the site but I really don't see how that could've affected my ability to upload any. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's not an upload problem - you can't reach the WCG servers at all. Usually, this is a firewall problem, so the first thing to do is check that Trend Micro aren't blocking you. WCG uses secure (SSL) communications on port 443.
The WCG website updates have nothing to do with this. It's updates on your computer that interest me (it's amazing how many people discount changes because they seem insignificant or unrelated. For example, does your security software auto-update?) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yeah it auto updates (I checked the date for the last update and it was today, thought it was only on Wednesdays but that was the spy sweeper program I used to use), I completely shut the program down and it still wouldn't connect.
Yeah I didn't think the website updates would have anything to do with it. Windows is not set to auto update either. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
FWIW an excerpt from a FAQ in the Start Here forum:
----------------------------------------Firewall related issues. For the BOINC agent make sure to allow localhost traffic (IP 127.0.0.1) over port 31416 for the 4 possible components: * BOINC.exe (The Core Client aka Daemon) I, * BOINCmgr.exe (The GUI Interface) II, * BOINC.scr (The Screensaver, if the BOINC version is used) and * BoincCmd.exe (for the few that use command line instructions) Port 80 and 443 need to be open for outward traffic to WCG for IP 129.33.89.133 and 129.33.89.134 Finally ports in the range 1038-5000 needs to be open on IP 127.0.0.1 for I / II above to be able to use a random port for internal communication thru the operating system. The function is explained in the localhost Wikipedia page. You can check what ports BOINC presently is using by opening a command window and running the 'netstat -a' instruction. That will produce a list like below. Look for any line noting port 31416. The sample shows a connection also to a second computer (in the LAN, where the BOINC manager thru the advanced menu 'Select Computer' option is looking at another client. Someone found that deleting current BOINC exceptions in the (ZA) firewall, restarting BOINC and re-applying the exceptions made things to work again. Who knows.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Aug 7, 2007 12:05:42 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Shutting the program down shouldn't stop the firewall functionality. You will have to manually create some exceptions to allow BOINC to connect.
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Actually ZA and certainly my Sunbelt PF gave warnings for anything BOINC was trying to do including that random localhost port, so determined it was always in that 1038-5000 range and set a manual exception specific to BOINC. Trend not familiar with.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
William Timbrook
Cruncher Joined: Oct 25, 2006 Post Count: 6 Status: Offline Project Badges: 
|
Thanks for answer to the unable to upload question. I had the same problem but with Kaspersky. Pausing it allowed me to upload so now I'm not as irritated by the project.
William  |
||
|
|
|