Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Firefox cannot complete oauth dance to login.microsoftonline.com

  • 1 trả lời
  • 5 gặp vấn đề này
  • 28 lượt xem
  • Trả lời mới nhất được viết bởi dwlocks

more options

While trying to open the outlook web interface (OWA) via any of it's various names (such as https://outlook.office365.com), I am eventually redirected to https://login.microsoftonline.com/. The firefox UI says the server cannot be found, however, if I watch the network trafic, it actually seems that the problem is SSL. The get to microsoftonline.com is marked as insecure (the lock icon has a red slash), even though the protocol is https.

I can't figure out how to get more descriptive errors.

I'm fairly sure this is a certificate problem. Chrome can access OWA, but every firefox installation on every device I have (linux and android) shows this error.

Normally ssl problems give a popup that I know how to handle. I suspect that because this is part of an oauth dance, or because it's in the middle of a redirect chain, I cannot see the correct errors.

Any ideas on how to fix this or to get more informative errors?

While trying to open the outlook web interface (OWA) via any of it's various names (such as https://outlook.office365.com), I am eventually redirected to https://login.microsoftonline.com/. The firefox UI says the server cannot be found, however, if I watch the network trafic, it actually seems that the problem is SSL. The get to microsoftonline.com is marked as insecure (the lock icon has a red slash), even though the protocol is https. I can't figure out how to get more descriptive errors. I'm fairly sure this is a certificate problem. Chrome can access OWA, but every firefox installation on every device I have (linux and android) shows this error. Normally ssl problems give a popup that I know how to handle. I suspect that because this is part of an oauth dance, or because it's in the middle of a redirect chain, I cannot see the correct errors. Any ideas on how to fix this or to get more informative errors?

Giải pháp được chọn

Updating from FF 57 to FF57.0.1 solved the problem. No clue what the root cause was.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (1)

more options

Giải pháp được chọn

Updating from FF 57 to FF57.0.1 solved the problem. No clue what the root cause was.