I can't download new WU since the fire event.
I resetted the project, re installed BOINC and windows drivers.
Checking log I found this:
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 504 Timeout while reading response from Server

Complete log from the connection attempt:
29/08/2017 13:45:59 | SETI@home | Fetching scheduler list
29/08/2017 13:46:00 | SETI@home | [http] [ID#1] Info: Connection 61 seems to be dead!
29/08/2017 13:46:00 | SETI@home | [http] [ID#1] Info: Closing connection 61
29/08/2017 13:46:00 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Connection 62 seems to be dead!
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Closing connection 62
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Connection 60 seems to be dead!
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Closing connection 60
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Trying 208.68.240.110...
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Connected to setiathome.berkeley.edu (208.68.240.110) port 80 (#63)
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: GET / HTTP/1.1
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: Host: setiathome.berkeley.edu
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.6.33)
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: Accept: */*
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server: Accept-Language: it_IT
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Sent header to server:
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 504 Timeout while reading response from Server
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Date: Tue, 29 Aug 2017 11:45:40 GMT
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Cache-Control: no-cache
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Pragma: no-cache
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/html; charset="UTF-8"
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Content-Length: 0
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Accept-Ranges: none
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Via: HTTP/1.1 sophos.http.proxy:3128
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server: Connection: close
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Received header from server:
29/08/2017 13:47:02 | SETI@home | [http] [ID#1] Info: Closing connection 63


I have no connection problems and I can get response to ping, tracert and browser navigation.
Any hint ?

Thanks in advance,
Andrea

---

I29/08/2017 13:46:00 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Connection 62 seems to be dead!
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Closing connection 62
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Connection 60 seems to be dead!
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: Closing connection 60
29/08/2017 13:46:01 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):

The bold above says that you are trying to connect to an HTTPS address. The Seti project address for BOINC however is just HTTP, even when its forums can be reached via an HTTPS address prefix.

So check that you added Seti with http://setiathome.berkeley.edu/ and not https://setiathome.berkeley.edu/

---

Hi Ageless,
thank you for your kind reply.
I confirm I'm using HTTP:

31/08/2017 09:56:19 | SETI@home | [http] HTTP_OP::init_get(): http://setiathome.berkeley.edu/
31/08/2017 09:56:19 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
31/08/2017 09:56:19 | | [proxy] HTTP_OP::no_proxy_for_url(): http://setiathome.berkeley.edu/
31/08/2017 09:56:19 | | [proxy] returning false

Any other idea ?
Thank you

Can you post a complete cycle of what http_debug has to say on such a contact? Not just an excerpt.
Also, are you using a proxy?

---

Yes I'm on a company network so it's possibile I'm connecting throw a proxy.
Anyway, as told on my first post, I have no problems connecting to the seti server via ping, tracert or brower request. I assume it's a common http request so the proxy should not be a problem.
Here is my latest log, but it doesn't add nothing to my first post:

31/08/2017 09:30:29 | SETI@home | [http] HTTP_OP::init_get(): http://setiathome.berkeley.edu/
31/08/2017 09:30:29 | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
31/08/2017 09:30:29 | | [proxy] HTTP_OP::no_proxy_for_url(): http://setiathome.berkeley.edu/
31/08/2017 09:30:29 | | [proxy] returning false
31/08/2017 09:30:29 | SETI@home | Fetching scheduler list
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Connection 217 seems to be dead!
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Closing connection 217
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Connection 218 seems to be dead!
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Closing connection 218
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Connection 216 seems to be dead!
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: Closing connection 216
31/08/2017 09:30:29 | SETI@home | [http] [ID#1] Info: TLSv1.2 (OUT), TLS alert, Client hello (1):
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Info: Trying 208.68.240.110...
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Info: Connected to setiathome.berkeley.edu (208.68.240.110) port 80 (#219)
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: GET / HTTP/1.1
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: Host: setiathome.berkeley.edu
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.6.33)
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: Accept: */*
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server: Accept-Language: it_IT
31/08/2017 09:30:30 | SETI@home | [http] [ID#1] Sent header to server:
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 504 Timeout while reading response from Server
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Date: Thu, 31 Aug 2017 07:30:06 GMT
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Cache-Control: no-cache
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Pragma: no-cache
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Content-Type: text/html; charset="UTF-8"
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Content-Length: 0
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Accept-Ranges: none
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Via: HTTP/1.1 sophos.http.proxy:3128
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Connection: close
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server:
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Info: Closing connection 219

31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: HTTP/1.1 504 Timeout while reading response from Server
31/08/2017 09:31:31 | SETI@home | [http] [ID#1] Received header from server: Via: HTTP/1.1 sophos.http.proxy:3128

The above are the main lines, I think.
You won't be able to connect to anything using port 80, when your proxy uses a different port number. So then connections time out.

Is your BOINC set up to use the proxy?
Options->Other options...->HTTP or SOCKS Proxy
If neither of these is populated, BOINC won't connect to the server.
If either of these is populated, check the details. Especially the port number.
You may need to add information via the <proxy_info></proxy_info> tags in cc_config.xml, see https://boinc.berkeley.edu/wiki/Client_configuration#Options for that - and mind the asterisks (*) as those options are only for BOINC 7.8 and above (which is still in testing).

---

You just gave me the correct hint to track down the problem !
Here is the explanation to my problems:
https://www.sophos.com/it-it/press-office/press-releases/2006/10/application-control-distcomp.aspx

It seems that my company's network team changed policy lately ... I have no words ...
Thank you for your time and support.

Best regards,
Andrea