[SOLVED] Turns out I’m just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.

As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don’t need to access the host remotely/outside my home network, this is just for updating it etc.

I can’t see the host under active devices in my router though.

I have been trying to figure why, but so far without any luck.

      • @PlexSheep@feddit.de
        link
        fedilink
        English
        28 months ago

        Can you dig @9.9.9.9? If so, its certainly DNS. If it’s not DNS, perhaps try to check your iptables iptables -L && iptables -t nat -L.

        • @DreadPotato@sopuli.xyzOP
          link
          fedilink
          English
          08 months ago

          I’m not really sure what to look for, I’m not very experienced in network, but this is the output i get

          • @PlexSheep@feddit.de
            link
            fedilink
            English
            38 months ago

            From the output, you don’t have any routing rules for your machine that block outgoing traffic. The dig command confirms that you can talk to servers. 9.9.9.9 is a common DNS Server. Based off of this, it seems like your problem is that your system has a bad DNS configuration (it’s always DNS).

            Can you parhaps cat /etc/resolv.con? This file normally contains the used DNS servers for Linux systems, unless using special software.

              • @PlexSheep@feddit.de
                link
                fedilink
                English
                18 months ago

                Okay, no external software for DNS management present here. Is that ip a working DNS Server? Is it your server itself perhaps?

                • @DreadPotato@sopuli.xyzOP
                  link
                  fedilink
                  English
                  1
                  edit-2
                  8 months ago

                  192.168.68.210 is my adguard, it’s on a different machine. It should be working, all my other devices use it and I can see the traffic going through it. My servers IP is 192.168.68.120, and I can’t see traffic from that on my adguard at all. But it can ping my adguard.

                  • @PlexSheep@feddit.de
                    link
                    fedilink
                    English
                    18 months ago

                    Okay, so if that’s your actual DNS Server, can you confirm that it works? dig @yourdns debian.org, for example. Afterwards try to use the default DNS of your system dig debian.org. If both works, your DNS config should be fine. Try a curl debian.org -v too.

                    debian.org is just a random domain for this, use whatever you want. I don’t see anything badly configured so far.

      • @BearOfaTime@lemm.ee
        link
        fedilink
        English
        18 months ago

        Is the host configured with static IP or DHCP? Either way, verify it has the correct DNS config.

        Personally I use static for any device that hosts a service.

        What happens if you ping Yahoo.com from the console in Proxmox? It should show the DNS server IP it’s using for resolution.

        • @DreadPotato@sopuli.xyzOP
          link
          fedilink
          English
          1
          edit-2
          8 months ago

          It’s set to static, I also do that for anything that hosts something.

          It won’t ping yahoo.com at all, it just reports 100% packet loss.

          Edit: just realised that it won’t ping my gateway/router either. It’s pinging all other devices on my network just fine though.

          • @Phrey
            link
            English
            18 months ago

            If you can’t ping your gateway, then you have a problem with your interface configuration.

            Do you need it to be on a specific VLAN or something else?