Secure Connection Failed when accessing Microsoft Sharepoint
Hello Firefox community. I'm trying to switch over to Firefox from Chrome but I'm encountering issues when it comes to getting Sharepoint from MS Office 365 to work on Firefox. Word, Exel, Outlook, Teams, and One Drive work fine. When it comes to Sharepoint, Firefox gives me a Secure Connection Failed message. Sharepoint works fine on Chrome, Safari, and Edge. Is there a setting I need to change on the Firefox browser that allows me to use Sharepoint cloud without it telling me?
Thanks in advance for all advice and assistance.
ప్రత్యుత్తరాలన్నీ (3)
Web search: https://www.bing.com/search?q=pr_end_of_file_error
radi.stoyanov said Turns out the option DNS over HTTPS is what caused the problem.
jamesafuf123 said https://support.mozilla.org/en-US/questions/1264659#answer-1237475 my ISP was blocking sites like that
cor-el said This usually means that Firefox wasn't able to find a cipher suites to use to connect to this server and reached the end of the list. There can be two possibilities: one is that the server is outdated and doesn't support modern cipher suites, another might be that the server only supports a few cipher suites and Firefox doesn't support any of these.
You can check your browser and possibly compare this with the server setup.
You can check the connection settings.
- Settings -> General -> Network: Connection -> Settings
If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.
See "Firefox connection settings":
Thanks for your response FredMcD. The reason why I thought it could be a Firefox browser setting issue is that it's Microsoft Sharepoint, so I assume Microsoft have their act together, and that Sharepoint works great on all the other major browsers, so it can't be the ISP. I also ran the SSL scan you provided the link to and no vulnerabilities, everything looks fine.
Thanks for your response cor-el. I tried the different proxy settings suggested but no luck so far. The article you provided the link to says it could be an extension causing the issue so I'll play around with those next.