Updating Proxmox without subscription

P

proxmox_nooblet

New Member
Jan 15, 2022
6
0
1
35
New to proxmox! Got a home lab, and I want to install lm-sensors but keep hitting repository errors.

root@lab:/etc/apt/sources.list.d# apt-get install lm-sensors
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package lm-sensors
root@lab:/etc/apt/sources.list.d#

So, trying to do 'apt-get update'. But run into other errors.

root@lab:/etc/apt/sources.list.d# apt-get update
Err:1 http://ftp.us.debian.org/debian bullseye InRelease
Temporary failure resolving 'ftp.us.debian.org'
Err:2 http://download.proxmox.com/debian/ceph-octopus bullseye InRelease
Temporary failure resolving 'download.proxmox.com'
Err:3 http://security.debian.org bullseye-security InRelease
Temporary failure resolving 'security.debian.org'
Err:4 http://download.proxmox.com/debian/pve buster InRelease
Temporary failure resolving 'download.proxmox.com'
Err:5 http://ftp.us.debian.org/debian bullseye-updates InRelease
Temporary failure resolving 'ftp.us.debian.org'
Reading package lists... Done
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye/InRelease Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/bullseye-updates/InRelease Temporary failure resolving 'ftp.us.debian.org'
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://download.proxmox.com/debian/ceph-octopus/dists/bullseye/InRelease Temporary failure resolving 'download.proxmox.com'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/buster/InRelease Temporary failure resolving 'download.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

Contents of sources.list.d directory

root@lab:/etc/apt/sources.list.d# ls
ceph.list pve-enterprise.list pve-no-subscription.list

pve-no-subscription.list contains

#deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

pve-enterprise.list is totally commented out, but has the original. Haven't changed ceph.list, but it has

deb http://download.proxmox.com/debian/ceph-octopus bullseye main

and my /etc/apt/sources.list is unchanged and contains

deb http://ftp.us.debian.org/debian bullseye main contrib

deb http://ftp.us.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

One of the articles suggested it's an issue with DNS not resolving. So I tried to ping 8.8.8.8 and got this:

root@lab:/etc/apt/sources.list.d# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3052ms\

So I modified my /etc/resolv.conf file:

#search rat.environment
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1

Which didn't help.

Please see this reddit post for things I have tried so far: https://www.reddit.com/r/Proxmox/comments/s48qj0/updating_proxmox_without_subscription/hst8ry6/

What am I missing? Is there another direction I should be going in? I also tried to modify the analogs of these same files within the Proxmox webgui, but nothing helped. Any help would be greatly appreciated!
 
proxmox_nooblet said:
oot@lab:/etc/apt/sources.list.d# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3052ms\
Click to expand...

The problem is more that you can´t access the Internet. That makes resolving impossible. :(
 
Whats your output of cat /etc/network/interfaces? I guess you use a random gateway IP that doesn'T match your routers IP.
 
Dunuin said:
Whats your output of cat /etc/network/interfaces? I guess you use a random gateway IP that doesn'T match your routers IP.
Click to expand...
There was a cat output in the reddit post, but reran it again as there were some Linux Bridges deleted.


Bash: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.100.2/24
        gateway 192.168.100.1
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0
 
And your routers IP is really 192.168.100.1? Not something more usual like 192.168.0.1 or 192.168.1.1?
 
Last edited:
When I enter 192.168.100.1 into my browser, it takes me to my routers login page. I can ping it, both from my lab PC (proxmox) and home PC.
 
Then your network config looks fine.
Can you ping your router from your PVE host?
Did you change any PVE firewall rules?
 
Last edited:
Yes.


Bash: 
root@lab:~# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=63 time=2.20 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.753 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.737 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.728 ms
^C
--- 192.168.100.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3049ms
rtt min/avg/max/mdev = 0.728/1.104/2.200/0.632 ms
 
SOLUTION:
I have no idea why this was working, but I was able to go to 192.168.100.1 for my Default Gateway. But actually signing into my router, and it was on the 192.168.0.x network. Dunno why it would let me do that, but it did. Changed my interface in the proxmox host to take an ip address from dhcp instead of being configured statically, picked up a new ip (in range) address from the router, and then just added that ip address to the reserved list.
Thank you everyone for the help! Posted solution here for posterity.
 
You must log in or register to reply here.
Top Bottom