Forums

[edited by admin: check out this "how to deal with 502 Backend errors" page on our wiki]

My django app is getting this error code, I've tried to reload it but the problem is not solved. It's everything ok in the platform?, is something wrong in my app? how i can know it?

The last log in my server.log are these:

Wed Jan 15 22:41:31 2014 - received message 1 from emperor 2014-01-15 22:41:32 ...gracefully killing workers... 2014-01-15 22:41:32 Gracefully killing worker 2 (pid: 3116)... 2014-01-15 22:41:32 Gracefully killing worker 1 (pid: 3113)... 2014-01-15 22:41:32 Wed Jan 15 22:41:32 2014 - received message 1 from emperor 2014-01-15 22:41:35 worker 2 buried after 4 seconds 2014-01-15 22:41:36 worker 1 buried after 5 seconds 2014-01-15 22:41:36 uWSGI: GAME OVER (insert coin) 2014-01-15 22:41:36 chdir(): No such file or directory [core/uwsgi.c line 1450] 2014-01-15 22:41:36 VACUUM: unix socket /var/sockets/cespar.pythonanywhere.com/socket removed. 2014-01-15 22:41:41 *** Starting uWSGI 1.9.20 (64bit) on [Wed Jan 15 21:41:37 2014] *** 2014-01-15 22:41:41 compiled with version: 4.8.1 on 29 November 2013 16:59:47 2014-01-15 22:41:41 os: Linux-3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 2014-01-15 22:41:41 nodename: glenn-liveweb2 2014-01-15 22:41:41 machine: x86_64 2014-01-15 22:41:41 clock source: unix 2014-01-15 22:41:41 detected number of CPU cores: 4 2014-01-15 22:41:41 current working directory: /etc/uwsgi/vassals 2014-01-15 22:41:41 detected binary path: /usr/local/bin/uwsgi 2014-01-15 22:41:41 !!! no internal routing support, rebuild with pcre support !!! 2014-01-15 22:41:41 using Linux cgroup /mnt/cgroups/cpu/user_types/premium with mode 700 2014-01-15 22:41:41 assigned process 5270 to cgroup /mnt/cgroups/cpu/user_types/premium/tasks 2014-01-15 22:41:41 using Linux cgroup /mnt/cgroups/cpuacct/users/cespar with mode 700 2014-01-15 22:41:41 assigned process 5270 to cgroup /mnt/cgroups/cpuacct/users/cespar/tasks 2014-01-15 22:41:41 using Linux cgroup /mnt/cgroups/memory/user_types/premium with mode 700 2014-01-15 22:41:41 assigned process 5270 to cgroup /mnt/cgroups/memory/user_types/premium/tasks 2014-01-15 22:41:41 uWSGI running as root, you can use --uid/--gid/--chroot options 2014-01-15 22:41:41 chroot() to /mnt/chroots/cespar 2014-01-15 22:41:41 setgid() to 60000 2014-01-15 22:41:41 setuid() to 191112 2014-01-15 22:41:41 limiting number of processes to 64... 2014-01-15 22:41:41 your processes number limit is 64 2014-01-15 22:41:41 your memory page size is 4096 bytes 2014-01-15 22:41:41 detected max file descriptor number: 123456 2014-01-15 22:41:41 building mime-types dictionary from file /etc/mime.types... 2014-01-15 22:41:41 536 entry found 2014-01-15 22:41:41 lock engine: pthread robust mutexes 2014-01-15 22:41:41 thunder lock: disabled (you can enable it with --thunder-lock) 2014-01-15 22:41:41 uwsgi socket 0 bound to UNIX address /var/sockets/cespar.pythonanywhere.com/socket fd 7 2014-01-15 22:41:41 Python version: 2.7.5+ (default, Sep 19 2013, 13:52:09) [GCC 4.8.1] 2014-01-15 22:41:41 *** Python threads support is disabled. You can enable it with --enable-threads *** 2014-01-15 22:41:41 Python main interpreter initialized at 0x2232cc0 2014-01-15 22:41:41 your server socket listen backlog is limited to 100 connections 2014-01-15 22:41:41 your mercy for graceful operations on workers is 60 seconds 2014-01-15 22:41:41 setting request body buffering size to 65536 bytes 2014-01-15 22:41:41 mapped 501048 bytes (489 KB) for 2 cores 2014-01-15 22:41:41 *** Operational MODE: preforking *** 2014-01-15 22:41:41 WSGI app 0 (mountpoint='') ready in 4 seconds on interpreter 0x2232cc0 pid: 5270 (default app) 2014-01-15 22:41:41 *** uWSGI is running in multiple interpreter mode *** 2014-01-15 22:41:41 spawned uWSGI master process (pid: 5270) 2014-01-15 22:41:41 spawned uWSGI worker 1 (pid: 5271, cores: 1) 2014-01-15 22:41:41 spawned 2 offload threads for uWSGI worker 1 2014-01-15 22:41:41 spawned uWSGI worker 2 (pid: 5274, cores: 1) 2014-01-15 22:41:41 spawned 2 offload threads for uWSGI worker 2 2014-01-15 22:41:46 announcing my loyalty to the Emperor... 2014-01-15 22:41:46 announcing my loyalty to the Emperor... 2014-01-15 22:51:06 Wed Jan 15 22:51:06 2014 - received message 1 from emperor 2014-01-15 22:51:06 ...gracefully killing workers... 2014-01-15 22:51:06 Gracefully killing worker 1 (pid: 5271)... 2014-01-15 22:51:06 Gracefully killing worker 2 (pid: 5274)... 2014-01-15 22:51:07 worker 1 buried after 1 seconds 2014-01-15 22:51:07 worker 2 buried after 1 seconds 2014-01-15 22:51:07 uWSGI: GAME OVER (insert coin) 2014-01-15 22:51:07 chdir(): No such file or directory [core/uwsgi.c line 1450] 2014-01-15 22:51:07 VACUUM: unix socket /var/sockets/cespar.pythonanywhere.com/socket removed. 2014-01-15 22:51:10 *** Starting uWSGI 1.9.20 (64bit) on [Wed Jan 15 21:51:09 2014] *** 2014-01-15 22:51:10 compiled with version: 4.8.1 on 29 November 2013 16:59:47 2014-01-15 22:51:10 os: Linux-3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 2014-01-15 22:51:10 nodename: glenn-liveweb2 2014-01-15 22:51:10 machine: x86_64 2014-01-15 22:51:10 clock source: unix 2014-01-15 22:51:10 detected number of CPU cores: 4 2014-01-15 22:51:10 current working directory: /etc/uwsgi/vassals 2014-01-15 22:51:10 detected binary path: /usr/local/bin/uwsgi 2014-01-15 22:51:10 !!! no internal routing support, rebuild with pcre support !!! 2014-01-15 22:51:10 using Linux cgroup /mnt/cgroups/cpu/user_types/premium with mode 700 2014-01-15 22:51:10 assigned process 5395 to cgroup /mnt/cgroups/cpu/user_types/premium/tasks 2014-01-15 22:51:10 using Linux cgroup /mnt/cgroups/cpuacct/users/cespar with mode 700 2014-01-15 22:51:10 assigned process 5395 to cgroup /mnt/cgroups/cpuacct/users/cespar/tasks 2014-01-15 22:51:10 using Linux cgroup /mnt/cgroups/memory/user_types/premium with mode 700 2014-01-15 22:51:10 assigned process 5395 to cgroup /mnt/cgroups/memory/user_types/premium/tasks 2014-01-15 22:51:10 uWSGI running as root, you can use --uid/--gid/--chroot options 2014-01-15 22:51:10 chroot() to /mnt/chroots/cespar 2014-01-15 22:51:10 setgid() to 60000 2014-01-15 22:51:10 setuid() to 191112 2014-01-15 22:51:10 limiting number of processes to 64... 2014-01-15 22:51:10 your processes number limit is 64 2014-01-15 22:51:10 your memory page size is 4096 bytes 2014-01-15 22:51:10 detected max file descriptor number: 123456 2014-01-15 22:51:10 building mime-types dictionary from file /etc/mime.types... 2014-01-15 22:51:10 536 entry found 2014-01-15 22:51:10 lock engine: pthread robust mutexes 2014-01-15 22:51:10 thunder lock: disabled (you can enable it with --thunder-lock) 2014-01-15 22:51:10 uwsgi socket 0 bound to UNIX address /var/sockets/cespar.pythonanywhere.com/socket fd 7 2014-01-15 22:51:10 Python version: 2.7.5+ (default, Sep 19 2013, 13:52:09) [GCC 4.8.1] 2014-01-15 22:51:10 *** Python threads support is disabled. You can enable it with --enable-threads *** 2014-01-15 22:51:10 Python main interpreter initialized at 0xcf8cc0 2014-01-15 22:51:10 your server socket listen backlog is limited to 100 connections 2014-01-15 22:51:10 your mercy for graceful operations on workers is 60 seconds 2014-01-15 22:51:10 setting request body buffering size to 65536 bytes 2014-01-15 22:51:10 mapped 501048 bytes (489 KB) for 2 cores 2014-01-15 22:51:10 *** Operational MODE: preforking *** 2014-01-15 22:51:10 WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0xcf8cc0 pid: 5395 (default app) 2014-01-15 22:51:10 *** uWSGI is running in multiple interpreter mode *** 2014-01-15 22:51:10 spawned uWSGI master process (pid: 5395) 2014-01-15 22:51:10 spawned uWSGI worker 1 (pid: 5396, cores: 1) 2014-01-15 22:51:10 spawned 2 offload threads for uWSGI worker 1 2014-01-15 22:51:10 spawned uWSGI worker 2 (pid: 5399, cores: 1) 2014-01-15 22:51:10 spawned 2 offload threads for uWSGI worker 2 2014-01-15 22:51:13 announcing my loyalty to the Emperor... 2014-01-15 22:57:04 announcing my loyalty to the Emperor... 2014-01-15 23:03:46 Wed Jan 15 23:03:46 2014 - received message 1 from emperor 2014-01-15 23:03:46 ...gracefully killing workers... 2014-01-15 23:03:46 Gracefully killing worker 1 (pid: 5396)... 2014-01-15 23:03:46 Gracefully killing worker 2 (pid: 5399)... 2014-01-15 23:03:47 worker 1 buried after 1 seconds 2014-01-15 23:03:47 worker 2 buried after 1 seconds 2014-01-15 23:03:47 uWSGI: GAME OVER (insert coin) 2014-01-15 23:03:47 chdir(): No such file or directory [core/uwsgi.c line 1450] 2014-01-15 23:03:47 VACUUM: unix socket /var/sockets/cespar.pythonanywhere.com/socket removed.

but I don't understand anything.

Can anyone help me?

Thanks a lot

Hi there -- looks like that's our fault, one of our web servers had a problem. I've rebooted it and it should be OK now. We'll investigate the underlying cause when we're back in the office tomorrow -- something similar happened to a different web server earlier on today, so there's clearly something wrong with at least some of them. Thanks for letting us know!

Thanks, I have been able to see my app running 10 minutes ago, but now I think that the server is down again. I hope you can fix it early.

Thanks.

It should be back up now. Keep us posted, everyone, if you see any other issues...

We are having the same problem again... There is no way of working in this situation.

Now it's ok, it's a bit crazy, don't you think?

Sometimes, if you hit “reload web app”, and then, while it’s still reloading (you can see the litter spinner thing), you go and hit the website, you’ll see an error. Could that be it? It’s best to wait until the reload is completely finished...

Something is wrong again? I'm getting the same error code. I don't know why but every time I try to work in your hosting I have the same problem. In my opinion it shouldn't be so common.

hello i'have the same problem with web2py (i was synchronising my dropbox, because it's freeze, i have tried to "reload" and now i get the "502" message regards h

Hm. it seems to be a problem with the same server as last time. And it doesn't affect all the apps on that server, only 3 or 4 of them, including @cespar's for a second time.

I'm going to do a fast-reboot. there will be 2-3 minutes of downtime.

We think we've identified a potential cause of the problem. Looking for ways to confirm / mitigate...

Just encountered the same problem, immediately after restarting my django application

me too, looks like the problem has resurfaced

Just reloaded a couple apps on another account I have here and one of them worked and the other one has the same problem /shrug. Hopefully they're looking into it now, they're usually quite quick when problems like this pop up.

On the case...

OK, it's a different web server this time. Same problem. Should be back in 5 mins.

Back up - thanks :)

Right, we should be back now. The first hit on each affected web app might be a bit slow (it's kicking them off on an as-needed basis) but everything looks OK now from our end. Let me know if you're still seeing problems.

This is actually quite odd. Like I said in the other thread, the problem is caused when people make a specific kind of mistake in their WSGI files. (Again, that's not to try to relinquish our responsibility for keeping PythonAnywhere up and running, we need to make it resilient to this kind of mistake.) But that does make it surprising that it's hit two of our web servers in a 24-hour period. It's not a mistake that people make frequently.

More investigation needed. I'll keep an eye on things, and will start watching all of our web servers rather than just the one I knew was having problems. And we'll also see if there's any way we can get paged when this specific error happens in the future. It looks like there's a clear signature in one of the logs, so we should be able to automate that.

@studentrentit -- thanks for confirming that!

Just checked on my other account (studentrentit is one of my accounts) and this one I can't get up and running. Is there another webserver that's affected as well? Thanks.

EDIT: studentrentit is back down again as well

This is really weird. All of the web servers look OK right now. I bounced the one that your awwester apps are on anyway, just in case the symptom in the logs that I thought was a sign of the problem was a sufficient but not necessary condition -- could you check if either/both are working again?

Both seem to be functioning normal now - thank you!

Excellent, thanks for confirming!

Mine is up and running again, Excellent response time !

No problem, thanks for confirming :-)

Hi, I have the same problem. I've changed the value of DEBUG and my app doesn't work anymore. I've tried to reload my app but with no results. What can I do? Thanks in advance!

Hi, I'm getting the same problem. I first changed DEBUG = False on my Django app, restarted the app, and everything worked fine. I then tried to push some other code updates, restart the app, and am now getting a 502-backend error. From the other comments, it looks like this is a PythonAnywhere issue or an issue caused by someone else the same server. Can I get some help as well? Thx.

I just got this same error as well. My site was fine before I uploaded a new version at about 2:50 AM GMT, and since then it's been down

removed: double post

Same here

I'm seeing a Error code: 502-backend. I created a new web app (manual configuration -> Python 2.7) and stuck with the default WSGI ( ie the "Hello World" app). Despite that, I'm seeing the Error code: 502-backend.

I really don't think it can be me, beacuse I haven't even hooked up my code to the app yet/

I'm also getting a 502-backend error. This error is only occurring on the 1 subdomain that I restarted.

Sorry about that, everyone. One of our web backends had a problem again, it's fixed now. We're working with the guys who wrote the misbehaving code to track down a fix, but it's proving really hard to isolate the problem.

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

i am also getting a 502-backend error . can you explain to me what reason is it? i is not work still

@kinfan I'm taking a look

Hmm, it looks fine to me -- you have a web app with a default PythonAnywhere "Hello world" page on it.

Mine is working, but I had to reload the app & then in my browser hit Ctrl+F5 to force refresh. You might be getting the version that your browser has cached.

That's a good point. Reloading the app shouldn't be necessary -- the fix we did involved reloading every app on the server -- but a force-refresh on your browser might be.

Force-refresh did the trick for me, thanks!

Thanks for confirming!

i also have this debug

The error on your site is a different one -- it's reporting a problem with your web application. Check out the error log for details -- there's a link on the "Web" tab.

I seem to be having this same issue. I was working on adding a new app and got the 502-backend error, though I waited till it was finished reloading before visiting my page, and I'm now getting that same error on my other two apps which were working fine earlier today and should be unaffected by the new one. I don't see anything in my error logs. Help?

Let me take a look -- we did have a problem on one server earlier on today, which is fixed, but perhaps it's spread to others.

OK, yes, one of the web servers is having problems. I'm rebooting it.

Thanks, that did it.

A couple of others were also showing problems -- all should be fixed now.

I'll keep an eye on all of them for the next few hours. Not sure what's causing the problem -- it's an error we've seen before, but never on so many servers at once. It happening simultaneously on a bunch of them makes our original diagnosis of the underlying problem seem less likely, too. Hmm.

Oh, and thanks for confirming that your sites are back!

Same problem here

Investigating...

OK, it looks like another problem with one of our web servers. I've bounced the affected one and all should be OK now.

OK...it works..thanks

I get this Error code: 502-backend page here, it's been there for roughly 2 hours now. No errors on the dashboard logs.

I'm experiencing the same issue as simplequiz--no errors in the logs but "502-backend" appears when I open my site.

Hi,

I'm getting the same error with my Flask web app since last night.

Might be domain name related somehow.

My app shows the 502 error if I use my domain name (www.<domainname>.com) but no error occurs if I use http://<username>.pythonanywhere.com/ - even though both apps have the same wsgi file and the same code-base directory.

• B

It seems to be working now. Sometimes you'll get the 502 for a short period while your web app is reloading.

Thanks glenn, is working now, but 502 was definitely due to something else aside from reloading because I have been reloading trying both my URLs at the same time all morning. maybe there's something else going on?

After I sent the last post, I discovered from a colleague that we'd actually had one of our web servers misbehaving and that he had fixed it. That was probably what you were seeing.

Well it's still not working for me. =/ (for simplequiz, I had to create another account to make it work)

Sorry, forgot to clear my browser's cache. Works fine now, thanks.

Great, glad to hear it :-)

hi, i got the error like this Something went wrong :-( This website is hosted by PythonAnywhere, an online hosting environment. Something went wrong while trying to load it; please try again later.

Debugging tips If this is your PythonAnywhere-hosted site, and you just reloaded it, then the problem might simply be that it hasn't loaded up yet. Try refreshing this page and see if this message disappears.

If you keep getting this message, you should check your site's server and error logs for any messages — you can view them from the Web tab inside PythonAnywhere.

If there's nothing in the logs, and you're sure your site is OK, then it might be a problem on our side. Drop us a line at support@pythonanywhere.com, in the forums, or using the "Send feedback" link on the site, quoting the error code below.

Error code: 502-backend please help me

Did you read the help page linked to at the beginning of this topic? What steps have you taken from that help page to resolve the issue, and what were the results of those steps?

hi, i got the error like this Something went wrong :-( This website is hosted by PythonAnywhere, an online hosting environment. Something went wrong while trying to load it; please try again later.

Debugging tips If this is your PythonAnywhere-hosted site, and you just reloaded it, then the problem might simply be that it hasn't loaded up yet. Try refreshing this page and see if this message disappears.

If you keep getting this message, you should check your site's server and error logs for any messages — you can view them from the Web tab inside PythonAnywhere.

If there's nothing in the logs, and you're sure your site is OK, then it might be a problem on our side. Drop us a line at support@pythonanywhere.com, in the forums, or using the "Send feedback" link on the site, quoting the error code below.

2019-04-21 17:28:36 *** Starting uWSGI 2.0.17.1 (64bit) on [Sun Apr 21 17:28:35 2019] *** 2019-04-21 17:28:36 compiled with version: 5.4.0 20160609 on 15 February 2019 14:46:37 2019-04-21 17:28:36 os: Linux-4.4.0-1075-aws #85 SMP Fri Feb 15 13:52:12 UTC 2019 2019-04-21 17:28:36 nodename: glenn-liveweb7 2019-04-21 17:28:36 machine: x86_64 2019-04-21 17:28:36 clock source: unix 2019-04-21 17:28:36 pcre jit disabled 2019-04-21 17:28:36 detected number of CPU cores: 2 2019-04-21 17:28:36 current working directory: (unreachable)/etc/uwsgi/vassals 2019-04-21 17:28:36 detected binary path: /usr/local/bin/uwsgi 2019-04-21 17:28:36 *** dumping internal routing table *** 2019-04-21 17:28:36 [rule: 0] subject: path_info regexp: .svgz$ action: addheader:Content-Encoding:gzip 2019-04-21 17:28:36 *** end of the internal routing table *** 2019-04-21 17:28:36 chdir() to /home/dextre30/ 2019-04-21 17:28:36 limiting number of processes to 120... 2019-04-21 17:28:36 your processes number limit is 120 2019-04-21 17:28:36 your memory page size is 4096 bytes 2019-04-21 17:28:36 detected max file descriptor number: 123456 2019-04-21 17:28:36 building mime-types dictionary from file /etc/mime.types... 2019-04-21 17:28:36 552 entry found 2019-04-21 17:28:36 lock engine: pthread robust mutexes 2019-04-21 17:28:36 thunder lock: disabled (you can enable it with --thunder-lock) 2019-04-21 17:28:36 uwsgi socket 0 bound to UNIX address /var/sockets/dextre30.pythonanywhere.com/socket fd 3 2019-04-21 17:28:36 Python version: 3.6.6 (default, Aug 22 2018, 20:46:46) [GCC 5.4.0 20160609] 2019-04-21 17:28:36 Set PythonHome to /home/dextre30/.virtualenvs/zoosolution-virtualenv 2019-04-21 17:28:36 *** Python threads support is disabled. You can enable it with --enable-threads *** 2019-04-21 17:28:36 Python main interpreter initialized at 0xed2220 2019-04-21 17:28:36 your server socket listen backlog is limited to 100 connections 2019-04-21 17:28:36 your mercy for graceful operations on workers is 60 seconds 2019-04-21 17:28:36 setting request body buffering size to 65536 bytes 2019-04-21 17:28:36 mapped 501384 bytes (489 KB) for 2 cores 2019-04-21 17:28:36 *** Operational MODE: preforking *** 2019-04-21 17:28:36 initialized 54 metrics 2019-04-21 17:28:36 WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0xed2220 pid: 1 (default app) 2019-04-21 17:28:36 *** uWSGI is running in multiple interpreter mode *** 2019-04-21 17:28:36 gracefully (RE)spawned uWSGI master process (pid: 1) 2019-04-21 17:28:36 spawned uWSGI worker 1 (pid: 3, cores: 1) 2019-04-21 17:28:36 spawned 2 offload threads for uWSGI worker 1 2019-04-21 17:28:36 spawned uWSGI worker 2 (pid: 6, cores: 1) 2019-04-21 17:28:36 metrics collector thread started 2019-04-21 17:28:36 spawned 2 offload threads for uWSGI worker 2 2019-04-21 17:28:39 DAMN ! worker 2 (pid: 6) died, killed by signal 7 :( trying respawn ... 2019-04-21 17:28:39 Respawned uWSGI worker 2 (new pid: 12) 2019-04-21 17:28:39 spawned 2 offload threads for uWSGI worker 2 2019-04-21 17:28:43 DAMN ! worker 1 (pid: 3) died, killed by signal 7 :( trying respawn ... 2019-04-21 17:28:43 Respawned uWSGI worker 1 (new pid: 16) 2019-04-21 17:28:43 spawned 2 offload threads for uWSGI worker 1 2019-04-21 17:28:44 DAMN ! worker 2 (pid: 12) died, killed by signal 7 :( trying respawn ... 2019-04-21 17:28:44 Respawned uWSGI worker 2 (new pid: 20) 2019-04-21 17:28:44 spawned 2 offload threads for uWSGI worker 2 2019-04-21 17:28:46 DAMN ! worker 1 (pid: 16) died, killed by signal 7 :( trying respawn ... 2019-04-21 17:28:46 Respawned uWSGI worker 1 (new pid: 25) 2019-04-21 17:28:46 spawned 2 offload threads for uWSGI worker 1 2019-04-21 17:28:47 DAMN ! worker 2 (pid: 20) died, killed by signal 7 :( trying respawn ... 2019-04-21 17:28:47 Respawned uWSGI worker 2 (new pid: 28) 2019-04-21 17:28:47 spawned 2 offload threads for uWSGI worker 2

Error code: 502-backend please help me

That is the server log. Did you also take a look at your error log?

Yes, there is nothing in the error log.

What does your error log say?

Hey, I got the same error when I tried to enter the admin page. What should i do?

Are you using Django 3.0 or higher, with Python 3.7? Your account is configured to use Python 3.7.0 as its specific version of 3.7, and that Python version has a bug which makes it crash in admin views if you use any version of Django after 3.0.

There are three ways to fix that:

• We can update your account by changing your system image so that you get 3.7.5 instead of 3.7.0, which will fix the issue. However, because changing the system image upgrades a lot of the pre-installed Python packages, any code that you have that relies on those packages might break if it's not compatible with the new versions. Also, because the new image has newer versions of Python, if you have any virtualenvs, you may need to rebuild them. If you're happy to go ahead despite that, just let us know and we'll switch you over.
• You can switch to using Python 3.6 instead of 3.7
• You can use a version of Django that's older than 3.0.

The best option is probably to update the system image, so I'd recommend going that way.