Playbook for Hetzner VMs being reported as unreachable: Difference between revisions

From Delft Solutions
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:
# Manually run  `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable.  
# Manually run  `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable.  
# Determine whether or not there is a hop in the path that is problematic.
# Determine whether or not there is a hop in the path that is problematic.
# Reset the servers DHCP settings if there is an issue using `dhclient eth0`
# Reset the servers DHCP settings if a hop fails, using `dhclient eth0`

Revision as of 05:21, 7 March 2024

Playbook for debugging Hetzner issue

  1. Check with a separate device that the services being reported as down are unreachable
  2. Manually run `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable.
  3. Determine whether or not there is a hop in the path that is problematic.
  4. Reset the servers DHCP settings if a hop fails, using `dhclient eth0`
Retrieved from "https://docs.delftsolutions.nl/index.php?title=Playbook_for_Hetzner_VMs_being_reported_as_unreachable&oldid=241"