Is this on your home connection?
I didnt know seti was communicating on port 80, but often port 80 can be blocked on non allowed website if you are running it in a company or at a school etc..

does this URL works for you?

http://setiboincdata.ssl.berkeley.edu/

You should see a webserver test page

---

The strange thing is, it connects OK the first time, but times out when it tries again.

By contrast, one of mine has just uploaded: I'll show a bit of an overlap, and then how it completes.

05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server: <data_server_reply>
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server: <status>0</status>
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server: <file_size>0</file_size>
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server: </data_server_reply>
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server:
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server: 0
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Received header from server:
05/10/2018 13:53:24 | SETI@home | [http] [ID#9673] Info: Closing connection 10183
05/10/2018 13:53:24 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: Hostname setiboincdata.ssl.berkeley.edu was found in DNS cache
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: Trying 208.68.240.118...
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: Connected to setiboincdata.ssl.berkeley.edu (208.68.240.118) port 80 (#10184)
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: POST /sah_cgi/file_upload_handler HTTP/1.1
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Host: setiboincdata.ssl.berkeley.edu
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.9.2)
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Accept: */*
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Accept-Encoding: deflate, gzip
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Content-Type: application/x-www-form-urlencoded
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Accept-Language: en_GB
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Content-Length: 21150
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Expect: 100-continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server:
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: 
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Received header from server: HTTP/1.1 100 Continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: We are completely uploaded and fine
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: HTTP/1.1 200 OK
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: Date: Fri, 05 Oct 2018 12:53:14 GMT
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: Server: Apache/2.2.15 (Scientific Linux)
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: Connection: close
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: Transfer-Encoding: chunked
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: Content-Type: text/plain; charset=UTF-8
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server:
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: 40
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: <data_server_reply>
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: <status>0</status>
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: </data_server_reply>
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server:
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server: 0
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Received header from server:
05/10/2018 13:53:26 | SETI@home | [http] [ID#9673] Info: Closing connection 10184
05/10/2018 13:53:26 | SETI@home | Finished upload of blc22_2bit_guppi_58340_60369_HIP26335_0093.23543.818.20.29.211.vlar_0_r1379057043_0

You have an extra line before the timeout:

5/10/2018 9:13:09 PM | SETI@home | [http] [ID#10] Info: Found bundle for host setiboincdata.ssl.berkeley.edu: 0x376f0b0 [can pipeline]

That's strange, and I don't know what it means - I'll keep thinking about it.

You say 'home connection', which rules out corporate firewalls (thank goodness), but can you say a little bit more about how you connect to the internet - wired or wireless, DSL or cable, that sort of thing. And are you running an antivirus or internet security package? If so, which one?

Interesting.. in the log it looks like it succeeded to connect once, but timed out when opening a second connection.
Maybe there is a link between you and the server that is problematic, possibly high packet loss?

Have you tried to disable windows firewall just to test if it is working with it off?

---

I see this part is a little different:
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Expect: 100-continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server:
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: 
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Received header from server: HTTP/1.1 100 Continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: We are completely uploaded and fine

I see this part is a little different:
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: Expect: 100-continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server:
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Sent header to server: 
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Received header from server: HTTP/1.1 100 Continue
05/10/2018 13:53:25 | SETI@home | [http] [ID#9673] Info: We are completely uploaded and fine

And that's on the part which says

Content-Length: 21150

- in other words, the main file upload. NKAR gets

5/10/2018 9:13:07 PM | SETI@home | [http] [ID#10] Sent header to server: Content-Length: 334
5/10/2018 9:13:07 PM | SETI@home | [http] [ID#10] Sent header to server:
5/10/2018 9:13:07 PM | SETI@home | [http] [ID#10] Info: We are completely uploaded and fine

The very short message is perhaps some preliminary identification - file name to open, possibly? Larger files may use a different (asynchronous) protocol, though I didn't think it kicked in as low as that. There can also be packet size issues over longer, multi-hop links.

5/10/2018 9:13:09 PM | SETI@home | [http] [ID#10] Info: Found bundle for host setiboincdata.ssl.berkeley.edu: 0x376f0b0 [can pipeline]

That's strange, and I don't know what it means - I'll keep thinking about it.

It means that the server can do pipelining and isn't blacklisted. Pipelining is another word for keeping the connection alive/using the same connection as before. It's a Curl message.

---

My home internet is wired VDSL, antivirus is Avast, no other internet security packages. Like I said I've got two PCs which both have the same problem, both the PCs are almost identical except for the OS (one is Win 10 Pro, the other is Win 10 Home).

ISP & town?

I'm in Darwin with iiNet on NBN, Win10 Pro, no 3rd party AV or firewall and no network issues.

---

Grant
Darwin NT

You could use a network tool like WinMTR to do a traceroute including ping average, it will list every routers and their latency/packet loss.
But be aware that some router will show packet loss even when there is none (because they are rate limiting) If the next router on the list
has no packet loss, then it means it is rate limiting and not actual packet loss.

If there is a problem on the first few router, you could possibly call your ISP, if it is lower down the list, i am afraid you would have to wait it out..

---

I am having problems with web browsing and Seti uploads and downloads on Telstra network for the last couple of days. I have a second network using iiNet that is working fine. I’m in Sydney. Both are using ADSL. I even had browsing issues on the mobile phone which is also on Telstra.

---

BOINC blog

I am having problems with web browsing and Seti uploads and downloads on Telstra network for the last couple of days. I have a second network using iiNet that is working fine. I’m in Sydney. Both are using ADSL. I even had browsing issues on the mobile phone which is also on Telstra.

Hmm, found this site-
From aussieoutages.com

Telstra outage map
Recent reports mostly originate from: Brisbane, Melbourne, Sydney, Perth, Adelaide, Richmond, New Farm, South Yarra, Collingwood, and Concord.

---

Grant
Darwin NT

Yes I can now get to BOINC and Seti, using the Telstra connection so it looks like they've fixed whatever it was. I was able to get to GPUgrid in Spain so maybe it was their undersea cable to the states.

---

BOINC blog