Only works on ff for the past couple months

[drizuid]

All other browsers just reload until banned by cloudflare. Started maybe 3 months ago

[drizuid]

it appears this is due to most chromium based browsers trying to force https connections by default.

[GreatWizard]

Oh that's annoying because forced HTTPS blocks all requests to server in order to get the state... I'm going to think about all that if I can implements a newsolution

[drizuid]

I pointed instructions to allow the sure to load unsecured on chromium, you could have https load an error page and just show those instructions?

[drizuid]

Just adding this, i pinned this on discord in #general

For those of you having issues accessing the site, it is not down, it is you. Your browser (or you) are inputting https when it should be http. Here are some options

1. use firefox
2. edge: edge://settings/content/insecureContent add www.lan-play.com to the allowed list (otherwise edge will force you to https which will not work)
3. chrome: chrome://settings/content/insecureContent add www.lan-play.com to the allowed list (otherwise edge will force you to https which will not work)
4. other chromium based stuff: it's going to be something similar to what you see for edge and chrome, they're all the same.
5. you can also try manually specifying http://www.lan-play.com which may or may not work depending on your browser's enforcement/addons

It is worth noting that if a user leaves it sitting there long enough, due to the infinite loop, cloudflare will eventually ban them for "attacking"

[minecrafted1432]

The browsers only try to force https if the webserver offers it. There is a script tag in index.html that checks whether a user accessed the site using https and if so, redirects to http. The Browser knows that the site is also served on https and redirects back to https. Disabling https at the website hoster would stop the loop.

If https is disabled at the hoster, users get a warning when accessing the website, but they can click on ignore. Since the webserver wouldn't offer https anymore, the browser wouldn't try to force it.

Oh that's annoying because forced HTTPS blocks all requests to server in order to get the state... I'm going to think about all that if I can implements a newsolution

If you would use https on the website, the lan play server would also need to support https. I think staying on http is the simplest solution