<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>proxmoxlib.js on Andrew Beaton</title>
    <link>https://andrewbeaton.net/tags/proxmoxlib.js/</link>
    <description>Recent content in proxmoxlib.js on Andrew Beaton</description>
    <image>
      <title>Andrew Beaton</title>
      <url>https://andrewbeaton.net/me.jpeg</url>
      <link>https://andrewbeaton.net/me.jpeg</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 29 Sep 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://andrewbeaton.net/tags/proxmoxlib.js/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remove Proxmox 5.4 &#34;No Valid Subscription&#34; message</title>
      <link>https://andrewbeaton.net/posts/2019/09/proxmox-no-valid-subscription/</link>
      <pubDate>Sun, 29 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://andrewbeaton.net/posts/2019/09/proxmox-no-valid-subscription/</guid>
      <description>Remove Proxmox 5.4 &amp;#34;No Valid Subscription&amp;#34; message</description>
      <content:encoded><![CDATA[<p>If, like me, you are using Proxmox in your Homelab, it can get a bit annoying to see the “No valid Subscription” message, every time you log in.</p>
<p>Purchasing a subscription from Proxmox is certainly recommended if you’re planning to use it in anger or in a production environment as it will give you access to support, the enterprise repository and keep the developers supported.</p>
<p>But for a test environment, you can remove the message by simply editing one of the JavaScript files on the server.</p>
<p>This file does get overwritten when you update, so you will need to reapply when that happens.</p>
<h2 id="detailed-approach">Detailed Approach</h2>
<pre tabindex="0"><code>cd /usr/share/javascript/proxmox-widget-tookit
cp proxmoxlib.js proxmoxlib.js.old
vi proxmoxlib.js
</code></pre><p>Search for Active until you find it in the following line:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-JavaScript" data-lang="JavaScript"><span style="display:flex;"><span><span style="color:#66d9ef">if</span> (<span style="color:#a6e22e">data</span>.<span style="color:#a6e22e">status</span> <span style="color:#f92672">!==</span> <span style="color:#e6db74">&#39;Active&#39;</span>) {
</span></span></code></pre></div><p>And change it to:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-JavaScript" data-lang="JavaScript"><span style="display:flex;"><span><span style="color:#66d9ef">if</span> (<span style="color:#66d9ef">false</span>) {
</span></span></code></pre></div><p>Save the file and exit. Now restart the service to load the updated file:</p>
<pre tabindex="0"><code>systemctl restart pveproxy.service
</code></pre><h2 id="one-liner-approach">One Liner Approach</h2>
<pre tabindex="0"><code>sed -i.bak &#34;s/data.status !== &#39;Active&#39;/false/g&#34; /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js &amp;&amp; systemctl restart pveproxy.service
</code></pre><p>Even if you are feeling brave, I would recommend that you take a backup of proxmoxlib.js file before running the above command, just to be safe.</p>
]]></content:encoded>
    </item>
    
  </channel>
</rss>
