Hi!

I've running the Boinc manager SW 5.2.13 on an XP Prof behind the company firewall.
It seems that boinc can connect to the internet (proxy adjustments where made correctly).

Nevertheless I keep getting:
"|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500"

-when trying to get new work and-

"|SETI@home|Temporarily failed upload of 02mr05ac.1007.1984.390916.1.89_2_0: error 500"

When trying to upload it seems as upload would start and then stalls when 0,28kbyte "where sent".

I have this problems for some time now and I saw no news at the seti homepage, that the server has problems so I gues that some configuration of my boinc software is screwed up.

Any suggestions?

Regards
Leo

Actually, its been an ongoing problem for a lot of people with many threads and many many posts about the problem(s). Seems there are many different problems that all give the Generic ERROR 500. Some people and systems have them, and one setting next to them using the same version of software, local network and path to Berkeley don't. Current ones are Persistant Error 500 issue / Redirects hit maximum amount and I have 3 computers - main one now can't connect and Interesting Post @ Einstein on upload failures and Mysterious error 500 still with me as recent examples. And there were a number of much longer ones.

Some of them have been traced to very old firmware levels in Linksys routers. To "Black Hole" routers in your path through the Internet to the Berkeley servers. Issues between peer ISP's. The Berkeley upload/download server being overloaded when you hit it. Problems with using SOCKS Proxy instead of HTTP Proxy. And a number of bugs in the current releases of the BOINC application that are being worked on, and changes that will at least give more meaningful error messages about which of the many different errors currently just get called ERROR 500.

Temporary fixes include Berkeley changing the network route for the scheduler server (but not the upload/download server), using proxy servers near Berkeley, updating older Linksys (home) routers, using much older 4.xx versions of BOINC, enabling Black Hole detection, adjusting MTU to a lower value, etc. while they test code changes in the BOINC Manager to see if they are going to help.

Hallo Jack!

Thanks for the reply.
I've allready read some of the articles you pointed out. I will go through the others after work.
I've upgraded to the 5.2.13 Version because the Boinc Mangaer sudenly could not connect to the client previousely. The upgrade did not help, but after starting the client manually and connecting the manager afterwards sveral times the boinc manager can now connect to the client without manual help at startup.

One interresting thing is, that upon an upload try of the results the boinc manager claims that 0,28kByte where uploaded (and than it stalls until a timeout occurs). I think that this 28x bytes are overhead data (some protocolls) and that ist stalls as soon as it comes to the real thing (or stops becaus the protocoll is crap). But if it can transmitt some protokoll that means that a working connection was established which would disqualify most of the network topics...

I will go through the other posts. I would have the posibillity to log the http traffic on the client side. But since it costs some effort I will only setup my proxy if I not what to look for.

Regards
Stephan

Also added a trace of an unsuccessfull scheduler request to the topic
http://setiathome.berkeley.edu/forum_thread.php?id=27013

(don't know how to add an link here yet)

---