* Knowledge Base 404 Not Found

[tatewise]

The FHUG Home page and Forum seem to have standardised on the https://www.fhug.org.uk/ domain.

The https://fhug.org.uk/ domain produces 404 Not Found error.

The Knowledge Base https://fhug.org.uk/kb/ and https://www.fhug.org.uk/kb/ now both produce 404 Not Found error or a security certificate error.

So the links from the Home page and the Forum page to the Knowledge Base page are broken.

[ColeValleyGirl]

I can't replicate this, Mike.

Have you done the usual clearing of caches?

Also please confirm what url you're using as your starting point -- have you followed the advice to start from https://www.fhug.org.uk ?

[tatewise]

Yes, I am using https://www.fhug.org.uk

If I use https://fhug.org.uk/ or https://fhug.org.uk/forum/ then I get 404 Not Found error, etc.

The problem occurs on Firefox, Chrome & Edge and I've cleared history caches.

It seems that https://www.fhug.org.uk/kb/ is being redirected to https://fhug.org.uk/kb/ which fails.

Everything was working fine yesterday.

[ColeValleyGirl]

Everything was working fine yesterday.

And nothing has changed since.

Can anyone else replicate this?

[Jane]

I am not seeing any errors with any of the links you posted.

If you ping www.fhug.org.uk and fhug.org.uk do you get the same ip for both?
It should be 77.72.2.82

[tatewise]

All of a sudden https://www.fhug.org.uk/kb/ is now working.

BUT many KB links in the Forums are now broken because they use https://fhug.org.uk/kb/...
e.g.
See your viewtopic.php?p=140897#p140897 link to Attachments.
and my viewtopic.php?p=141198#p141198 link to Last Updated Date and Time.

[Jane]

The links work fine both ways, it does look like an issue with the DNS look up for the fhug.org.uk variant.

Mike please confirm the values you are getting for the two pings.

[Jane]

Another thought, if you have mobile data on your phone do you have the same problem there?

[tatewise]

Ping results yield different IP for those two domains:

Code: Select all

PS C:\Users\Mike> ping  www.fhug.org.uk

Pinging fhug.org.uk [77.72.2.82] with 32 bytes of data:
Reply from 77.72.2.82: bytes=32 time=12ms TTL=56
Reply from 77.72.2.82: bytes=32 time=12ms TTL=56
Reply from 77.72.2.82: bytes=32 time=12ms TTL=56
Reply from 77.72.2.82: bytes=32 time=12ms TTL=56

Ping statistics for 77.72.2.82:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 12ms, Average = 12ms
PS C:\Users\Mike> ping  fhug.org.uk

Pinging fhug.org.uk [77.72.1.21] with 32 bytes of data:
Reply from 77.72.1.21: bytes=32 time=16ms TTL=56
Reply from 77.72.1.21: bytes=32 time=11ms TTL=56
Reply from 77.72.1.21: bytes=32 time=12ms TTL=56
Reply from 77.72.1.21: bytes=32 time=11ms TTL=56

Ping statistics for 77.72.1.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 16ms, Average = 12ms

[Jane]

Some how your computer or ISP has picked up the old server IP.

Try clearing you local DNS cache in Windows and your router to fix it. Doing a WHO.IS for the domain shows both are set to 77.72.2.82

image.png (26.94 KiB) Viewed 1324 times

[tatewise]

My mobile phone with Vodaphone seems to work OK via WiFi to the same router.

Tried ipconfig /flushdns which said successful but Ping fhug.org.uk still 77.72.1.21

When did the IP change?

I'll have to investigate how to reset router DNS, but surely I should not have to do any of this?

[jelv]

You probably don't need to do any of this if you are prepared to wait for the duff DNS records to expire which typically could be up to 48 hours.

Is your PC set to use the router DNS? (nslookup fhug.org.uk will tell you what it is using)

If so try setting it to use something else (8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) are good ones to try)

[tatewise]

Tried nslookup as shown below (it is using router IP) but Ping still gives wrong IP:

Code: Select all

PS C:\Users\Mike> nslookup fhug.org.uk
Server:  dsldevice.lan
Address:  192.168.1.1

Non-authoritative answer:
Name:    fhug.org.uk
Address:  77.72.2.82

PS C:\Users\Mike> ping  fhug.org.uk

Pinging fhug.org.uk [77.72.1.21]

[Jane]

The server was upgraded on the 16th September.

One possibility is you have an entry for the old IP in your local host table on the PC or the router, from when we moved last time. Try checking the hosts in the etc folder in Windows. Krystal may have had some helper code forcing you over to the new server which has now expired.

[tatewise]

Thank you all for the help.

For some reason the host file had the explicit line:
fhug.org.uk 77.72.1.21

Deleting that line has fixed the problem!

[Jane]

Yes, I suspect you added the line to hosts, when testing the new server when we moved last time and forgot to remove it afterwards.

Nothing on standard windows writes into that file and you normally need Admin rights to do so.

If anyone is interested there is a good article on the subject here https://en.wikiversity.org/wiki/Hosts_file/Edit