Re: [NTG-context] contextbeta moved or server down? SOLVED

On Sat, Sep 08, 2018 at 03:32:47PM +0200, Michael Hallgren wrote: > Usually port 22, since rsync is usually run in ssh when between distant hosts. It’s actually pretty common for port 22 to be blocked, many free wifi providers do so. In Hans’ case, since he can change the configuration I don’t

Re: [NTG-context] contextbeta moved or server down? SOLVED

Usually port 22, since rsync is usually run in ssh when between distant hosts. Cheers, mh Le 8 sept. 2018 à 15:19, à 15:19, Hans van der Meer a écrit: >I am not inclined to react so strongly. In general I am happy when the >ISP provides its customers with default save settings. It is best for

Re: [NTG-context] contextbeta moved or server down? SOLVED

I am not inclined to react so strongly. In general I am happy when the ISP provides its customers with default save settings. It is best for most people, I think. Perhaps the rsync port 873 should have been opened by default in the firewall, because I suspect more and more people will use it

Re: [NTG-context] contextbeta moved or server down? SOLVED

Hi Hans, I think that this is a scandal, as it is nothing else but censorship by your ISP. I am a member of a cooperative hoster in Germany (Hostsharing) and Telekom, the biggest German ISP, blocked our mail servers for years in their routers they bundle with internet access services. We had to

Re: [NTG-context] contextbeta moved or server down? SOLVED

This caused a lot of headaches but was finally solved this morning. Brainwave (and a nights sleep) needed to find the cause and it was so simple! The case being that between my last successful access of the garden and yesterday the firewall protection of my modem had gone up to the highest

Re: [NTG-context] contextbeta moved or server down?

telnet is not present here on the system (for safety I presume) > On 7 Sep 2018, at 17:45, Harald Koenig > wrote: > > On Sep 07, Alan Braslau wrote: > >> rsync uses port 873 >> >> This often gets blocked at many sites. > > an easy and "naiive" test can be trying to connect to that port via

Re: [NTG-context] contextbeta moved or server down?

On Sep 07, Alan Braslau wrote: > rsync uses port 873 > > This often gets blocked at many sites. an easy and "naiive" test can be trying to connect to that port via rsync: telnet 193.2.4.200 rsync or telnet 193.2.4.200 873 the output should look similar to this if that

Re: [NTG-context] contextbeta moved or server down?

I looked into the modem: no port filtering set up there. > On 7 Sep 2018, at 17:25, Alan Braslau wrote: > > rsync uses port 873 > > This often gets blocked at many sites. > > Alan > >> On 7 Sep 2018, at 17:17, Hans van der Meer wrote: >> >> Tried it on a MacBook too, same problem. Could be

Re: [NTG-context] contextbeta moved or server down?

Did this, see below, > On 7 Sep 2018, at 17:16, Mojca Miklavec > wrote: > > On Fri, 7 Sep 2018 at 17:08, Hans van der Meer wrote: >> >> If I connect in the browser to >> contextgarden.net/minimals/setup/$platform/bin (platform set to my osx-64) >> it gives an empty page with text as below.

Re: [NTG-context] contextbeta moved or server down?

On Fri, 7 Sep 2018 at 17:18, Hans van der Meer wrote: > > Ping gave this: Ping gives you the correct address and a sign that you can reach the server. I'm almost certain it's a firewall issue. Please check whether you can reach, say, rsync rsync://rsync.macports.org/ Mojca

Re: [NTG-context] contextbeta moved or server down?

rsync uses port 873 This often gets blocked at many sites. Alan > On 7 Sep 2018, at 17:17, Hans van der Meer wrote: > > Tried it on a MacBook too, same problem. Could be my router then. > >> On 7 Sep 2018, at 17:04, Mohammad Hossein Bateni wrote: >> >> works for me. I have macbook pro

Re: [NTG-context] contextbeta moved or server down?

Tried it on a MacBook too, same problem. Could be my router then. > On 7 Sep 2018, at 17:04, Mohammad Hossein Bateni wrote: > > works for me. I have macbook pro (mid 2015) running High Sierra 10.13.6. I > guess, you should try to ping or traceroute to contextgarden.net >

Re: [NTG-context] contextbeta moved or server down?

On Fri, 7 Sep 2018 at 17:08, Hans van der Meer wrote: > > If I connect in the browser to contextgarden.net/minimals/setup/$platform/bin > (platform set to my osx-64) it gives an empty page with text as below. > Shouldn’t there be something to download? No, because that's the wrong URL. The

Re: [NTG-context] contextbeta moved or server down?

If I connect in the browser to contextgarden.net/minimals/setup/$platform/bin (platform set to my osx-64) it gives an empty page with text as below. Shouldn’t there be something to download? minimals/setup/osx-64/bin There is currently no

Re: [NTG-context] contextbeta moved or server down?

works for me. I have macbook pro (mid 2015) running High Sierra 10.13.6. I guess, you should try to ping or traceroute to contextgarden.net from terminal. the IP is different for www.contextgarden.net, which is probably what the browser looks for. On Fri, Sep 7, 2018 at 10:43 AM Hans van der

Re: [NTG-context] contextbeta moved or server down?

Not here. I copied your call into Terminal and it gave the same timeout as before. My system is a MacPro (2017), could it have a special setting in the tailored software? Anywhere someone with the same machine who can test this? Otherwise, can I download ‘manually’ a package and then install

Re: [NTG-context] contextbeta moved or server down?

Hi Hans, I can download first-setup.sh without problems. $ rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . first-setup.sh sent 38 bytes  received 4826 bytes  3242.67 bytes/sec total size is 4715  speedup is 0.97 Wolfgang Hans van der Meer schrieb am 07.09.18 um 16:25:

Re: [NTG-context] contextbeta moved or server down?

Clicking on contextgarden.net brings up the garden in the browser. The site therefore is reachable from here. I guess then, the problem is in the rsync. I am afraid I known next to nothing about rsync. It would be nice if someone with an Apple Macintosh will try

Re: [NTG-context] contextbeta moved or server down?

Hi Hans, The garden server is working for me as well, but I am on the same IP as Mojca at the moment, so that is probably to be expected. Can you connect to contextgarden.net in *any* way from where you are? There could be some issue with the internet routing from your machine to

Re: [NTG-context] contextbeta moved or server down?

Still not working. this is the full script, I didn’t change the rsync line since last time it ran ok: echo "start download and install of contextbeta" rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . chmod a+x first-setup.sh mkdir tex sh ./first-setup.sh --engine=luatex

Re: [NTG-context] contextbeta moved or server down?

On Fri, 7 Sep 2018 at 11:11, Hans van der Meer wrote: > > This used to give me the latest contextbeta: > rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . > > Today I get this error > start download and iinstall of contextbeta > rsync: failed to connect to contextgarden.net:

[NTG-context] contextbeta moved or server down?

This used to give me the latest contextbeta: rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . Today I get this error start download and iinstall of contextbeta rsync: failed to connect to contextgarden.net: Operation timed out (60) Is the garden down or have the sources been