Proxmox initial setup annoyances

black3dynamite

The git repo is from someone else. But the pve-nag-buster script hasn't been updated with the fix for NAGTOKEN variable.

pve-nag-buster make changes to the data.status while the one from John McLaren changes Ext.Msg.show

JaredBusch

@black3dynamite said in Proxmox initial setup annoyances:

The git repo is from someone else. But the pve-nag-buster script hasn't been updated with the fix for NAGTOKEN variable.

pve-nag-buster make changes to the data.status while the one from John McLaren changes Ext.Msg.show

When I reinstalled everything today, I looked at the github.

That also fixes the repo as well as the nag (minus the current bug).

VoIP_n00b

I've always just dealt with the nag screen. I guess I'll have to give this a shot.

JaredBusch

So with the git repo method, immediately after installing PM...
Even before opening the web console the first time..
Hit up ssh as root.

apt update # you will get an error because of the enterprise repo. ignore it.
apt install git -y
git clone https://github.com/foundObjects/pve-nag-buster.git
cd pve-nag-buster && ./install.sh

# as of this writing, there is a bug in the git repo. so fix it.
sed -i 's/NAGTOKEN="data.status !== \x27Active\x27"/NAGTOKEN="data.status.toLowerCase() !== \x27active\x27"/g' /usr/share/pve-nag-buster.sh
bash /usr/share/pve-nag-buster.sh

# now update the system
apt update && apt dist-upgrade -y

# then reboot.
reboot

Now you have a clean install, fully updated and not nagging you.

VoIP_n00b

@JaredBusch Thanks!

Dashrender

@JaredBusch said in Proxmox initial setup annoyances:

So with the git repo method, immediately after installing PM...
Even before opening the web console the first time..
Hit up ssh as root.

apt update # you will get an error because of the enterprise repo. ignore it.
apt install git -y
git clone https://github.com/foundObjects/pve-nag-buster.git
cd pve-nag-buster && ./install.sh

# as of this writing, there is a bug in the git repo. so fix it.
sed -i 's/NAGTOKEN="data.status !== \x27Active\x27"/NAGTOKEN="data.status.toLowerCase() !== \x27active\x27"/g' /usr/share/pve-nag-buster.sh
bash /usr/share/pve-nag-buster.sh

# now update the system
apt update && apt dist-upgrade -y

# then reboot.
reboot

Now you have a clean install, fully updated and not nagging you.

you should make your git for this, fewer steps for people

JaredBusch

@Dashrender said in Proxmox initial setup annoyances:

you should make your git for this, fewer steps for people

The owner of the above repo has not updated the repo in 11 months. The "issue" has only been hanging around since November 10th.

I know that issues posted to my github are not immediately noticed by me. Because I have email turned off. So not blaming this guy.

VoIP_n00b

This post is deleted!

JaredBusch

The noted repo has been updated.

The "fix" is no longer required.

It also still works on ProxMox 7.0.0

apt update # you will get an error because of the enterprise repo. ignore it.
apt install git -y
git clone https://github.com/foundObjects/pve-nag-buster.git
cd pve-nag-buster && ./install.sh

# now update the system
apt update && apt dist-upgrade -y

# then reboot.
reboot

marcinozga

You may have to clear browser cache to fully get rid of the nag. Mine kept coming back, clearing caches got rid of it.

JaredBusch

@marcinozga said in Proxmox initial setup annoyances:

You may have to clear browser cache to fully get rid of the nag. Mine kept coming back, clearing caches got rid of it.

I run this prior to ever opening the web interface, so never an issue.