How to setup a community version of Proxmox VE 5.x-6.x

gistfile1.txt

# Disable Commercial Repo
sed -i "s/^deb/\#deb/" /etc/apt/sources.list.d/pve-enterprise.list
apt-get update

# Add PVE Community Repo
echo "deb http://download.proxmox.com/debian/pve $(grep "VERSION=" /etc/os-release | sed -n 's/.*(\(.*\)).*/\1/p') pve-no-subscription" > /etc/apt/sources.list.d/pve-no-enterprise.list
apt-get update

# Remove nag
echo "DPkg::Post-Invoke { \"dpkg -V proxmox-widget-toolkit | grep -q '/proxmoxlib\.js$'; if [ \$? -eq 1 ]; then { echo 'Removing subscription nag from UI...'; sed -i '/data.status/{s/\!//;s/Active/NoMoreNagging/}' /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js; }; fi\"; };" > /etc/apt/apt.conf.d/no-nag-script
apt --reinstall install proxmox-widget-toolkit

sed -i.bak 's/NotFound/Active/g' /usr/share/perl5/PVE/API2/Subscription.pm && systemctl restart pveproxy.service

Thanks @DavidFW1960 ! This helped me removing the NAG, running Proxmox 6.1-3

Hey Guys! I just tried updating my NUC (production) and my test server. I am now going from 6.0-xx to 6.1-15 with no issues here. Both machines are up-to-date as of today; no nag.

Tollbringer

Just did the install, and still getting the nag. I will do a few things and try again. I will follow up and edit if it goes away.

Works for me on 6.1-5 but changed the file name in the second command. Didn't see any files named "pve-no-enterprise.list" in the directory so I changed the file name to match what was already present "pve-no-subscription.list".

I had same issue

Works for me on 6.1-5 but changed the file name in the second command. Didn't see any files named "pve-no-enterprise.list" in the directory so I changed the file name to match what was already present "pve-no-subscription.list".

But after all it works

Once you log out, you need to refresh web browser, before login, if commands inputted correct, then should work.

Is this still up to date? The video that Dr Zzs made on installing proxmox is still all the same process? I plan on installing proxmox on an old all in one HP I am installing a new ssd on. I won't to us proxmox as the OS. I already got it on a USB drive ready. Just making sure nothing has change before I install.

@Shannondalebreaux Yes, the process is the same as described in the video. This gist is still valid.

Good look, I have decided to go with XCP-ng, then install Xen Orchestra, better panel view, amazing, but Proxmox is a lot easer to use.

This still worked for 6.2 🎉

works perfect, great work!

is it possible to get rid of the nagging datacenter status red cross also? see pic

sed -i.bak 's/NotFound/Active/g' /usr/share/perl5/PVE/API2/Subscription.pm && systemctl restart pveproxy.service

tnx . worked for me to running 6.2-9

verified, script works on build 6.2-4

6.2-1 - executing apt-get upgrade after the last command breaks pve-manager, and after reboot the machine isn't reachable over webUI. I applied all the steps in the correct order as described, then ran apt-get update and then rebooted the system, and now it is unreachable. How can I fix this?

I went over the boot log and the relevant error lines are as follows:
-Failed to start PVE API Daemon (pvedaemon.service exits with status 255/EXCEPTION)

• Failed to start PVE API Proxy Server

The mentioned errors show up multiple times on the boot log, as I assume it's trying to start those services again after the errors.

I made a fresh 6.2-1 install and ran the commands again, and still got the same results - PVE API Daemon fails to start and webUI is no longer reachable, so the error can be reproduced as such

@AABatteries I have just tried running this Gist on a clean 6.2-1 install and had no problems. I ran a full apt upgrade -y and reboot the server. It came up with 6.3-3. It might be worth trying again.

Hi, I am starting with Proxmox and following the tutorial from DrZzs.
But i get this error when i try to remove the nag:
ll proxmox-widget-toolkitroot@DockerLXC:~# apt --reinstall install proxmox-widget-toolkit Reading package lists... Done Building dependency tree... Done E: Unable to locate package proxmox-widget-toolkit

And the nag is still present.
I am using the latest version of Proxmox, 6.3-3
Any idea what i can do to solve the nag?

EDIT: BTW, This is my pve-no-enterprise.list:
root@DockerLXC:~# cat /etc/apt/sources.list.d/pve-no-enterprise.list
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

Did a fresh install of Proxmox and followed the steps in the script, but the nag remains present...

@deltabert Did you clear the cookies from the browser after you ran the script? You can try using private/incognito mode of your browser to help test proper functionality. I just install PVE 6.3 ISO and tested this commands above and all works as expected.

Hello everyone I have a little insight that might help I have installed proxmox more that 6 times on a new server over last few days. I have found that if I install fresh proxmox DO NOT UPDATE it from the list on the left hand side just use this script before any thing else. It worked every time if I used the update from the list on the left under proxmox the updates then using this repository failed every time. I also think if you have a fresh install and install a couple of OS's that can cause it to fail can not remember if it did or not. These are my findings only and are from my R720 server your mileage may vary and as always do your own research to confirm

Thanks Whiskerz007 @6.4

Has anyone tested this after upgrading to 7.0?

Edit
Did not work for me..... but I don't guarantee my own work.

I had this patch applied and working before upgrading to 7.0, still working afterwards, no nags on my end.

Not a clue if it works on a fresh install.

It started working for me, too. I guess it was a browser cache issue.

Working fine on 7.1-7

Using these commands posted, then issuing
apt upgrade -y
and rebooting, Proxmox 7.1-7 updated to 7.1-12 no issues! Thanks!

The commands above worked for me on Proxmox version 7.2-3
Oh, I rebooted the node, not sure I had to though.
thank you very much

Works on 7.2-7
But after
apt upgrade -y

root@pve:~# dpkg -V proxmox-widget-toolkit | grep -q '/proxmoxlib\.js$'; echo $?                        
1
root@pve:~# apt policy proxmox-widget-toolkit
proxmox-widget-toolkit:
  Installed: 3.5.5
  Candidate: 3.5.5
  Version table:
 *** 3.5.5 500
        500 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 Packages
        100 /var/lib/dpkg/status

what hell going on ?
BTW, there are many way to getting rid nag message. I've been writing some of them, in here

Regards

On Proxmox 8.0 need to add this after line 2 in gistfile1.txt above:
sed -i "s/^deb/\#deb/" /etc/apt/sources.list.d/ceph.list

Just wanted to stop and say thanks!