Unable to reach any wiki.manjaro.org link, including the one listed here in the left side category options (under ‘Manjaro’). I’ve tried different browser, different distro but the issue remains.
Error message shown:-
This site can’t be reached
wiki.manjaro.org unexpectedly closed the connection.
Try:
Checking the connection
ERR_CONNECTION_CLOSED
Just checked - it appears to be working
I do note that your link is http://wiki.manjaro.org this will redirect to https
This is a weird one. Even if i insert an ‘s’ after ‘http’ and enter, it still produces the same error, and the URL once again shows the insecure ‘http’. I have no idea what’s causing this as it doesn’t appear to be happening with other secured sites. Just tried this on Windows 10, and the same thing.
Manjaro - Upptime - Manjaro Wiki
Manjaro Wiki Up
Overall uptime
99.10%
It is up now. Maybe a temporary dns problem, maybe at your internet provider side?
Try https://wiki.manjaro.org/index.php?title=Main_Page (it’s the actual “301 moved permanently” target)
Hmm! Do you think they’re causing this to happen? I did change to a new ISP nearly 2 months ago. Since then I’ve had no issues with opening websites - until now. But so far only this .org one is affected, which I don’t think I’ve used in a while.
It is up and working fine for me as well.
Maybe you can try a VPN temporarily just to check if isp is actually the problem…
Server side things like bots protection etc can do this kind of a thing…
Recently happened to me with other sites,
Some ISPs route thousands of user’s internet traffic through one static gateway : The curse of Carrier-Grade NAT (CGNAT) or you have a VPN turned on…
Because the world ran out of IPv4 addresses, ISPs (especially mobile data providers or local fiber providers) pool hundreds of customers onto a single public IP address,
which may alert the bot protection system that the user is trying to access the site for 1000th time, and may block the connection…
I had to make actual accounts on sites so that I could use them, I don’t know what bot protection system manjaro wiki uses, but it’s a possibility.
Well I pinged the site and no problem there. If my ISP were blocking it would not ping at all.
S ping wiki.manjaro.org -c5
PING wiki.manjaro.org (2a01:4f9:c010:2eb3::1) 56 data bytes
64 bytes from 2a01:4f9:c010:2eb3::1: icmp_seq=1 ttl=48 time=54.1 ms
64 bytes from 2a01:4f9:c010:2eb3::1: icmp_seq=2 ttl=48 time=76.0 ms
64 bytes from 2a01:4f9:c010:2eb3::1: icmp_seq=3 ttl=48 time=79.5 ms
64 bytes from 2a01:4f9:c010:2eb3::1: icmp_seq=4 ttl=48 time=63.8 ms
64 bytes from 2a01:4f9:c010:2eb3::1: icmp_seq=5 ttl=48 time=61.4 ms
--- wiki.manjaro.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 54.083/66.937/79.464/9.435 ms
So even more perplexing.
The newly installed wiki server has indeed better bot protection, because that was exactly the problem with the old system.
About ISPs and DNS, every internet provider uses caching servers. That is the point to save resources. The good isps refresh every couple of hours, the especially stupid ones leave the cache for a day or 2 (vodafone, i am looking at you). So if there was a minute outage in the actual server, it can transform to a day outage by some home users somewhere.
At least the dns problems are easy to diagnose. Just change the dns in your connection settings, to auto ip manual dns and pick your BigTech Spy DNS server poison - 1.1.1.1, 8.8.8.8, 9.9.9.9. Just disable ipv6 before (or you have to modify that connection too).
Another very easy method to exclude the ISP as a possible problem is to fire you mobile phone. Obviously disabling the wifi so it uses the mobile network. (Unless…you have the same provider for fixed and mobile services, then it wouldn’t make sense).
Or, as said - vpn.
Since you aren’t having any trouble connecting to the forum and ping is working, I suspect there is a problem with outdated or corrupted information in your browser cache or cookies. Did you clear the cache already?
OK. I had an idea and booted to Manjaro’s installer where I know it can’t be anything to do with the network configuration on my internal drive, and it’s exactly the same issue. I also tried wiki.debian.org and that site opens fine. Interesting that it first showed a ticked green ‘V’ for verification just before it opened. So this is looking more like an issue with my ISP, who for some weird reason may be blocking the manjaro site.
It doesn’t explain the contradiction between my being able to ping the site, but it refusing to open in any browser. So I’ll contact my ISP tomorrow when they are open and see what they have to say about this
Those are two very different things. A ping sends out an ICMP echo request, and waits for an ICMP echo reply. Connecting to a site using http, https, ftp, ftps et al is a much higher-level type of connection.
In the ~5 days the wiki was down - I set up a temporary site.
However - due to getting 404 when following links - I added a redirect to index.html which provided a short explanation - I made the error of using 301 which is permanent.
Your browser cache may be in play - try emptying cache - a typical shortcut is Shift+Ctrl+Del then deselect everything but cache or temporary files.
When emptied you may retry.
Problem still ongoing. I don’t think this is going to be resolved. I thought there might be an entry in my hosts file that’s blocking, but checked and there isn’t.
“Your browser cache may be in play - try emptying cache”
If you mean my local cache, I’ve already tried that. It affects both my browsers on all 3 Linux distros I have, as well as on the Windows platform. So it’s not a Linux, Windows or browser issue.
It’s not a big deal for me. I only wanted to refer to the website for a pacman command, and there are plenty of alternative arch-based websites should I need them. Except I’ve never before been able to ping a website, yet unable to open it. So far, every important website that I regularly use is opening without issue, fortunately except that one.
Wenn we say internet provider, we really mean also the home network. Home router, cable modem…if it happens on 3 different computers with 3 OSes, the common denominator is the network (if you have a relatively modern android phone pop it up with a usb cable and choose tethering…) a virtual lan card will be created. Now disable the wifi on the laptop and the phone so you are purely on the mobile network…i bet the wiki will be available.
p.s. a simple fix to try: cut the power supply of the home router and or modem for a minute to hard restart them. As a side effect they might get a new ip from another network segment (that is not buggy) from the ISP. Worth trying.
Just the one computer, but 3 different Linux distros + Windows 10.
The common denominator is my ISP. Clearly the hardware used in the network remains constant but isn’t the cause. I also remove the power from my router every night before I go to bed, so I can rule that attempt out.
I don’t have a smart phone, android or otherwise. Just a simple Nokia type which makes/receives phone calls, texts and has a (as yet unused) camera.
Why not switch your DNS resolvers to well-known public ones that are guaranteed not to use any filters? Just to be on the safe side.
EDIT: I just noticed that Teo had already suggested that. What was the outcome?
You could use some trace commands to find out where the connection ends, e.g.:
mtr -c 1 --report --tcp --port 443 wiki.manjaro.org
or for better readable output:
mtr -c 1 --report --tcp --port 443 -bw wiki.manjaro.org
curl --head --trace - https://wiki.manjaro.org/index.php
or for better readable output:
curl --head --trace - --verbose https://wiki.manjaro.org/index.php
(Instead of the hyphen following the --trace option, you can specify a filename for the output.)
How are you trying to access the Wiki? Are you using saved bookmarks?
If so, you may need to edit or recreate your bookmarks. During the migration to the new Server, many (most) Wiki URLs have changed; for example:
Before the migration:
https://wiki.manjaro.org/index.php/CheatSheet
After the migration:
https://wiki.manjaro.org/index.php?title=CheatSheet
Otherwise, I note that @Acor (in their posts above) has mentioned emptying your browser cache – this means trawling through your browser settings to find the appropriate section — have you tried this?