I currently have two servers: one for production and one for development. I recently updated only the development server from version 360 to the latest (version 367). Since version 361, all resources now display a message at the bottom of the page:
The latest configuration has not been applied. Please restart (or redeploy) to apply the new configuration.
Additionally, I see the following error message at the top of the page:
Error:
nosgossw48wokwgswscogwo4-proxy Pulling
nosgossw48wokwgswscogwo4-proxy Pulled
network nosgossw48wokwgswscogwo4 declared as external, but could not be found.
I have not made any configuration changes, so I am unsure why I am being prompted to apply new configurations.
After trying a restart, the "restart to apply configurations" message disappeared, but the resource remains marked as unhealthy, despite having a health check defined in the configuration.
Additional Context
These operations have only been performed on the development and test server. I am hesitant to update Coolify to the latest version on the production server, which hosts multiple resources that must remain operational.
I am unsure if this issue is an isolated case or if it could impact the production environment.
Could anyone advise on the best course of action or if this is a known issue with a potential solution?
Error Message and Logs
I currently have two servers: one for production and one for development. I recently updated only the development server from version 360 to the latest (version 367). Since version 361, all resources now display a message at the bottom of the page:
The latest configuration has not been applied. Please restart (or redeploy) to apply the new configuration.
Additionally, I see the following error message at the top of the page:
Error: nosgossw48wokwgswscogwo4-proxy Pulling nosgossw48wokwgswscogwo4-proxy Pulled network nosgossw48wokwgswscogwo4 declared as external, but could not be found.
I have not made any configuration changes, so I am unsure why I am being prompted to apply new configurations.
After trying a restart, the "restart to apply configurations" message disappeared, but the resource remains marked as unhealthy, despite having a health check defined in the configuration.
Additional Context
Could anyone advise on the best course of action or if this is a known issue with a potential solution?
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.367
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
No response