We now have two threads at the help desk with what are seeming to me to be Identical. Both can tracert both servers at berkeley successfully but can't attach. Firewall are OFF in both. both have tried several boinc versions, including the latest. I am "assuming" it to be a port issue, but I'm not good with ports.
neither can attach to seti

One thread is Boinc connection error 182, the other is Help me Please......

help please

Not my speciality unfortunatly although all these Q&A's are helping me get a better understanding of ports/proxies etc

---

Join us in Chat (see the forum) Click the Sig


Join UBT

Tony

In the thread 'Help me please...' I mentioned that the person should download the freeware program - TcpView available at Sysinternals that he could use.

Have them save the info to disk and then copy and paste to msg board. It might help to diagnose the problem.

THere is another thread with the same issue, I wrote an email to Rom, asking for help with these three.

THere is another thread with the same issue, I wrote an email to Rom, asking for help with these three.

Tony
Do they have the SSL port open too as this is needed now for authentication.

---

ssl port?

see why I"m asking for assistance???

tony

If someone could figure out one of these, we could probably fix the others.

ssl port?

see why I"m asking for assistance???

tony

Tony
Google says its 443

[edit] ssl = Secure Sockets Layer [/edit]

---

Tigher or someone with access to available proxies sites, can you go here and recommnend a proxy site for this guy to try?

ssl port?

see why I"m asking for assistance???

tony

Its port 443 used for secure transmissions (SSL= Secure Socket Layer = encryption). Used for authentication now since 5.x.x I recall from the _dev mails. So add it to 80, 1043 the 31416 or7 cant remember. As for helping Tony doubt I can because [editor]....................................................[/editor] so I can only help in emergencies I guess. That's why I have been missing these last 5/6 weeks.
Cheers

---

Tigher or someone with access to available proxies sites, can you go here and recommnend a proxy site for this guy to try?

Tony
I posted my proxy page with all the links to addresses to help him. Hope it works for him.

---

We now have two threads at the help desk with what are seeming to me to be Identical. Both can tracert both servers at berkeley successfully but can't attach. Firewall are OFF in both. both have tried several boinc versions, including the latest. I am "assuming" it to be a port issue, but I'm not good with ports.
neither can attach to seti

One thread is Boinc connection error 182, the other is Help me Please......

help please

Tony,

My first question is: can he "browse" to http://setiboinc.ssl.berkeley.edu/ and/or http://setiboincdata.ssl.berkeley.edu/?

These should get "403 Forbidden" errors, but it means that he or she can reach the servers themselves.

Ports aren't magical. It seems to me that they've also been covered reasonably well in this thread.

-- Ned

---

Ned, at this point there are 4 affected users. All have firewall off, all can ping and traceroute both servers. One stated that ports 443, 80, 1043, and 31416 were open both ways. and still couldn't attach.

This is in the mesage log of all:

27/11/2005 21:41:45||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php
27/11/2005 21:41:47||Missing account key
27/11/2005 21:42:03|http://setiathome.berkeley.edu/|Master file download succeeded
27/11/2005 21:42:04|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
27/11/2005 21:42:04|http://setiathome.berkeley.edu/|Reason: Requested by user
27/11/2005 21:42:04|http://setiathome.berkeley.edu/|Requesting 8640 seconds of new work
27/11/2005 21:44:51|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
27/11/2005 21:44:51|http://setiathome.berkeley.edu/|No schedulers responded
27/11/2005 21:44:51|http://setiathome.berkeley.edu/|Couldn't connect to URL http://setiathome.berkeley.edu/.Please check URL.
27/11/2005 21:44:51|http://setiathome.berkeley.edu/|Resetting project
27/11/2005 21:44:51||request_reschedule_cpus: exit_tasks
27/11/2005 21:44:51|http://setiathome.berkeley.edu/|Detaching from project

I'm starting to wonder about the HTTPS vs http stuff.

I've emailed both Rom Walton and Dr Anderson an provided info and links to these threads

tony

I'm starting to wonder about the HTTPS vs http stuff.

Aha... I was wondering about that as well: The Wiki describes: "BOINC (Boinc.exe) needs to open an inbound connection to either 1043 or 31416, and an outbound connection to port 80 for downloads and uploads of workunits, results, and science packages, and an outbound connection on port 443 during the attach process to a project."

I know John Keck said it is used to attach to or access a secure server. Is the Seti server recognized as a secure server? So shouldn't the connect to then happen with the HTTPS marker instead of the HTTP ?

---

I'm starting to wonder about the HTTPS vs http stuff.

Aha... I was wondering about that as well: The Wiki describes: "BOINC (Boinc.exe) needs to open an inbound connection to either 1043 or 31416, and an outbound connection to port 80 for downloads and uploads of workunits, results, and science packages, and an outbound connection on port 443 during the attach process to a project."

I know John Keck said it is used to attach to or access a secure server. Is the Seti server recognized as a secure server? So shouldn't the connect to then happen with the HTTPS marker instead of the HTTP ?

By convention, web servers are on port 80, but it is entirely possible to override the port and run HTTP on any other port number.

Same is true for HTTPS (SSL) -- it is generally on port 443, but can be done on a non-standard port.

BOINC may be using 443 because many companies allow port 443 through their firewalls.

So, it can be port 443 and not run SSL or TLS.

Don't get me started on the "secure server" question -- It isn't about security, it's about identity. ... and for another time.

---

Ned, at this point there are 4 affected users. All have firewall off, all can ping and traceroute both servers. One stated that ports 443, 80, 1043, and 31416 were open both ways. and still couldn't attach.

This is in the mesage log of all:

(snip)

27/11/2005 21:41:47||Missing account key

The line above seems to say that there is something wrong with their sign-in.

27/11/2005 21:42:03|http://setiathome.berkeley.edu/|Master file download succeeded

... and this says that they can connect to the SETI servers.

Sounds like connectivity (and firewall, etc) is not the issue -- it's in their sign on procedure.

-- Ned

---

BOINC uses https on port 443 when it needs to send the password back to the server. Since https does do encryption of the payload, it is much more secure than http that does not do any encryption of the payload.

---

BOINC WIKI

Bump.

Users with the '500-problem' begin to heap up...

:-)= Greybeard

---

All about BOINC: BOINC-Wiki (by Paul D. Buck)

Bump.

Users with the '500-problem' begin to heap up...

:-)= Greybeard

The log example given earlier says "missing account key" so we need to start looking at that as a possible reason.

I guess I could load up BOINC on a test machine and do a clean install/sign-up, but I'm not sure I'm going to do the same steps. Worth a try, though.

---

I don't think the missing key message is a problem. Everytime we start a new version of boinc, or restart, it checks for a key. That's just a message saying "I haven't found a key". I think that happens because it hasn't yet communicted with the local client and exchanged keys (on a secure path). I.E It's NOT attached just yet. I've seen that missing key message many times when I did a "Virgin" install.