Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
How to setup a community version of Proxmox VE 5.x-6.x
# 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
@Tollbringer
Copy link

Tollbringer commented Sep 27, 2019

Yes- I have used this gist more than 40 times (many, many Proxmox testing re-installs) and it works. Occasionally I do see one more nag, clearing cookies, clearing browser and rebooting definitely clears this up every time.

Glad you got it working. I know Whiskerz007 made changes a while ago to make sure the nag removal was persistent across all updates. In the prior revision it could sometimes be disabled, but this seems to have been corrected with his changes some time ago.

[-=SrZ=-]

@waynerigley
Copy link

waynerigley commented Dec 15, 2019

Just tried to remove the nag, on Dec 15 2019, does not work

@DavidFW1960
Copy link

DavidFW1960 commented Dec 16, 2019

Trying to run a shell in the GUI and I get this error:

main.js?version=3.13.2-1:129 WebSocket connection to 'wss://proxmox.fritz.box:8006/api2/json/nodes/proxmox/vncwebsocket?port=5900&vncticket=PVEVNC%3A5DF7EA33%3A%3AyuzX4b0Onp%2FoTrw6KYa9vJuwdt7uiShncb5z%2FSDN3q0FNLp0HyJGo0JZ23RHxmYlOiDzu0y2tr%2FulzvKcfIPXo5tyfho%2FcDHM1CqV6s2GZS7v2vf7PmVJ1h7OH0t9ZE0gk%2FCLn0eXuRlzar7tTqM9Ws%2Bghefj9Uzf2s4xSxNhggk7N0KG%2BR2UPH%2Bg6BURMZkpOR%2BQHm5nyOvwFGbItGBiANlEwOX%2BPpM9BzocNS6uiO%2F4JMj6nmQN2%2Be%2FKWIKUCR6Fbddlnjs1lYQ%2BJwSE7%2FlLt0zO0%2FB%2BVDA%2B%2FS3jHD7aw0INpsH6OhKHOyFlS3N9dY1eXySJ5vLJ6F66GqhUPJXg%3D%3D' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

I did get the nag removed using

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

@Tollbringer
Copy link

Tollbringer commented Dec 16, 2019

Thanks for sharing; My Proxmox is uptodate with the nag removal continuing to be persistent. I'll have a look into this (w/Whiskerz007) and see what we can come up with. TY.

Tollbringer

@HFeenstra
Copy link

HFeenstra commented Dec 24, 2019

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

@Tollbringer
Copy link

Tollbringer commented Dec 27, 2019

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

@Smitty357
Copy link

Smitty357 commented Dec 29, 2019

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.

@jamman9000
Copy link

jamman9000 commented Jan 27, 2020

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".

@Actpohomoc
Copy link

Actpohomoc commented Feb 12, 2020

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

@beng8857
Copy link

beng8857 commented Feb 15, 2020

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

@Shannondalebreaux
Copy link

Shannondalebreaux commented Apr 11, 2020

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.

@whiskerz007
Copy link
Author

whiskerz007 commented Apr 11, 2020

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

@beng8857
Copy link

beng8857 commented Apr 11, 2020

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.

@basnijholt
Copy link

basnijholt commented May 21, 2020

This still worked for 6.2 🎉

@midnitezone
Copy link

midnitezone commented Jul 11, 2020

works perfect, great work!

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

@invalidoz
Copy link

invalidoz commented Jul 13, 2020

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

@manubuhay
Copy link

manubuhay commented Aug 2, 2020

verified, script works on build 6.2-4

@AABatteries
Copy link

AABatteries commented Nov 15, 2020

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

@whiskerz007
Copy link
Author

whiskerz007 commented Dec 26, 2020

@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.

@deltabert
Copy link

deltabert commented Jan 20, 2021

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

@deltabert
Copy link

deltabert commented Jan 21, 2021

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

@whiskerz007
Copy link
Author

whiskerz007 commented Jan 22, 2021

@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.

@rottison
Copy link

rottison commented Apr 20, 2021

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

@BigMassive
Copy link

BigMassive commented May 28, 2021

Thanks Whiskerz007 @6.4

@Justahobby01
Copy link

Justahobby01 commented Jul 25, 2021

Has anyone tested this after upgrading to 7.0?

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

@towerhand
Copy link

towerhand commented Jul 26, 2021

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.

@Justahobby01
Copy link

Justahobby01 commented Jul 27, 2021

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

@scottmando2000
Copy link

scottmando2000 commented Dec 31, 2021

Working fine on 7.1-7

@Phone-guy
Copy link

Phone-guy commented Apr 25, 2022

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

@Compukid
Copy link

Compukid commented Jun 28, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment