Remove the Proxmox “No Valid Subscription” message
Category : How-to
Proxmox 3.1 has implemented a new repository setup, as described in my recent blog post.
Each time you log into Proxmox 3.1 a dialogue box pops up with the message:
You do not have a valid subscription for this server. Please visit www.proxmox.com to get a list of available options.
One way to remove the message is to purchase a subscription from the Proxmox team. Remember that paying subscriptions keeps the development of Proxmox progressing. For the recent release, the subscription cost has been heavily reduced and is more affordable than ever.
The fact of the matter is, I started using Proxmox as a free and open source tool and expected it to stay that way. Had I known a subscription element would have been introduced, I would likely have chosen another toolset. As it is, I am too invested in Proxmox (time-wise) and changing to another technology is simply out of the question at this point. This brings me onto the other method; make a slight change to the code to remove the dialogue box from appearing. This is allowed under the License (aGPLv3) used for Proxmox however future updates may break your code and you may have to re-apply it or apply a different change.
You will need SSH access to the Proxmox host with the required access to edit the pvemanagerlib.js file.
First, take a backup of the file:
cp /usr/share/pve-manager/ext4/pvemanagerlib.js /usr/share/pve-manager/ext4/pvemanagerlib.js_BKP
Then open the file using a text editor, vi for example.
vi /usr/share/pve-manager/ext4/pvemanagerlib.js
Currently on line 519 of the file, however it may change with future updates, there is a line similar to below;
if (data.status !== 'Active') {
This line is doing the check to see if your subscription status is not ‘Active’. This needs to be changed to return false to stop the subscription message from being shown.
if (false) {
And that annoying little popup will be a thing of the past!
Note: You may need to clear your web browser cache after applying this code change.
I have added this code to my Proxmox patch – see this blog post for more information.
64 Comments
David
16-Sep-2013 at 10:48 pmThx James,
Your trick did it. No more annoying popup :)
Sad to see yet another opensource project go commercial.
David
16-Sep-2013 at 11:10 pmYou’re also right about updates: the patch to the .js file needs to be re-applied after running update/upgrade.
Keith
17-Sep-2013 at 6:15 pmI editted the file and saved……I even rebooted….but I still get the message when I login to the ProxMox web manager.
Could something have changed that this edit/hack no longer works?
Thanks.
Keith
Keith
17-Sep-2013 at 6:23 pmDisregard my previous comment.
My cache (Firefox) had to be cleared.
It worked!
Thanks!
Keith
james.coyle
21-Sep-2013 at 8:20 pmThanks Keith, I have updated the article.
le_top
23-Sep-2013 at 5:14 pmFor the record, I initially posted the solution on the Proxmox forum on September 6th, but they removed the information indicating precisely what had to be changed:
http://forum.proxmox.com/threads/15987-HOWTO-Remove-popup-regarding-subscription-on-login?p=82385
The funny thing is that today a colleague (in another company) informed me about this change by sending me a link to this page.
So that’s proof that deleting it on the Proxmox forum did not make the information go away.
[I am not saying that James did not identify the same change by himself].
james.coyle
23-Sep-2013 at 6:10 pmHi le_top
I saw your thread on the Proxmox forum and all the controversy which ensued, including your link being removed which I could not find.
I don’t want to start a political debate on what’s right or wrong in these comments. Obviously for development to continue on Proxmox the developers need to be paid but for my circumstances I chose Proxmox because it was open and free. In my circumstances, if I had to pay for this software I would have to look for alternatives which itself is a problem as I have invested so much time in understanding Proxmox and developing my setup.
That’s why I looked at removing the irritating message. The trouble, of cause, is how well updates will apply since the code was changed.
We’ll just have to wait and see.
Nour
2-Oct-2013 at 6:12 pmwould you please attach the full content of the file as I accidentally removed the file with no backup!
james.coyle
2-Oct-2013 at 6:49 pmHi Nour,
Remember – bakup, bakup, bakup!
I have emailed you the file to the address in your comment. I have taken the file from one of my dev servers which I only currently have FTP access to and can’t be sure of the exact version.
Nour
2-Oct-2013 at 7:18 pmHi James,
Thank you very much, would you please compress the file and resend it as the email blocked the attachment ”
Warning Outlook has blocked some attachments in this message because they appear to be unsafe.
”
Best Regards
Jochen metzger
9-Oct-2013 at 2:29 pmHi guys,
here is a patch.
— /usr/share/pve-manager/ext4/pvemanagerlib.js_BKP 2013-10-09 16:23:11.000000000 +0200
+++ /usr/share/pve-manager/ext4/pvemanagerlib.js 2013-10-09 16:24:49.000000000 +0200
@@ -447,7 +447,7 @@
success: function(response, opts) {
var data = response.result.data;
– if (data.status !== ‘Active’) {
+ if (false) {
Ext.Msg.show({
title: ‘No valid subscription’,
icon: Ext.Msg.WARNING,
Maybe that helps.
james.coyle
9-Oct-2013 at 2:36 pmHi Jochen,
The problem with a patch is that when Proxmox goes through updates the patch tends to stop working as lines are added and removed.
Raja
6-Nov-2013 at 3:55 pmHey Buddy !!! works Great.
Thank you so much.
nobody
26-Nov-2013 at 1:26 pmHere is a Sed one liner making backup and changes to the file:
# sed -i”_pve-manager_3.1-24″ ‘/^[ ,\t]*if (data.status !== ‘\’Active\”)/s/(data.status !== ‘\’Active\”)/(false)/’ /usr/share/pve-manager/ext4/pvemanagerlib.js
Thanks
james.coyle
26-Nov-2013 at 1:46 pmWhilst this might work to change the required line (I have not tested), it will also change any other lines which contain the same text.
Use this with caution.
Eric Osterberg
17-Jan-2014 at 9:02 pmOops, didn’t see your one liner before creating my own.
sed -i.bak -r -e “s/if \(data.status !== ‘Active’\) \{/if (false) {/” /usr/share/pve-manager/ext4/pvemanagerlib.js
kenny
20-Dec-2013 at 4:53 pmTried this and when I refresh the page I just get a white screen. Tried all the codes that have been posted above but nothing. If I delete the extra code then the login page is displayed. Any help?
james.coyle
20-Dec-2013 at 7:14 pmHi Kenny,
The details in the above post is accurate – I have just tested it on a fully updated Proxmox 3.1 test install. I opened the pvemanagerlib.js and did a search for data.status – the first instance you find is the row which you need to edit.
Did you clear your browser cache? I assume you don’t run the Proxmox interface through a caching reverse proxy as this could also cause issues?
Eric Osterberg
17-Jan-2014 at 8:59 pmHopefully this posts correctly…. Here’s a one liner that can do the job.
sed -i.bak -r -e “s/if \(data.status !== ‘Active’\) \{/if (false) {/” /usr/share/pve-manager/ext4/pvemanagerlib.js
Eric Osterberg
13-Aug-2014 at 2:36 pmThe forum here is changing the quotes, otherwise this works perfectly time and time again.
sisantha
24-Jan-2014 at 11:18 pmhi,
I’m new to this proxmox VE and running it for some weeks now.
thank you for the tip, and it works on my proxmox VE.
May I put another inquiry regarding to certificate problem with accessing the console on proxmox web admin site?
After upgrading Java it’s Certificate is not valid for access to console Applet.
How could I resolve this please?
Any help is much appreciated.
Regards,
Sisantha
Bob Henderson
29-Jan-2014 at 3:59 pmJava did this change, sadly, and I just needed to make it work on mine. These instructions are for a Windows client:
Pop into your control panel, and go to the Java option.
Go to the security tab, and at the bottom you’ll find an Exception site list. Put in the hostname or IP of your Proxmox box(es). Make sure to include the https:// as Java is picky.
Boom, you should be good to go.
I can’t wait for the day Proxmox puts in an HTML5 VNC viewer. I’m not a fan of anything that requires Java anymore.
james.coyle
29-Jan-2014 at 4:05 pmThanks Bob.
+1 for anything which removes the Java VNC.
DrWiza
5-Apr-2014 at 9:02 pmhow a procedure for 3.2?
james.coyle
6-Apr-2014 at 1:21 pmIt is exactly the same for Proxmox 3.2.
Johan
14-Apr-2014 at 8:59 amFree is not the same as gratis. In my opinion it is a perfectly fine move by Proxmox adding this “anti feature”. It is still free software and you are legally free to remove it by the method mentioned in this blog post. See it more like a reminder that you should pay for the support if you use it commercially. Though you are never obliged to do it.
This “hack” (possibly with slight adaptions) will always continue working.
newtesla
20-Jun-2014 at 11:24 amMaybe I am using newer version (3.1-21) but:
-this code is on line 454, and;
-I have easier solution – just
if (data.status !== 'Active') {turn into
if (data.status == 'Active') {yep, just erase exclamation mark ;) and, remember to type it back once you do have subscription, because this makes nagging inverted, ie. nagging when you DO have subscription, but NOT when you don’t :D
pmelon
11-Sep-2014 at 1:12 pmCan anyone verify newtesla’s fix? I’ll have a go later if nobody already has.
I used Proxmox for a LONG time and loved it. I was forced to switch to using vSphere in Nov last year but a new client/job prospect is leading me to look at virt solutions. It’s between Proxmox and Ovirt at the moment for me.
I’ve never been able to get Ovirt in a state where I can actually trust it… yet. Anyway, thanks for the post and all the commenters’ help too!
Felipe
18-Sep-2014 at 12:21 pmWork fine!
Thanks!
Babin Lonston
29-Sep-2014 at 6:53 amworked !!
Thanks for bulk of Proxmox articles.
GW
30-Jan-2015 at 1:51 amLooks like they added another condition which should probably be true. Sed accordingly :)
root@DEVNET-HOST:~# dpkg –list|grep pve-manager
ii pve-manager 3.3-1 amd64 The Proxmox Virtual Environment
root@DEVNET-HOST:~# cat -n /usr/share/pve-manager/ext4/pvemanagerlib.js|awk ‘/if \(data.status/’ 462 if (data.status !== ‘Active’) {
25647 if (data.status === ‘Active’) {
root@DEVNET-HOST:~#
markit
13-Feb-2015 at 3:17 pmWe are talking about freedom, not price.
You say you love Proxmox being Free (aGPL3) software, so do I. I always use Free software, the only one I can trust and that I have control on.
I’ve seen a lot of project with only Free “core” and the rest proprietary. Proxmox is great because you always have it at 100%, not a dumbed down version useful just for play and not for serious work.
Of course, if you want Proxmox be developed only on spare time, and have no support in the forum, and not a company that is able to support you if you deploy to enterprise, and the project eventually die in the future, keep with your tips about removing the message, is the way to go.
But you are damaging your future and mine, so I ask you to remove this (even if legal) tip, since you are hurting the project.
Proxmox is one of the best “freedom respecting” project I’ve seen, and the idea to get money from the “enterprise” repositories acces is realy briliant.
No hurt to the community (100% aGPL code), money only from who is probably getting money himself from proxmox deploy, if they want certified repos.
The “No Valid Subscription” message is there to remember you that: if you love this project, you should contribute to it.
It’s annual cost is really cheap, you should pay one just to support them.
And yes, they know that aGPL3 allows the message remove, and yes, they could have created a “proprietary core” that prevents this.
But no, they value freedom and respect the community, so they didn’t. They are fair people and you should be fair with them as well.
“I started using Proxmox as a free and open source tool and expected it to stay that way”, well, it is still Free and Open source, or you don’t understand Free software license? You mean “no cost”? It’s still “no cost”, so?
Do you prefer Proprietary VMWare, where you have NO control of the code, probably some trojan or spyweare or backdoor in the code, and you can have only a “no cost” partial version, with very high costs if you want a better one?
As I said, in addition to be moral unbecoming, it’s hurting the community, the project and so ME, that I’m enjoining this wonderful GPL3 project.
So please stop damaging the project and please stop using Proxmox and go to hurt something (proprietary this time, please) else!
winkyhub
15-May-2015 at 2:26 pmon my reading. is not about fredom or gratis or paying.
there is the way to remove nagging dialog and everyone can do that
if proxmox force with “closed source code” nagging dialog, many people will complain and this is vialotion of AGPL3 too :P
nagging message is permitted, this is up to the user to remove it or not:D
the main concern is, on proxmox forum, they delete on how to remove :nagging dialog:. this is no secret since js sourcecode can be easly scanned through,
JJHans
9-Oct-2015 at 11:29 amThat is so wrong in so many ways. What are you asking about is just censorship because you don’t like others to get information about an open source project.
Nobody spends money just because there is a pop-up. If you really need the support because you are using proxmox to earn money you will buy the subscription.
So please stop damaging freedom of speech and go to hurt something else!
Nunez
16-Sep-2015 at 2:40 pmHi James,
Thanks for the tip.
I am exactly in the same situation as you were except I was given an oportunity to change.
Since you seem to be aware of alternatives, what would you pick?
james.coyle
16-Sep-2015 at 3:58 pmIt depends on the use case :)
Docker is excellent, but not at everything. http://opennodecloud.com/ is quite good, OpenVZ with one of the web GUI’s, there are so many choices to choose from.
nuh
26-Jan-2016 at 10:04 amThank you.
Francisco Barcenas Cruz
20-Mar-2016 at 7:34 pmGreat tip. Would you know how to change the interface the PROXMOX bound to? I made the mistake of setting up my virtual ips before installing proxmox. now it’s bound to eth0:0 instead of eth0.
Jeff Moss
11-May-2016 at 7:04 amOn Proxmox 4.2 (just upgraded), that file to change is now in /usr/share/pve-manager/ext6/ instead of /usr/share/pve-manager/ext4/
james.coyle
11-May-2016 at 7:12 amThanks, Jeff.