IDE is not working for me
Closed this issue · 22 comments
What symptom did you see (attaching screenshots as necessary)?
When date and time (UTC) did the problem happen?
20:40 UTC
What steps did you follow to reproduce the problem?
1 Reloaded the page
2 Exited out and tried again
Which web browser did you use (including version number)?
Google Chrome is up to date
Version 89.0.4389.114 (Official Build) (x86_64)
Which operating system did you use (including version number)?
macOS Catalina version 10.15.7
Did you log in to CS50 IDE using the same GitHub account you used to create this issue?
yes
If you open Chrome's console by pressing Ctrl + Shift + J, do you see any errors in the console when you get this error?
Try again now?
davkct
Please try visiting code.cs50.io again now and see if that works?
Apparently it was my browser, changed to chrome and was fine then. Thanks
Same issue - switching browsers does not help unfortunately
I have the same issue, I try to back to code.cs50.io doesn't work.
I have the same issue, I try to back to code.cs50.io doesn't work.
Please email sysadmins@cs50.harvard.edu and be specific about your issue.
Hello
I also receive a 502 Bad Gateway - could not create repo. Please try again in 5-10 minutes. I have also tried to open in VS Code Desktop with the same result.
Thank you for any support to remedy.
Hello, i having the same issue.
hello
I received a similar issue showing Bad Gateway-Could not add as collaborator
please help
Hello, same issue for me :(
Apologies, do keep an eye on https://cs50.statuspage.io/incidents/fmgc736bd132!
Hello i have the same problem , how i can fix it ?
I have the same problem :( tried to follow different tutorials and logging in and out of my github account, as well as restarting chrome but still says bad gateway. What should I do?
I have the same problem :( tried to follow different tutorials and logging in and out of my github account, as well as restarting chrome but still says bad gateway. What should I do?
Please email sysadmins@cs50.harvard.edu about it!
same problem. tried logging out and log in again.






