Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

School's elearning website says that "For safety reasons, only https connections are allowed", what should I do to access it?

more options

Hi, as the corona grows, our school decided to go digital, but I have a problem on all of my devices with the schools elearning webstie which translates to: "For safety reasons, only https connections are allowed, we're sorry". Thought it will go away as there were some website problems before, but it seems to be working for everyone else. It's not an firefox exclusive isuee either, tried it on old version of MS Edge, new one too, as well as chromium, even with the firefox on my phone but every single one gives me the same site based error (it's in polish btw).

Hi, as the corona grows, our school decided to go digital, but I have a problem on all of my devices with the schools elearning webstie which translates to: "For safety reasons, only https connections are allowed, we're sorry". Thought it will go away as there were some website problems before, but it seems to be working for everyone else. It's not an firefox exclusive isuee either, tried it on old version of MS Edge, new one too, as well as chromium, even with the firefox on my phone but every single one gives me the same site based error (it's in polish btw).
Attached screenshots

Chosen solution

hi, does this message go away if you click into the address bar and add an "s" into the url, so that it starts with "https://"?

Read this answer in context 👍 1

All Replies (2)

more options

Chosen Solution

hi, does this message go away if you click into the address bar and add an "s" into the url, so that it starts with "https://"?

more options

philipp said

hi, does this message go away if you click into the address bar and add an "s" into the url, so that it starts with "https://"?

As you can see it didn't even have a "http", and using "www" crashed it, but when you just add "https://" it actually works, thank you very much Philip.