Can't connect to http://holometer.fnal.gov/
Asherehsa opened this issue · 8 comments
Hey all,
Just testing out the app and for some reason it wouldn't let me connect to http://holometer.fnal.gov/ not sure why (maybe you just can't access it for some reason) but thought I'd report it!
I am not able to ping that IP using the desktop client either. Some networks block MTU discovery, and sometimes can't be reached over a VPN, but that is increasingly rare. Do you know if you can reach that host over other VPNs?
I can reproduce the bug.
I pinged and surfed that site using desktop client, a few seconds ago, but now the site is not responding.
hahaha
I just loaded the site from my phone using bitmask android and lucid browser.
I can't reproduce this bug. @Asherehsa do you?
I don't have another vpn to try but still can't access the site via the ubuntu or android bitmask clients. Here is a traceroute, if it helps:
traceroute to 131.225.105.231 (131.225.105.231), 30 hops max, 60 byte packets
1 10.42.0.1 (10.42.0.1) 63.214 ms 63.204 ms 63.324 ms
2 wren.riseup.net (198.252.153.1) 63.530 ms 63.727 ms 63.915 ms
3 gi1-5.mag01.sea02.atlas.cogentco.com (38.104.127.1) 64.106 ms 64.834 ms 64.952 ms
4 te0-0-0-5.ccr21.sea02.atlas.cogentco.com (154.54.41.210) 65.489 ms 65.608 ms te0-7-0-5.ccr21.sea02.atlas.cogentco.com (154.54.41.214) 65.812 ms
5 level3.sea02.atlas.cogentco.com (154.54.12.14) 64.202 ms 65.214 ms 65.062 ms
6 * ae-12-51.car2.Chicago2.Level3.net (4.69.138.133) 108.236 ms 108.872 ms
7 ae-12-51.car2.Chicago2.Level3.net (4.69.138.133) 105.721 ms 105.715 ms 106.885 ms
8 * * *
9 starcr5-ip-a-chiccr5.es.net (134.55.42.42) 107.009 ms 107.565 ms 107.646 ms
10 fnalmr2-ip-b-starcr5.es.net (134.55.220.5) 110.785 ms 115.727 ms 115.186 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I think the the problem is not the VPN. I am able to grab the website if I switch gateways. It appears that the network in question is blocking traffic from the seattle nodes for both demo.bitmask.net and riseup.net vpn providers.
it might be that the problem is cogent, the upstream provider for the servers in seattle.
regardless of what the problem is, i am confident it does not relate to MTU or any problem with the client application, so I am going to close this issue. Obviously, there still is a problem, but I don't think it is one we have any control over.