The following is happening in Edinburgh, Glasgow and Islay in Scotland, over the wifi of the B&B.
There's no problem accessing the site on my phone without wifi or on my other devices over the phone's hotspot. However, over wifi it gives the error:
The connection for this site is not secure
storiesonline.net didn't accept your login certificate or a login certificate may not have been provided.
Search Bing for storiesonline.net
ERR_BAD_SSL_CLIENT_AUTH_CERT
The wifi provider at the B&B is blocking Storiesonline.net.
That's very common around the world.
I have encountered this in several countries, both when staying hotels and even in a private residence (they had a kid and had nanny controls activated).
DNS over IP was not "a thing" back then so I signed up for Laz's alternate domain - it costs money but the problem went away and has never reoccurred.
That mean the B&B wifi is using a transparent proxy setup.
Wifi services you or you IT service didn't setup should never be trusted.
When using third party Wifi, always use a vpn.
If you do not have a vpn service, configuring a private DNS may in some case bypass the proxy filters.
Might going through a proxy server website work? Or are those too banned?
Are Finestories and Scifistories also banned?
AJ
When using third party Wifi, always use a vpn.
Unfortunately, not always possible.
I've been in some airports where I couldn't get the VPN to connect. The wifi was blocking access to certain ports and VPN handshakes kept failing. So I had to forego the wifi, and go through cellular service to get the VPN connection to work.
That's why I provide separate domains for Storiesonline to bypass network blocks.
I couldn't get the VPN to connect. The wifi was blocking access to certain ports and VPN handshakes kept failing
There are several possible reason for vpn to not work there:
1 Blocking of ports.
In that case just use port 439 for the vpn. also called vpn over https.
2 Blocking of IPs, vpn ip are often banned.
You just change the vpn server until you find one working or you host your own vpn server. It's often a standard config available on vps.
3 Blocking of the vpn dns.
Use the ip instead.
4 Deep packet filtering (the technology used by the GFC) standard vpn will never work, you may connect but the traffic would be cutoff after a short interval.
You can still use Tor protocol with it's snowflake ephemeral proxies with either the Tor Browser (Onion Browser on iOS) or the Brave browser and the snowflake extension. Tor with bridge and snowflake can still pierce the GFC.