This is not the first time when my healthy working webservice interrupts unexpectedly and take the website down. (b6d9992b).
It fails silently until I deploy again the exact same commit (without build).
What do you mean by it? How does it fail? Does it stop responding?
As for the screenshot, it’s a known console issue that we are working on.
The website goes down .. 500 error no response. Then when I login to the console I see that there’s no web instance attached to my deployment. Then I will have to redeployment manually to restore my service
After 1h of inactivity, we put an instance to sleep. When a new request comes, we wake up the instance. If it takes a long time for an instance to start, you can see a 500 error.
I’ve checked the logs, and I don’t see any issue with your app.
That’s because I redeployed it.
It’s happening again. To be fair, after evaluating Koyeb I don’t think it’s reliable. Sorry but that’s not a great user experience.
The service has been down without making any changes for 3 days. It can’t be hibernating for that long despite the many requests it has received. Now says 404.
And I couldn’t add more than one image attachment in here (according to your policy) !!
It’s been 24 hours since the last attempt to load the service. I left it down for you to prove that Koyeb failed it not hibernation.
Hey @M_Y
We are working on the fix. It will be released today. I’m really sorry that it’s affecting you.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.