惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Hugging Face - Blog
Hugging Face - Blog
量子位
H
Help Net Security
Microsoft Azure Blog
Microsoft Azure Blog
MongoDB | Blog
MongoDB | Blog
小众软件
小众软件
爱范儿
爱范儿
博客园 - 【当耐特】
Vercel News
Vercel News
S
SegmentFault 最新的问题
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
Apple Machine Learning Research
Apple Machine Learning Research
GbyAI
GbyAI
博客园 - 叶小钗
博客园_首页
V
Visual Studio Blog
宝玉的分享
宝玉的分享
B
Blog
MyScale Blog
MyScale Blog
C
Check Point Blog
博客园 - 三生石上(FineUI控件)
L
LangChain Blog
V
V2EX

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Ruined my proxmox installation, help please!
invalid@exam · 2026-06-02 · via Proxmox Support Forum

I have (had) a pc (NAS) with Promox 8.3.0. I used the shell to upgrade but I did it wrong. It was stuck in 8.3.0 telling me that there were 181 for update but apt update would not update anything. A little more research indicated to change the repos from bookworm to Trixie. I did but that make it worst. At some point it the screen indicated the following:
ou are attempting to remove the meta-package 'proxmox-ve'!
I followed the directions because they indicated that I could install promox-ve again with apt install.

I erased it and updated but there were errors. It indicated that I did not have the right repository - it said bookworm was still in use. I checked all the files which had repo information and made it trixie but nothing.

So I think I have to backup some directories and use a USB drive to install promox 9x and then copy back those directories so I do not loose my VMs which include my truenas with all my media.

Any help will be appreciated. Do I do that? backup the config folders and install again? or is there something I can do? It tells me there repo entry is wrong with either bookworm or trixie.

Also, I can only ssh to it now

Last edited:

Please share

Bash:

apt update
apt policy proxmox-ve
find /etc/apt/sources* -type f -exec tail -n+1 {} +

Hello Impact thanks for replying,

I had the machine off. I turned it on and no ssh access. I put a monitor and keyboard and i ran: ip a
and it shows no ip address

apt update shows errors indicating it cannot resolve deb.debian.org
apt policy promox-ve results in: it cannot locate the proxmox-ve package
and also the find command results in:
trixie main contrilb
trixi-updates main contrib
trixie-security main controb

it does show no subscription as disabled (#) but it is bookworm
old list also shows trixie.

I had to take pics since it seems I cannot longer ssh to it.

Share these pictures then.

Share these pictures then.

I attached them and I saw them upload but something went wrong. I will resize them and see if they go up then.

  • IMG_4512.JPG

    IMG_4512.JPG

    1.3 MB · Views: 19

  • IMG_4511.JPG

    IMG_4511.JPG

    1.2 MB · Views: 19

Thank you. I was able to get on lin with the first command and get an IP address. I was then able to run apt update and I attached pictures of results of: "ip a" and "apt update"

  • apt update.JPG

    apt update.JPG

    558.3 KB · Views: 9

  • ip a.JPG

    ip a.JPG

    625.7 KB · Views: 9

  • sources all trixie verified.JPG

    sources all trixie verified.JPG

    1.2 MB · Views: 9

Delete the enterprise list and that error should be gone, then try apt update && apt full-upgrade. If that works try apt install proxmox-ve to get PVE back.

Last edited:

Hello. I just got back to the NAS and I ssh into it. I do run the apt update command and I get the error:
Error: The repository 'http://proxmox.com trixie Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

Sorry, I missed that it's supposed to be download.proxmox.com and not just proxmox.com.
The bad repo is configured here. Remove what you added, alter this file and then try again
1780523660025.png

Last edited:

Hello. Sorry I just got your message now. About a half hour ago I was able to get the distribution updated and I installed prxmox-ve and I got the GUI again. I still get the error - same as before - but at least I can now properly backup my machines in case I finally decide to wipe this box clean and start fresh.

I am attaching a picture of the error from the GUI.

So I still have to work on this.

I want to say thanks again and is there any way I can repay you in some way, at least something. Please let me know - and if you have any thoughts on how to correct this current problem, I am all ears but I will keep reading

  • Screenshot from 2026-06-03 18-40-31.png

    Screenshot from 2026-06-03 18-40-31.png

    31.9 KB · Views: 10

You still have the bogus http://proxmox.com repo configured in your files somewhere. Use the find/tail command from earlier again to locate it.
Alternatively you can try searching directly for http://proxmox.com like this

Bash:

grep -sR "http://proxmox.com" /etc/apt/sources*

node > Updates > Repositories in the GUI might also show it.
A re-install should not be necessary :)

Last edited: