-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Coolify won't start after restart proxy #4605
Comments
You can run the installer again to try to fix the problem. Also, what do you mean you cannot access Coolify when you restart the proxy? |
I had a same issue in the past weeks. The issue was that the proxy container was completely gone. It was stopped, deleted and not available anymore. Restart it via command line via docker compose fixed it for me. Since then I never tried it again to restart the proxy. |
What is the command? My server is down. Please help. |
cd into /data/coolify/proxy and start the container via the docker-compose.yml inside the folder. |
I tried but not working. Restarting the proxy makes the server inaccessible. It is accessible by IP but proxy can't be started. |
Error Message and Logs
Coolify Won't start on restart proxy even change nothing on the proxy, just restart.
Steps to Reproduce
2.Login
3.Go to server/proxy
4.Click restart proxy
Example Repository URL
No response
Coolify Version
4.0.0-beta.379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: