I have no idea what to do. I emailed support and have gotten no response other than one telling me to sign into the fastly dashboard to verify which I dont even have an account on?
The project is https://woomy-online.glitch.me This is a videogame so the downtime is kind of killer
Side note: Why is this even a thing?!! If its an issue within my project that’s causing errors starting, I should be able to still edit it to fix those!!
hoping someonefrom the team sees this and can find the ticket and escalate, it’s clear support is backlogged and/or the agent thought you were talking about an app on fastly.
i can say that the reason for suspensions like this is typically that something happened at restart and it suspended so not to lose any app data or that the project was out of disk space, but unfortunately you won’t know until someone on the team looks into it.
if you go to the editor view at Glitch :･ﾟ✧ while logged in, is there a button to download the app tar file and uncompress it and see how big the folder is? at the very least you’ll have the code and can deploy it in an other app or elsewhere while you wait. sorry you’re going through this!
Hi @Drako_Hyena! I’ve been able to unsuspend your project and it appears to be running at the moment so hopefully you can at least figure out what’s going on. Apologies for the delay, there is as Jenn said a very big backlog of tickets being worked through at the moment. If you have any further issues please reply here and we’ll do our best to help.
Hey @sue-smith, I hate to bother you but it happened again to the same project… Im moving to a different host soon and just need to set up the redirect link but I cant do that if its suspended.
Not that it matters much now, but this appears to happen whenever the project looses its boost. (My subscription just ran out… like last time)
I’ve unsuspended your project - it looks like it got caught in a different project deciding that now is the perfect time to do some platform abuse in a way that got a bunch of projects flagged even though they were doing nothing wrong.
Looks like I spoke too soon, something’s automatically resuspending, so I’m going to have to dig deeper to see what’s going on here.
After some more digging, it does look like this is indeed caused by the boost expiring, making the project over-sized. Ironically, it’s not the project itself, there’s barely anything in terms of real files, but your .git dir is roughly 280MB. So: I’ve temporarily size-boosted your project, which should mean it can now at least load so you can use the editor’s terminal to do some git maintenance. 280MB is a pretty unusual size, so you can try running
git gc --aggressive --prune
to see if that clears it up a bit (you can run du -sh .git to see how much space the git dir is taking up). If that doesn’t have much of an effect, you could also try:
git reflog expire --expire=now --all
git repack -ad
git prune
which is a bit more aggressive.
And if none of that works, a last ditch option would be delete the .git dir, and then rebuild it by running git init in the project directory, followed by git add . to add all the current content to the staging area, and then git commit -m "reset" to mark those “changes” as your new first commit.
Thank you, that did appear to be the issue… a classic one.
Thanks for everything over the years btw 