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 just installed the latest 1.17.0 release and a couple of monitors started to turn red after the update and stayed like this since. After a bit of investigation it turns out these are all monitors which have a specific hostname rewrite in the /etc/hosts file.
Background: the server serving these services runs behind the same firewall as the server running Uptime-Kuma. To avoid having to use NAT reflection, the Uptime-Kuma server has /etc/hosts entries that point the public DNS entries to the internal address of the server running the services. This way the traffic does not have to pass the firewall, go to the public internet and then go back into the same firewall, while keeping the original DNS entries intact.
With the latest update it seems these /etc/hosts entries seems to be not respected anymore.
👟 Reproduction steps
Set up a monitor pointing to service.domain.tld
Set up /etc/hosts entry for service.domain.tld to point to an internal address like 10.0.0.1
See the uptime kuma monitor fail as it's trying to resolve the DNS only not respecting the /etc/hosts
👀 Expected behavior
The /etc/hosts entries should be respected
😓 Actual Behavior
The /etc/hosts entries are not respected
🐻 Uptime-Kuma Version
1.17.0
💻 Operating System and Arch
Arch Linux 5.15.41-1-lts
🌐 Browser
Any
🐋 Docker Version
🟩 NodeJS Version
18.2.0
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
Description
I just installed the latest 1.17.0 release and a couple of monitors started to turn red after the update and stayed like this since. After a bit of investigation it turns out these are all monitors which have a specific hostname rewrite in the
/etc/hosts
file.Background: the server serving these services runs behind the same firewall as the server running Uptime-Kuma. To avoid having to use NAT reflection, the Uptime-Kuma server has
/etc/hosts
entries that point the public DNS entries to the internal address of the server running the services. This way the traffic does not have to pass the firewall, go to the public internet and then go back into the same firewall, while keeping the original DNS entries intact.With the latest update it seems these
/etc/hosts
entries seems to be not respected anymore.👟 Reproduction steps
/etc/hosts
entry for service.domain.tld to point to an internal address like 10.0.0.1/etc/hosts
👀 Expected behavior
The
/etc/hosts
entries should be respected😓 Actual Behavior
The
/etc/hosts
entries are not respected🐻 Uptime-Kuma Version
1.17.0
💻 Operating System and Arch
Arch Linux 5.15.41-1-lts
🌐 Browser
Any
🐋 Docker Version
🟩 NodeJS Version
18.2.0
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: