You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently added a new server in Coolify using the same IP address as the main server (localhost) where Coolify is running. The installation proceeded without any errors, but afterward, I couldn't access the Coolify dashboard using the connected domain; however, I could access it using the IP address.
It would be really helpful if Coolify could provide a warning when attempting to add a server with an IP address that matches the main server. This could help prevent users from making such mistakes in the future.
Steps to Reproduce
Create a new server
Click on "Validate Server & Install Docker Engine"
Example Repository URL
No response
Coolify Version
v4.0.0-beta.347
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04
Additional Information
No response
The text was updated successfully, but these errors were encountered:
AndreFra96
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Oct 7, 2024
Error Message and Logs
I recently added a new server in Coolify using the same IP address as the main server (localhost) where Coolify is running. The installation proceeded without any errors, but afterward, I couldn't access the Coolify dashboard using the connected domain; however, I could access it using the IP address.
It would be really helpful if Coolify could provide a warning when attempting to add a server with an IP address that matches the main server. This could help prevent users from making such mistakes in the future.
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.347
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04
Additional Information
No response
The text was updated successfully, but these errors were encountered: