Disused Stations Website ( https://www.disused-stations.org.uk/ )

[riceuten]

...has been offline for some time now.

Have the owners of the site given up (I wouldn't blame them, to be honest), or have the hosting bills proved too much ?

 

[AntoniC]

...has been offline for some time now.

Have the owners of the site given up (I wouldn't blame them, to be honest), or have the hosting bills proved too much ?

Its working for me

 

[Gloster]

Ditto.

 

[Darandio]

Still up and receiving regular updates.

 

[riceuten]

I'm getting

 

[birchesgreen]

Its still up, and latest updates were last month.

 

[OscarH]

I don't know what that error is you have, some corporate malware or something? Try using HTTP instead of HTTPS, it doesn't support the latter unfortunately

(yes Forcepoint looks to be that kind of thing, there's a chance it will block you from making a HTTP connection even if you try and force it in your browser. I had to override my anti-HTTP protection to get it to load)

 

[Wandering Pom]

The problem is that the URL is not https: - it's still just old-style http:
http://www.disused-stations.org.uk/ works just fine for me.

 

[Adam Williams]

I don't know what that error is you have, some corporate malware or something? Try using HTTP instead of HTTPS, it doesn't support the latter unfortunately

I don't get what's going through these spyware software vendors' minds when they think "I know, let's intercept the request, pretend that there's a valid server listening and then return our own useless error" instead of letting the OS/browser do its thing and handle the failure to connect on port 443 correctly.

 

[dosxuk]

I don't get what's going through these spyware software vendors' minds when they think "I know, let's intercept the request, pretend that there's a valid server listening and then return our own useless error" instead of letting the OS/browser do its thing and handle the failure to connect on port 443 correctly.

It's because by the time it's intercepted the request to decide whether or not to allow it, it's too late to let the browser fail to connect.

In a way it's good - because it immediately shows it's some firewall / content blocker stopping you from getting where you expect, rather than the generic web browser response.

 

[mike57]

The issue is with the https:// if you type http://.... then it works fine. Its to do with the way you connect to the website. The website, or its hosts dont support the https:// protocol

A lot of browsers seem to default to using https:// which makes sense as its more secure

If you want a more detailed explanation of https:// it can be found here https://en.wikipedia.org/wiki/HTTPS

 

[riceuten]

Yes, amending the URL to http: did the trick.

 

[TheGrew]

It increasingly surprises me that websites haven't got SSL certificates, a few years ago there was a cost but with the rise of the likes of Lets Encrypt and tools to automate the renewal process like Certbot that excuse is diminishing.