Randomly getting "no healthy upstream" with Twenty front-end
This has been a bit of a weird issue that I have not been able to capture the logs for properly since it's a bit of a rush to get everything back up and I can't find a consistent trigger that causes it but two times now since I deployed Twenty it gives me a no healthy upstream error when accessing my site.
The only way to quickly fix is to just restart the docker containers and everything works fine again but for production I don't really want that happening if possible.
Currently running through a VM hosted through Google Cloud, Docker deployment. Sadly don't have logs right now but next time it happens I can capture logs. Feel like I have a pretty simple deployment and a lot of workflows are actually through n8n and not Twenty natively. Not sure what causes what I believe is the worker to basically die.
Don't expect any answers yet, just wanted to notate this here now.
The only way to quickly fix is to just restart the docker containers and everything works fine again but for production I don't really want that happening if possible.
Currently running through a VM hosted through Google Cloud, Docker deployment. Sadly don't have logs right now but next time it happens I can capture logs. Feel like I have a pretty simple deployment and a lot of workflows are actually through n8n and not Twenty natively. Not sure what causes what I believe is the worker to basically die.
Don't expect any answers yet, just wanted to notate this here now.
