I get ERR_CONNECTION_TIMED_OUT
My android phone can't connect too.
My ip is 95.165.148.251

tracert www.gpugrid.net

Трассировка маршрута к www.gpugrid.net [84.89.134.145]
с максимальным числом прыжков 30:

1 * * * Превышен интервал ожидания для запроса.
2 4 ms 3 ms 19 ms 95-165-128-1.static.spd-mgts.ru [95.165.128.1]
3 3 ms 3 ms 3 ms mpts-ss-51.msk.mts-internet.net [212.188.1.6]
4 * 5 ms 5 ms mag9-cr03-be12.51.msk.mts-internet.net [212.188.1.5]
5 5 ms 5 ms * mag9-cr02-be13.77.msk.mts-internet.net [195.34.53.206]
6 17 ms * 16 ms oct-cr01-be1.178.spb.mts-internet.net [195.34.59.145]
7 27 ms 29 ms 28 ms kivi-cr02-ae8.78.hel.mts-internet.net [212.188.54.2]
8 27 ms 27 ms 27 ms bro-cr01-be7.135.stk.mts-internet.net [195.34.50.146]
9 27 ms 27 ms 27 ms bro-cr02-ae1.468.stk.mts-internet.net [212.188.1.82]
10 41 ms 28 ms 29 ms se-sthb.nordu.net [194.68.128.24]
11 36 ms 36 ms 35 ms dk-ore.nordu.net [109.105.97.130]
12 44 ms 38 ms 38 ms dk-bal2.nordu.net [109.105.97.249]
13 43 ms 42 ms 42 ms dk-esbj.nordu.net [109.105.97.3]
14 47 ms 47 ms 47 ms nl-ams.nordu.net [109.105.97.75]
15 52 ms 50 ms 52 ms uk-hex.nordu.net [109.105.102.97]
16 56 ms 57 ms 56 ms ndn-gw.mx1.lon.uk.geant.net [109.105.102.98]
17 * * * Превышен интервал ожидания для запроса.
18 * * * Превышен интервал ожидания для запроса.
19 * * * Превышен интервал ожидания для запроса.
20 79 ms 68 ms 67 ms ae1.mx1.mar.fr.geant.net [62.40.98.72]
21 81 ms 81 ms 84 ms rediris-ias-rediris-gw.mar.fr.geant.net [83.97.88.130]
22 90 ms 90 ms 90 ms anella-router.red.rediris.es [130.206.214.98]
23 * * * Превышен интервал ожидания для запроса.
24 * * * Превышен интервал ожидания для запроса.
25 * * * Превышен интервал ожидания для запроса.
26 * * * Превышен интервал ожидания для запроса.
27 * * * Превышен интервал ожидания для запроса.
28 * * * Превышен интервал ожидания для запроса.
29 * * * Превышен интервал ожидания для запроса.
30 * * * Превышен интервал ожидания для запроса.

You were able to post to the forum so you were connecting to gpugrid.net to do that. There might be a regional issue that could be causing it. Not sure if there was a brief outage on GPUGRID when you were trying.

If you are running a tracert you should be getting to grosso.upf.edu at the end.
Don't worry too much about the Request timed out messages. Here is a sample of mine from the US. It did take about 175ms to get there.

C:\Users\chamberj>tracert www.gpugrid.net

Tracing route to www.gpugrid.net [84.89.134.145]
over a maximum of 30 hops:

1 5 ms 3 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 10 ms 8 ms static-50-53-112-1.bvtn.or.ptr.ziplyfiber.com [50.53.112.1]
3 7 ms 9 ms 9 ms xe-0-3-2---0.car01.bvtn.or.nwestnet.net [50.46.177.0]
4 13 ms 8 ms 7 ms ae2---0.cor01.bvtn.or.nwestnet.net [50.46.176.0]
5 9 ms 10 ms 7 ms ae0---0.cor02.bvtn.or.nwestnet.net [50.46.176.5]
6 11 ms 10 ms 8 ms cr2-bvtnorxb-a-be100.bb.as20055.net [204.194.220.5]
7 11 ms 8 ms 7 ms cr2-hlboorxh-a-be-10.bb.as20055.net [137.83.80.241]
8 15 ms 11 ms 10 ms cr2-hlboorxh-b-be-10.bb.as20055.net [137.83.80.243]
9 11 ms 8 ms 11 ms cr2-hlboornf-be-13.bb.as20055.net [107.191.236.115]
10 10 ms 10 ms 11 ms cr2-ptldorpb-b-be12.bb.as20055.net [107.191.236.22]
11 14 ms 13 ms 12 ms hu0-7-0-0.ccr21.pdx01.atlas.cogentco.com [38.104.105.145]
12 13 ms 13 ms 57 ms be2670.ccr22.sea02.atlas.cogentco.com [154.54.42.149]
13 33 ms 35 ms 32 ms be3284.ccr21.slc01.atlas.cogentco.com [154.54.44.74]
14 42 ms 44 ms 43 ms be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
15 57 ms 56 ms 58 ms be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
16 66 ms 67 ms 132 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
17 75 ms 75 ms 76 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
18 84 ms 84 ms 85 ms be2891.ccr41.dca01.atlas.cogentco.com [154.54.82.250]
19 155 ms 156 ms 155 ms be2331.ccr31.bio02.atlas.cogentco.com [154.54.85.242]
20 161 ms 167 ms 195 ms be2324.ccr31.mad05.atlas.cogentco.com [154.54.61.130]
21 157 ms 160 ms 158 ms be2470.rcr51.b015537-1.mad05.atlas.cogentco.com [130.117.0.206]
22 167 ms 166 ms 164 ms 149.14.242.226
23 168 ms 169 ms 165 ms ciemat.rt2.ae1-0.telmad.rt4.mad.red.rediris.es [130.206.245.2]
24 176 ms 178 ms 172 ms anella-router.red.rediris.es [130.206.214.98]
25 * * * Request timed out.
26 173 ms 172 ms 173 ms 84.89.159.147
27 * * * Request timed out.
28 * * * Request timed out.
29 175 ms 174 ms 174 ms grosso.upf.edu [84.89.134.145]

Trace complete.

I was also able to ping your IP and lookup your name so that looks good from here.

C:\Users\chamberj>ping 95.165.148.251

Pinging 95.165.148.251 with 32 bytes of data:
Reply from 95.165.148.251: bytes=32 time=194ms TTL=100
Reply from 95.165.148.251: bytes=32 time=196ms TTL=100
Reply from 95.165.148.251: bytes=32 time=192ms TTL=100
Reply from 95.165.148.251: bytes=32 time=195ms TTL=100

Ping statistics for 95.165.148.251:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 196ms, Average = 194ms

C:\Users\chamberj>nslookup 95.165.148.251
Server: resolver.hpecorp.net
Address: 16.110.135.51

Name: 95-165-148-251.static.spd-mgts.ru
Address: 95.165.148.251


C:\Users\chamberj>

FYI it's probably not a good idea to post your IP on forums. The guys here are cool however it is out there on the internet.

If you are still having troubles post back here. We would need a bit more info to help track down the problem.

I had to connect through proxy to do that

You can add a proxy to BOINC if you need to. It's under Options > Other options on the HTTP or SOCKS proxy tab.

I'm not real sure that is your problem though. Maybe should check a few other things first.

I was running honeygain and earnapp for some time. Maybe my ip appeared in some blacklist?

It just started working.

It just started working.

I am not working on any workunit.
There are no workunits left for distribution.

I am not working on any workunit.
There are no workunits left for distribution.

For some reason email notifications give http link

If you ask for work on a regular basis, as in use of a update script, then you can get work.

I have processed 12 beta Python for GPU tasks since yesterday, 3 in progress now in fact.

You mean like this?
cd e:\Program Files\BOINC
e:
:loop
TIMEOUT /T 5 /nobreak
boinccmd.exe --project https://www.gpugrid.net update

TIMEOUT /T 60 /nobreak
goto loop

Yep, that should work I think in Windows. Not familiar with Windows myself.
I do this in Linux.

Yep, that should work I think in Windows. Not familiar with Windows myself.
I do this in Linux.