anvil.server.RuntimeUnavailableError: Failed to launch server runtime

My client code is working but not client call to server. It has been more than 5 hours still facing below error. All forms connected to server are displaying error.

anvil.server.RuntimeUnavailableError: Failed to launch server runtime

Do anyone facing the same issue. Any information when this will get resolved.

Thanks

I am also experiencing this same exact issue,

anvil.server.RuntimeUnavailableError: Failed to launch server runtime

, when I have a server call from the client code. Also started getting this issue around the same time as @abhijeetpandatabul .

Please change python version in settings. I was getting issue in default python beta version 3.10
Change to basic python. It will start working. I resolved it by my own.

1 Like

I have changed the python version to basic python, unfortunately I have some dependencies and a package that needs to be installed onto the server, which shows that only python3.10(beta) allows to install packages and dependencies. When I remove the dependencies and the package and change the python version to basic python3 then the application loads and runs and the server runtime also starts and works. However my application needs these dependencies and packages for some features. When I change everything back(re-install the packages and dependencies and the change python version back to python3.10(beta)), I then get the same error(anvil.server.RuntimeUnavailableError: Failed to launch server runtime).

This was an issue affecting some of our Free Plan users, but it has now been resolved!

3 Likes

Same error here, with my Apps…

I greatly appreciate your prompt response. I am not getting this error anymore, thank you very much.

1 Like

Hi!
Is this happening again today?

Apparently yes, I’m dealing with this issue rn

This should now be resolved (again!). Can you let me know if you still see the error?

Fixed for me! Thanks for the quick solution.

Well… it changed the error!
Now I can run mi app directly, but if I try to use it as component from another app, I get this message:

anvil.server.TimeoutError: Server code took too long

at app/ProcSM/Main/Form1/init.py:44

Actually, it’s unstable: sometimes it works, sometimes it doesn’t.

I’m still receiving the error
anvil.server.RuntimeUnavailableError: Internal server error: Server runtime failed to start.

It is now working again, as @jchnaiderman said, it seems to be intermittent

Well, once again… it is not working.
If this affects only “Free Plan Users”… is this a way to put pressure for paying?
Trust me, I could pay… and I was wiling to do so… but if your company uses this kind of strategy, I don’t know what can I expect in the future… It makes me hesitate regarding this.

@jchnaiderman I wish it were that simple – that way, when things go wrong, we could just stop twirling our moustaches evilly and thereby stop the incident!

Unfortunately, the truth is more prosaic than that: Our Free-user runtime environments have (a) a different sandboxing configuration, to maximise tenancy, which has made them finicky in unexpected ways, and (b) a much greater propensity to abuse by any of the menagerie of pests who arrive if you offer free computing resources on the internet.

This was why, for the longest time, we didn’t offer custom Python packages on the Free plan - we just opted out of the pain - and it’s the main reason why our Free-user-facing infrastructure is a bit of an incident magnet. Obviously this isn’t ideal (very much not for our user community, but midnight incident response isn’t my idea of a fun time either :wink: ). We’re working on it!

As I type, the Free runtime environments are back on their feet, and your apps should be running.

3 Likes

Thank you very much for taking the time to answer my concerns.
I understand the hard balance you are talking about.

Hello,
Having the same issue today.