fresh install VE 2nd attempt, still in shell, apt update errors

jmsilva

New Member
Aug 31, 2023
5
0
1
Trying out Proxmox VE for a personal project, it's between my favorites of all the Linux distros that have tested in the last 6 weeks. But on the first install seems like something went wrong, so here we are again. This time accessing only thru ssh from another identical machine running Ubuntu Server 22.04 LTS. After install from USB /etc/hosts was edited as shown below to reflect the complete network, also IPv6 was disabled at the /etc/hosts and the router configuration.

Is this behavior on "apt update" normal for Proxmox? The first install apt update alone took over 1 hour, to then just fail at the end, so that's why I am repeating the install, all help and suggestions are greatly appreciated.

STDOUT apt update with errors.
root@amdb:~# apt update
Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://ftp.us.debian.org/debian bookworm InRelease
Hit:3 http://ftp.us.debian.org/debian bookworm-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Err:5 https://enterprise.proxmox.com/debian/pve bookworm InRelease
401 Unauthorized [IP: 144.217.225.162 443]

Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-quincy/dists/bookworm/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease
401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


STDOUT ifconfig:
root@amdb:~# ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 84:47:09:1d:cb:82 txqueuelen 1000 (Ethernet)
RX packets 979 bytes 351871 (343.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 574 bytes 64053 (62.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.75.160 netmask 255.240.0.0 broadcast 0.0.0.0
inet6 fe80::8647:9ff:fe1d:cb82 prefixlen 64 scopeid 0x20<link>
ether 84:47:09:1d:cb:82 txqueuelen 1000 (Ethernet)
RX packets 818 bytes 331689 (323.9 KiB)
RX errors 0 dropped 38 overruns 0 frame 0
TX packets 575 bytes 63555 (62.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

CONTENT /etc/hosts:
root@amdb:~# cat /etc/hosts

# filled by Proxmox installer
127.0.0.1 localhost.localdomain localhost
127.0.1.1 amdb.fang.xyz amdb

# Raspberry servers eth0 ***jms***
172.16.75.100 pi4a.fang.xyz pi4a
172.16.75.101 pi4b.fang.xyz pi4b
172.16.75.102 pi4c.fang.xyz pi4c
172.16.75.103 pi4d.fang.xyz pi4d

# AMD WorkStations/servers eno2 *** jms***
172.16.75.150 amda.fang.xyz amda
172.16.75.160 amdb.fang.xyz amdb
172.16.75.170 amdc.fang.xyz amdc

# AMD WorkStations/servers wifi ***jms***
172.16.75.151 amda.fang.xyz amdawf
172.16.75.161 amdb.fang.xyz amdbwf
172.16.75.171 amdc.fang.xyz amdcwf

# The following lines are desirable for IPv6 capable hosts Commented to leave only IPv4
#1 ip6-localhost ip6-loopback
#fe00::0 ip6-localnet
#ff00::0 ip6-mcastprefix
#ff02::1 ip6-allnodes
#ff02::2 ip6-allrouters
#ff02::3 ip6-allhosts
#EOF

STDOUT ping:
root@amdb:~# 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=52 time=25.9 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=26.3 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=26.9 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=26.3 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=26.4 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=26.6 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=26.4 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=27.1 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=26.4 ms
^C
--- 1.1.1.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8014ms
rtt min/avg/max/mdev = 25.912/26.487/27.109/0.330 ms

Thank all,

Juan Silva
admin@famg.xyz
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!