Is it possible to return results on a regular port? (ie, 80/443/8080) My company is now restricting outbound ports and will not approve 31416.

Thanks for any info!

Steve

31416 is only used for internal (localhost) loopback communications between the 'client' and 'manager' components of the local BOINC installation.

Most projects report back on port 80, though a few (WCG is a case in point) are moving to https on 443.

31416 can also be used between local machines if a single 'aggregating' manager like BoincTasks is used to monitor multiple local machines - but that is not a default configuration, and would only apply if you set it up manually.

Ignore this - unable to delete duplicate

---

Then why am I unable to upload results to SETI? Here is a recent snip from my log:

12/15/2013 10:50:33 PM | SETI@home | Started upload of 20dc08ab.3941.7434.438086664197.12.74_1_0
12/15/2013 10:50:33 PM | SETI@home | Started upload of 08jn08aa.31795.9888.438086664201.12.123_1_0
12/15/2013 10:50:36 PM | SETI@home | Project file upload handler is missing
12/15/2013 10:50:36 PM | SETI@home | Backing off 03:42:12 on upload of 20dc08ab.3941.7434.438086664197.12.74_1_0
12/15/2013 10:50:36 PM | SETI@home | Project file upload handler is missing
12/15/2013 10:50:36 PM | SETI@home | Backing off 03:14:02 on upload of 08jn08aa.31795.9888.438086664201.12.123_1_0

I am running BOINC 7.2.33 64 bit on a Windows 7 machine.

What is the "Project file upload handler" that is mentioned?

Thanks in advance for any insights!

Steve
____________

---

Um. Not an easy question. You are aware how BOINC works - the project you've chosen sends you data, you process it, you return the answers to the project? Well, the "Project file upload handler" is the process that runs on the project's servers to receive and store the files which are returned (uploaded) by the volunteers like you. I'm not sure that there's much more that can be said about it.

SETI's lives at http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler

If you paste that into a browser address bar, you should expect to see a human-readable reply like

<data_server_reply>
    <status>1</status>
    <message>no command</message>
</data_server_reply>

When a BOINC client contacts a server, saying it has a file to upload, it should receive a fuller reply, saying if it's OK to upload or not.

BOINC will try to contact the domain address above. It will expect your local network infrastructure to resolve the domain to 208.68.240.16 - you could check whether the domain resolves correctly, and whether the IP address is reachable, over your network.

But in your opening post, you did say "My company is now restricting outbound ports". You are aware, I presume, that BOINC projects remind you of your personal responsibilities - SETI's version says:

Run SETI@home only on computers that you own, or for which you have obtained the owner's permission.

I would interpret the word 'computers' in that sentence to include servers, routers, and any other paraphenalia associated with the network. A company being cautious, for example, might think that computer files being sent outside the company to an unknown 'file upload handler' looks like a competitor attempting industrial espionage. If you are clear to go on the 'authorized computer use' question, you should consult your company's technical staff, specifically their network technicians, to see if a block is in place and if it could be modified. If you don't feel comfortable about approaching the network techs, then you probably shouldn't be running SETI in the first place.