Beta.FreeCodeCamp.org is down - 502 Bad Gateway
See original GitHub issueChallenge Name
beta.freecodecamp.org
Issue Description
Beta is down again for the second time this evening. Quincy corrected it the first time but now getting errors again 502 Bad Gateway
Browser Information
- Browser Name, Version:
- Operating System:
- Mobile, Desktop, or Tablet:
Your Code
Screenshot
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
502 Bad Gateway Error [Solved] - freeCodeCamp
The causes of the 502 bad gateway error include an overloaded server, an error in the code, and yet-to-be-propagated domain names. So the...
Read more >Error 502 Bad Gateway Meaning - freeCodeCamp
When you visit a website and you get a “502 Bad Gateway” error, it means there's an issue with the servers powering the...
Read more >502: Bad Gateway on freeCodeCamp website?
I'm using the freeCodeCamp api to get user data in a Node app, and I used to be able to get data just...
Read more >Bad Gateway? Anyone else? - The freeCodeCamp Forum
Anyone else getting a bad Gateway notification when trying to enter the site? Doesn't let me do anything. :confused:
Read more >FreeCodeCamp host is Down
I'm getting a 502 Bad Gateway while attempting to login via GitHub. It seems as if the host @ freeCodeCamp.org is down.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@theoutlander Thanks for the feedback. We may be able to build some sort of status page in the future.
Nice. I didn’t know that. People testing it were not sure what was going on, so I figured access to a dashboard might be nice.