Replies: 1 comment
-
|
coolify is just a wrapper around docker commands, so once coolify has started your container, it has nothing to do with what happens later when it stops responding, you first need to look at logs/server stats before you restart container to see if it's a memory leak i'm not sure why you would need 3 seperate coolify instances tho, or if its a big site, then why even run coolify on those instances, and not one instance that controls the 3 servers, such that they only run your site and nothing else. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Has anyone experienced their container randomly stops responding.
First off, I know I shouldn't have used this in production but anyways....
So we have a pretty big nextJS site that is hosted under 3 coolify instances under a loadbalancer. From time to time, it randomly stops responding to any requests. Loadbalancer shows high latency but other than that, traffic and load doesnt spike at all. At first, we figured it was our API as some queries were a little too slow but have since been resolved.
The reason why I think it's something to do with either the container or coolify as a whole is that when I trigger a restart of the container, everything goes working as it should.
For context, the containers are built using Github actions and are hosted on a private repo. Coolify just pulls the container to the machine then hosts it.
Any thoughts or ideas?
Beta Was this translation helpful? Give feedback.
All reactions