It seems that the SWISH notebook application (https://swish.swi-prolog.org/) is down. I used it in my previous semester course. Now as I see it be down, I am at a loss. Kindly help
The site is up for me.
Thanks. But somehow its not up for me.
Do you get a timeout or something else?
What do you get at http://eculture3.labs.vu.nl
Thanks for the response.
The SWISH page shows ‘connection timeout’.
http://eculture3.labs.vu.nl shows ‘connection was reset’
Can you ping SWISH? I get around 101ms from here (near New York, USA)
It shows ‘ping request could not find host SWISH’
Sorry, I should have suggested “ping swish.swi-prolog.org”
I suggested that because the ‘connection timeout’ and ‘connection was reset’ indicates that Nginx is timing out and i wanted to see if you had a slow internet connection to SWISH. Maybe @jan has an idea.
I’m afraid not. The server is up and running. All works just fine. All I can imagine is that something in the middle is blocking traffic either to this destination or from this source. Anyone else with problems?
It does seem to be specific to @plaban. Some of the Nginx ‘connection timeout’ pages seemed to say it might be a timeout between Nginx and the backend, but I cannot think of any way that would affect only one user.
I forgot to ask @plaban, have you tried another browser?
I did ‘ping swish.swi-prolog.org’. It shows request timed out. I tried with chrome and Mozilla firefox. I tried from behind a firewall (my institute network) as well as from outside firewall. Nothing seems to work.
Something between your institute network and the SWISH server is blocking traffic. You said you tried from outside the firewall. Was that still from the institute?
When I tried outside the firewall, that means I tried to access outside the institute. I also confirmed this with some of my friends outside my institute.
It is possible to install it in your machine, where you can access with http://localhost.
I tried both on Win10 or Linux, however I had to be a little ‘creative’, the official instructions don’t work for my use cases. IIRC, the main problem is that we have to use https://www.swi-prolog.org/download/swish/swish-node-modules.zip (note https://). Also, I don’t use yarn, but npm… anyway, those are optional.
Still, it looks like some firewall issue. FYI, I dumped a traceroute from our US backend for www.swi-prolog.org in Oregon. That could help people knowledgeable in network issues to figure out who is blocking traffic. From 18 it enters the Dutch network.
> traceroute swish.swi-prolog.org
traceroute to swish.swi-prolog.org (130.37.193.11), 30 hops max, 60 byte packets
1 corv-car1-gw.nero.net (140.211.15.1) 0.322 ms 0.300 ms 0.286 ms
2 corv-p1-gw.nero.net (207.98.64.18) 2.499 ms 2.579 ms 2.570 ms
3 ptck-p1-gw.nero.net (207.98.64.212) 2.860 ms 2.849 ms 2.896 ms
4 ptck-pe1-gw.nero.net (207.98.64.78) 2.378 ms 2.378 ms 2.342 ms
5 ptck-pe1-gw.nero.net (199.165.177.4) 2.409 ms 2.392 ms 2.383 ms
6 hundredge-0-0-0-24.701.core1.port.net.internet2.edu (198.71.45.218) 6.845 ms 6.175 ms 6.219 ms
7 fourhundredge-0-0-0-1.4079.core2.seat.net.internet2.edu (163.253.1.231) 75.847 ms 75.278 ms 75.283 ms
8 fourhundredge-0-0-0-16.4079.core1.seat.net.internet2.edu (163.253.2.54) 76.285 ms 76.271 ms fourhundredge-0-0-0-17.4079.core1.seat.net.internet2.edu (163.253.2.52) 74.617 ms
9 fourhundredge-0-0-0-0.4079.core1.salt.net.internet2.edu (163.253.1.156) 76.018 ms 76.003 ms 76.054 ms
10 fourhundredge-0-0-0-22.4079.core2.salt.net.internet2.edu (163.253.1.31) 74.412 ms fourhundredge-0-0-0-23.4079.core2.salt.net.internet2.edu (163.253.1.33) 74.378 ms 74.384 ms
11 fourhundredge-0-0-0-0.4079.core2.denv.net.internet2.edu (163.253.1.168) 75.043 ms 74.495 ms 74.377 ms
12 fourhundredge-0-0-0-0.4079.core2.kans.net.internet2.edu (163.253.1.251) 74.824 ms 76.006 ms 74.703 ms
13 fourhundredge-0-0-0-0.4079.core1.chic.net.internet2.edu (163.253.2.28) 76.471 ms 74.882 ms 74.857 ms
14 fourhundredge-0-0-0-0.4079.core1.eqch.net.internet2.edu (163.253.1.207) 76.272 ms 76.267 ms 76.274 ms
15 fourhundredge-0-0-0-0.4079.core1.clev.net.internet2.edu (163.253.1.210) 75.514 ms 75.456 ms 75.532 ms
16 fourhundredge-0-0-0-3.4079.core1.ashb.net.internet2.edu (163.253.1.122) 74.178 ms 77.106 ms 77.074 ms
17 fourhundredge-0-0-0-1.4079.core1.newy32aoa.net.internet2.edu (163.253.1.117) 75.422 ms 75.427 ms 75.950 ms
18 e1-3-2-502.asd001b-jnx-06.surf.net (145.145.166.18) 162.731 ms 162.501 ms 162.461 ms
19 ae28.asd001b-jnx-01.surf.net (145.145.176.144) 164.875 ms 163.383 ms 162.883 ms
20 e2-2-2-0.asd003a-jnx-01.surf.net (145.145.20.57) 163.105 ms 163.017 ms 162.920 ms
21 vu-router.customer.surf.net (145.145.20.58) 162.910 ms 162.988 ms 162.889 ms
22 130.37.6.94 (130.37.6.94) 162.618 ms 162.621 ms 162.587 ms
23 130.37.6.98 (130.37.6.98) 163.092 ms 163.102 ms 163.020 ms
24 router-routers.labs.vu.nl (130.37.14.1) 162.695 ms 162.808 ms 162.684 ms
25 colossus.labs.vu.nl (130.37.14.2) 163.138 ms 164.686 ms 165.504 ms
26 eculture3.labs.vu.nl (130.37.193.11) 162.897 ms 162.896 ms 162.773 ms
1 Like