ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Proxmox initial setup annoyances

    IT Discussion
    proxmox proxmox 6.3 proxmox ve
    5
    16
    1.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • black3dynamiteB
      black3dynamite
      last edited by black3dynamite

      If there is an update to proxmox-widget-toolkit you will end up needing to run that script again because proxmoxlib.js will be replaced.

      You can confirm it by running this: apt --reinstall install proxmox-widget-toolkit

      You could create a dpkg post install hook script that will remove the license nag after each update. Or use the one provided at https://github.com/foundObjects/pve-nag-buster.

      But the last time I used it, the variable, NAGTOKEN="data.status.toLowerCase() !== 'Active'" need to be change to NAGTOKEN="data.status.toLowerCase() !== 'active'"
      https://github.com/foundObjects/pve-nag-buster/issues/3

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @black3dynamite
        last edited by

        @black3dynamite said in Proxmox initial setup annoyances:

        If there is an update to proxmox-widget-toolkit you will end up needing to run that script again because proxmoxlib.js will be replaced.

        You can confirm it by running this: apt --reinstall install proxmox-widget-toolkit

        That is all on the blog. I wasn't reposting his blog.

        black3dynamiteB JaredBuschJ 2 Replies Last reply Reply Quote 0
        • black3dynamiteB
          black3dynamite @JaredBusch
          last edited by

          @JaredBusch said in Proxmox initial setup annoyances:

          @black3dynamite said in Proxmox initial setup annoyances:

          If there is an update to proxmox-widget-toolkit you will end up needing to run that script again because proxmoxlib.js will be replaced.

          You can confirm it by running this: apt --reinstall install proxmox-widget-toolkit

          That is all on the blog. I wasn't reposting his blog.

          My bad.

          1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @JaredBusch
            last edited by

            @JaredBusch said in Proxmox initial setup annoyances:

            @black3dynamite said in Proxmox initial setup annoyances:

            If there is an update to proxmox-widget-toolkit you will end up needing to run that script again because proxmoxlib.js will be replaced.

            You can confirm it by running this: apt --reinstall install proxmox-widget-toolkit

            That is all on the blog. I wasn't reposting his blog.

            Is this git by someone else?

            I didn't look at that. Maybe his would be the answer because he says it works form 5.x to current.

            1 Reply Last reply Reply Quote 0
            • black3dynamiteB
              black3dynamite
              last edited by 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

              JaredBuschJ 1 Reply Last reply Reply Quote 1
              • JaredBuschJ
                JaredBusch @black3dynamite
                last edited by

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

                1 Reply Last reply Reply Quote 0
                • V
                  VoIP_n00b
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch
                    last edited by

                    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.

                    V DashrenderD 3 Replies Last reply Reply Quote 2
                    • V
                      VoIP_n00b @JaredBusch
                      last edited by

                      @JaredBusch Thanks!

                      1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @JaredBusch
                        last edited by

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

                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch @Dashrender
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • V
                            VoIP_n00b @JaredBusch
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch
                              last edited by 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
                              M 1 Reply Last reply Reply Quote 3
                              • M
                                marcinozga @JaredBusch
                                last edited by

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

                                JaredBuschJ 1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @marcinozga
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • JaredBuschJ JaredBusch marked this topic as a question on
                                  • JaredBuschJ JaredBusch has marked this topic as solved on
                                  • 1 / 1
                                  • First post
                                    Last post