[Solved][Proxmox update] Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 51.79.159.216 443]

-

Here is the solution to the Proxmox update and upgrade issue. Error : E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443]

Error: 

root@moni:~## apt update

Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease           
Hit:3 http://ftp.debian.org/debian buster-updates InRelease   
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease 401  Unauthorized [IP: 51.79.159.216 443]
Reading package lists... Done            |
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 51.79.159.216 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster 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.


Solution:

If you check the proxmox repository  /etc/apt/sources.list.d/pve-enterprise.list, you will find that the apt package manager on the fresh Proxmox host is configured to download packages from Enterprise Repository. For enterprise package, unless your pay the subscription one cannot upgrade the proxmox.   

If you don't want to pay and use the free version of Proxmox you should switch to No-Subscription Repository.

To do that replace the repository:

deb http://enterprise.proxmox.com/debian/pve buster pve-enterprise

with following:

deb http://download.proxmox.com/debian/pve buster pve-no-subscription


Now try updating, it should work.

root@moni:~##apt update

Hit:1 http://security.debian.org buster/updates InReleaseHit:2 http://ftp.debian.org/debian buster InRelease

.
.
.
.

14 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@moni:~# apt upgrade

Reading package lists... Done
Building dependency tree       
.
.
.
After this operation, 288 MB of additional disk space will be used.

Do you want to continue? [Y/n] 

Comments

Post a Comment

Popular posts from this blog

(Solved) (Fixed )MariaDB Unmet Dependencies on Ubuntu 20.04.

-
Error or Issue : Unmet Dependencies:  # sudo apt install mariadb-server Reading package lists... Done Building dependency tree        Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:  mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.25-0ubuntu0.20.04.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Solution or Fix : Remove the different version of MySQL/MariaDB. To check the version run the following command. #  dpkg -l | grep -E 'mysql|mariadb' output:  ii  libdatetime-format-mysql-perl          0.06-1                            all          module to parse and format MySQL dates and times i
Read more

Solution to Moodle Error: Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write.

-
Image
Did you ever come across the following error when you try to access Moodle, "Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write." This usually happens when cache files are corrupted, one probable cause can be improper shutdown of Moodle system. Here is the solution to fix the issue. 1. Go to Moodle root directory     #cd /var/www/html/moodle   2. Run the command      #php admin/cli/purge_caches.php 3. Go to moodledata/cache directory   #cd /var/moodledata/cache    4. Remove the cache store directory, DO NOT remove of change the core_component.php file    # rm -rf cachestore_file/ 5. Refresh the Moodle Page. Its should work.
Read more

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

-
To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /
Read more