Firefox Monitor appears broken, login gives error 502, how to fix this?
When trying to login to Firefox monitor, redirect to https://accounts.firefox.com is done. I sign in with my existing account. When then pressing "Sign In", the following error appears:
502 Bad Gateway openresty/1.13.6.2
すべての返信 (6)
I just tested myself and it worked. Perhaps there were some server issues that were resolved. Can you try again?
You can try these steps in case of issues with web pages:
You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Clear the Cache and remove the Cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).
"Remove the Cookies" from websites that cause problems:
- Options/Preferences -> Privacy & Security
Cookies and Site Data -> Manage Data
"Clear the Cache":
- Options/Preferences -> Privacy & Security
Cookies and Site Data -> Clear Data -> Cached Web Content: Clear
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Safe Mode start window
Tried again, used the instructions mentioned above, but the problem persists. I also removed the authorization in my Firefox Account, tried again. Tried with all cookies removed, tried with cache cleared and cookies removed. Tried with Chrome, tried on 3 different Windows Machines. Tried with Firefox mobile, tried with Chrome mobile, tried with Safari mobile, tried with Firefox Focus. I'm kind of lost.
Also tried in Safe mode.
In case of issues try to log in to the Firefox Account via this website.
Tried both Firefox Accounts links and I'm able to login successfully. I used this to Revoke the Firefox Monitor application and try to 'refresh' that way.
I suspect (very naively) that there's something in my profile information in Firefox Monitor that's causing this to occur. The issue appears to occur in the Monitor application on the callback from Accounts.