Update Err:1 no-subscription

fanava

New Member
Mar 11, 2020
16
8
3
37
Hello. I can not update.
My system:

sources.list
Code:
deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

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

pve-enterprise.list
Code:
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

Still getting an error.
Code:
root@pve1:~# apt-get update
Err:1 http://ftp.debian.org/debian buster InRelease
  Temporary failure resolving 'ftp.debian.org'
Err:2 http://download.proxmox.com/debian/pve buster InRelease
  Temporary failure resolving 'download.proxmox.com'
Err:3 http://security.debian.org/debian-security buster/updates InRelease
  Temporary failure resolving 'security.debian.org'
Err:4 http://ftp.debian.org/debian buster-updates InRelease
  Temporary failure resolving 'ftp.debian.org'
Reading package lists... Done
W: Failed to fetch http://ftp.debian.org/debian/dists/buster/InRelease  Temporary failure resolving 'ftp.debian.org'
W: Failed to fetch http://ftp.debian.org/debian/dists/buster-updates/InRelease  Temporary failure resolving 'ftp.debian.org'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/buster/InRelease  Temporary failure resolving 'download.proxmox.com'
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease  Temporary failure resolving 'security.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@pve1:~#

Thanks for the help.
 
root@pve1:~# apt-get update Err:1 http://ftp.debian.org/debian buster InRelease Temporary failure resolving 'ftp.debian.org' Err:2 http://download.proxmox.com/debian/pve buster InRelease Temporary failure resolving 'download.proxmox.com' Err:3 http://security.debian.org/debian-security buster/updates InRelease Temporary failure resolving 'security.debian.org' Err:4 http://ftp.debian.org/debian buster-updates InRelease Temporary failure resolving 'ftp.debian.org'

You have a name resolving (DNS) issue.. Do you have a valid DNS server setup?

That can be edited in Webinterface under Node → DNS or by editing /etc/resolv.conf
 
so been trying to update and keep getting this error
starting apt-get update
Err:1 http://ftp.us.debian.org/debian bullseye InRelease
Temporary failure resolving 'ftp.us.debian.org'
Err:2 http://security.debian.org bullseye-security InRelease
Temporary failure resolving 'security.debian.org'
Err:3 http://download.proxmox.com/debian/pve bullseye InRelease
Temporary failure resolving 'download.proxmox.com'
Err:4 http://ftp.us.debian.org/debian bullseye-updates InRelease
Temporary failure resolving 'ftp.us.debian.org'
Reading package lists...
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/pve/dists/bullseye/InRelease Temporary failure resolving 'download.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
TASK OK
ive tried severaly different dns settings as suggested by other posts and im never even able to ping google.com. settled with 75.75.75.75 primary and 75.75.76.76 secondary dns as suggested by my isp and still nothing... like im cut off from the internet. total noob and totally clueless
 
yeah, that sounds like your network config is wrong.. can you ping 8.8.8.8 ?
 
Please provide the full output in code-tags each from the PVE-host of:
  • cat /etc/network/interfaces
  • ip a
 
from cat /etc.....
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.0.0.88/24
gateway 192.168.100.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
from ip a...
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether ec:b1:d7:46:e8:47 brd ff:ff:ff:ff:ff:ff
altname enp0s25
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ec:b1:d7:46:e8:47 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.88/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::eeb1:d7ff:fe46:e847/64 scope link
valid_lft forever preferred_lft forever
8: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
link/ether 7e:7f:29:62:3a:b0 brd ff:ff:ff:ff:ff:ff
9: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 3e:0f:9c:5c:5d:9b brd ff:ff:ff:ff:ff:ff
10: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether ce:8a:55:ab:67:ea brd ff:ff:ff:ff:ff:ff
11: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether 66:01:08:24:4d:6a brd ff:ff:ff:ff:ff:ff
 
address 10.0.0.88/24
gateway 192.168.100.1

Without routing, your PVE-host can not reach your gateway.
Is this your actual gateway (most likely the IP of your router) or did you simply let it on the default (fallback) IP? I highly assume the latter; if so, you need to change the gateway IP in your: /etc/network/interfaces to your actual gateway.
 
Without routing, your PVE-host can not reach your gateway.
Is this your actual gateway (most likely the IP of your router) or did you simply let it on the default (fallback) IP? I highly assume the latter; if so, you need to change the gateway IP in your: /etc/network/interfaces to your actual gateway.
thank you so much... not much of what you told me made much sense but your answer got me across the finish line. Cheers. how do i mark this as solved?
 

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!