"SOLVED"Can ping 8.8.8.8, 1.1.1.1 and my home network, but can't update

D

Dreyhunt

New Member
Mar 3, 2025
11
0
1
Hi, I relatively new to Proxmox and as the title stated I can ping those, but can't ping anything else. I had the same problem with my previous Proxmox server, but I can't remember how I solved the issue...

When I try to update I get this:
Code: 
root@pve:~# apt update
Ign:1 http://ftp.ca.debian.org/debian bookworm InRelease
Ign:2 http://download.proxmox.com/debian/pve bookworm InRelease           
Ign:3 http://security.debian.org bookworm-security InRelease               
Ign:4 http://ftp.ca.debian.org/debian bookworm-updates InRelease
Ign:1 http://ftp.ca.debian.org/debian bookworm InRelease
Ign:3 http://security.debian.org bookworm-security InRelease
Ign:2 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:4 http://ftp.ca.debian.org/debian bookworm-updates InRelease
Ign:1 http://ftp.ca.debian.org/debian bookworm InRelease
Ign:3 http://security.debian.org bookworm-security InRelease
Ign:2 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:4 http://ftp.ca.debian.org/debian bookworm-updates InRelease
Err:1 http://ftp.ca.debian.org/debian bookworm InRelease
  Temporary failure resolving 'ftp.ca.debian.org'
Err:3 http://security.debian.org bookworm-security InRelease
  Temporary failure resolving 'security.debian.org'
Err:2 http://download.proxmox.com/debian/pve bookworm InRelease
  Temporary failure resolving 'download.proxmox.com'
Err:4 http://ftp.ca.debian.org/debian bookworm-updates InRelease
  Temporary failure resolving 'ftp.ca.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ftp.ca.debian.org/debian/dists/bookworm/InRelease  Temporary failure resolving 'ftp.ca.debian.org'
W: Failed to fetch http://ftp.ca.debian.org/debian/dists/bookworm-updates/InRelease  Temporary failure resolving 'ftp.ca.debian.org'
W: Failed to fetch http://security.debian.org/dists/bookworm-security/InRelease  Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease  Temporary failure resolving 'download.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
It seems to be a sort resolver issue, but I'm not an expert. I'm just really starting to go deeper into networking.

There's the ping for 8.8.8.8:
Code: 
root@pve:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=15.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=11.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=12.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=11.2 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=120 time=13.1 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=120 time=13.7 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=120 time=10.8 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=120 time=13.7 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=120 time=11.2 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=120 time=11.0 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 10.783/12.365/15.014/1.367 ms

There's the one for 1.1.1.1:
Code: 
root@pve:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=16.5 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=12.2 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=16.6 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=13.7 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=11.1 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=60 time=11.5 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=60 time=10.8 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=60 time=12.2 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=60 time=12.4 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=60 time=12.1 ms
--- 1.1.1.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9017ms
rtt min/avg/max/mdev = 10.833/12.911/16.582/1.953 ms


I have my server connected to a switch(bridge mode) and the switch is connected to a opnsense router(router mode)
Code: 
root@pve:~# ip r
default via 192.168.1.1 dev vmbr0 proto kernel onlink
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.20
A quick note is that the default of 192.168.1.1 is correct as is the 192.168.1.0. They're both the same as the VM the only difference is that the IP of the server is a static one out of the dhcp range, but the VM is configured with dhcp.

Last thing my VM has internet and no problem updating, navigate online and even has a perfectly working Steam app. I don't seems to be able to find info on this. Most people can't ping anything outside while I can ping these two although nothing else. Any help would be extremely appreciated.
 
Hi @Dreyhunt, welcome to the forum.

Have you checked the contents of your /etc/resolv.conf or /etc/network/interfaces to ensure that DNS servers are properly defined?

Pinging an IP address bypasses DNS resolution, and based on your description, the issue is likely related to network resolution.

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: alexskysilk
@bbgeek17 I checked and the first one looks like that:
Code: 
search node.1
nameserver 127.0.0.1

The name of my server is pve.node.1

The second like so:
Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.20/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0


source /etc/network/interfaces.d/*

The second one look correct, but I'm not sure about the first one.

*Edit typos
 
Should I keep the 127.0.0.1 and just add the other as such:
Code: 
search node.1
nameserver 127.0.0.1
nameserver 8.8.8.8

Or should I rename the first one:
Code: 
search node.1
pve.node.1 127.0.0.1
nameserver 8.8.8.8
 
It worked. I can update the server now. Thank you! I think I'll keep it the"nameserver 127.0.0.1" and just add "nameserver 8.8.8.8". I'll be playing around with dns to get my vm server to get custom name and understand dns better.

By the way, thank you for the video very informative. Also thanks for your help in general!
 
You must log in or register to reply here.
Top Bottom