Search results

  1. I

    PVE services start in a DEAD state

    Sorry for the super late reply, no everything PVE related starts as “dead” on system boot until it gets internet in which everything springs to life, I’ve pretty much gave up on it and have been looking at alternatives since even after an update it’s still seeming like a one of a kind issue.
  2. I

    PVE services start in a DEAD state

    Anyone have any idea how we can get this fixed?
  3. I

    PVE services start in a DEAD state

    Without, the dns server is running on a vm on the server~ which won’t start due to proxmox... not having connection Resolv.conf- Search kitty.local Nameserver 192.168.254.254 It’s the router’s ip Out of curiousity I added a line, nameserver 127.0.0.1 and restarted the networking just to see it...
  4. I

    PVE services start in a DEAD state

    Yes, currently my hosts file shows `127.0.0.1 localhost.localdomain localhost 192.168.254.19 baddragon.kitty.local baddragon pvelocalhost` And then the ipv6 stuff, using my phone so I can’t really copy paste, but It resolves itself when I try to ping its hostname it’s full hostname and ofc the ip
  5. I

    PVE services start in a DEAD state

    Hi, I’m not 100% sure if this is a proxmox issue but for the past couple months whenever I have to restart my proxmox server, I have to change the dns settings in the router to point to google or some other non local hosted dns server (fine and dandy my dns server is hosted on a vm on the pve...