Skip to content
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

Open
wpdevninja opened this issue Dec 17, 2024 · 5 comments
Open

[Bug]: Coolify won't start after restart proxy #4605

wpdevninja opened this issue Dec 17, 2024 · 5 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team.

Comments

@wpdevninja
Copy link

Error Message and Logs

Coolify Won't start on restart proxy even change nothing on the proxy, just restart.

Steps to Reproduce

  1. Install coolify
    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

@wpdevninja wpdevninja added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 17, 2024
@peaklabs-dev
Copy link
Member

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?

@peaklabs-dev peaklabs-dev added 💤 Waiting for feedback Issues awaiting a response from the author. and removed 🔍 Triage Issues that need assessment and prioritization. labels Dec 17, 2024
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Dec 17, 2024
@pseuss
Copy link

pseuss commented Dec 17, 2024

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.

@peaklabs-dev peaklabs-dev removed the 💤 Waiting for feedback Issues awaiting a response from the author. label Dec 17, 2024
@wpdevninja
Copy link
Author

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.

@pseuss
Copy link

pseuss commented Dec 18, 2024

cd into /data/coolify/proxy and start the container via the docker-compose.yml inside the folder.
https://docs.docker.com/compose/gettingstarted/

@wpdevninja
Copy link
Author

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 tried but not working. Restarting the proxy makes the server inaccessible. It is accessible by IP but proxy can't be started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team.
Projects
None yet
Development

No branches or pull requests

3 participants