Sadly not, I try that but then it just leads back to an old post for a different issue on the same repl.
My always on won’t actually keep the repl on.
I also keep running into an issue where it’ll say ports are in use but I am unable to terminate them. I think this may be linked to the always on not working, not sure.
The reason I am believing this is an issue with Replit is that this code has been running fine for over a year but once the file system issue happened it hasn’t been. I could be incorrect though.
Using kill 1 I can get it running for about a couple hours maybe, then ill have to repeat the cycle because the always on will glitch out.
We are deprecating Always-On in favor of Deployments, allowing you to keep your Repl on 24/7 reliably without hiccups. You can find more information on our pricing page and in our docs.
I’m having the same issue right now on replit. It says, “We ran into an internal error” “The repl didn’t wake up in time, please try again in 30 secs” and then it asks me to run it again, and it’s just been an ongoing cycle ever since. Where you able to get yours fixed?