Originally created by @francoisWeber on GitHub (Aug 27, 2025).
The IP of my server recently changed from X to Y.
My domain name is properly configured to map the new IP address Y.
My applications are configured with a LetsEncrypt certificate and linked to a subdomain of my domain name.
They are working as usual inside my LAN. However, applications are not reachable from outside.
I tried to reload each application's DNS via the "Domains" section of each application and I receive the following message Domain resolves to Y but should point to X.
How to solve this issue ? Is it a local/Dokploy caching problem ? Thank you
Originally created by @francoisWeber on GitHub (Aug 27, 2025).
The IP of my server recently changed from `X` to `Y`.
My domain name is properly configured to map the new IP address `Y`.
My applications are configured with a LetsEncrypt certificate and linked to a subdomain of my domain name.
They are working as usual inside my LAN. However, applications are not reachable from outside.
I tried to reload each application's DNS via the "Domains" section of each application and I receive the following message `Domain resolves to Y but should point to X`.
How to solve this issue ? Is it a local/Dokploy caching problem ? Thank you
@francoisWeber commented on GitHub (Aug 28, 2025):
Looks like the problem comes from Dokploy instance not refreshing it's own new IP adress. I went to https://dokploy-ip/dashboard/settings/server and Server > Update IP. This refreshed the IP address and made the DNS validation work
@francoisWeber commented on GitHub (Aug 28, 2025):
Looks like the problem comes from Dokploy instance not refreshing it's own new IP adress. I went to `https://dokploy-ip/dashboard/settings/server` and `Server` > `Update IP`. This refreshed the IP address and made the DNS validation work
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @francoisWeber on GitHub (Aug 27, 2025).
The IP of my server recently changed from
XtoY.My domain name is properly configured to map the new IP address
Y.My applications are configured with a LetsEncrypt certificate and linked to a subdomain of my domain name.
They are working as usual inside my LAN. However, applications are not reachable from outside.
I tried to reload each application's DNS via the "Domains" section of each application and I receive the following message
Domain resolves to Y but should point to X.How to solve this issue ? Is it a local/Dokploy caching problem ? Thank you
@francoisWeber commented on GitHub (Aug 28, 2025):
Looks like the problem comes from Dokploy instance not refreshing it's own new IP adress. I went to
https://dokploy-ip/dashboard/settings/serverandServer>Update IP. This refreshed the IP address and made the DNS validation work@jaainil commented on GitHub (Aug 29, 2025):
Wrong repository bro post in https://github.com/Dokploy/dokploy.
@francoisWeber commented on GitHub (Aug 29, 2025):
Ow you're right !! Thanks !