<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic license.api.paloaltonetworks.com returned with HTTP response code : 404 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/license-api-paloaltonetworks-com-returned-with-http-response/m-p/1242209#M125518</link>
    <description>&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;HI all, I am encountering an issue with the Palo Alto Networks VM-Series firewall (VM-SERIES-2, VM Mode) running on Amazon AWS with software version 11.1.10-h5. The error message is:&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Request made to the server "license.api.paloaltonetworks.com" returned with HTTP response code : 404.&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The device certificate is valid and correctly retrieved from the server. The license status shows "Never expired," and the API key certificate has been generated properly. Despite this, the license API call returns the 404 error.&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Has anyone experienced this? How can this be resolved?&lt;/P&gt;</description>
    <pubDate>Wed, 19 Nov 2025 11:20:35 GMT</pubDate>
    <dc:creator>MarcinKrasz</dc:creator>
    <dc:date>2025-11-19T11:20:35Z</dc:date>
    <item>
      <title>license.api.paloaltonetworks.com returned with HTTP response code : 404</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/license-api-paloaltonetworks-com-returned-with-http-response/m-p/1242209#M125518</link>
      <description>&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;HI all, I am encountering an issue with the Palo Alto Networks VM-Series firewall (VM-SERIES-2, VM Mode) running on Amazon AWS with software version 11.1.10-h5. The error message is:&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Request made to the server "license.api.paloaltonetworks.com" returned with HTTP response code : 404.&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The device certificate is valid and correctly retrieved from the server. The license status shows "Never expired," and the API key certificate has been generated properly. Despite this, the license API call returns the 404 error.&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Has anyone experienced this? How can this be resolved?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 11:20:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/license-api-paloaltonetworks-com-returned-with-http-response/m-p/1242209#M125518</guid>
      <dc:creator>MarcinKrasz</dc:creator>
      <dc:date>2025-11-19T11:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: license.api.paloaltonetworks.com returned with HTTP response code : 404</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/license-api-paloaltonetworks-com-returned-with-http-response/m-p/1242213#M125519</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/319789"&gt;@MarcinKrasz&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-path-to-node="5"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;I have seen this behavior before when there was a License and Serial Number Mismatch.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="8"&gt;The HTTP 404 from the licensing server occured because the Firewall GUI Serial Number&amp;nbsp;'xyz' didn't match the Registered Serial Number&amp;nbsp;(abc) that holds your active subscription entitlements.&lt;/P&gt;
&lt;P data-path-to-node="9"&gt;In my experience, this scenario typically arises when:&lt;/P&gt;
&lt;UL data-path-to-node="10"&gt;
&lt;LI&gt;
&lt;P data-path-to-node="10,0,0"&gt;A VM-Series firewall is provisioned using a license token that was already consumed or incorrectly mapped.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="10,1,0"&gt;A VM image was cloned or redeployed without properly clearing the previous license configuration, leading to the device adopting an unrecognized serial number.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-path-to-node="11"&gt;Since the licensing server cannot find any active entitlement associated with the serial number the VM is presenting, it returns "404 Not Found."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="13"&gt;If you are hitting this issue, it cannot be fixed via configuration on the firewall itself. The entitlements must be re-mapped on the backend.&lt;/P&gt;
&lt;P data-path-to-node="14"&gt;Please contact support. You will need to provide them with the following information to facilitate the backend fix:&lt;/P&gt;
&lt;OL start="1" data-path-to-node="16"&gt;
&lt;LI&gt;
&lt;P data-path-to-node="16,0,0"&gt;The Correct/Registered Serial Number&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P data-path-to-node="16,1,0"&gt;The Incorrect/GUI Serial Number&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P data-path-to-node="17"&gt;TAC will be able to disassociate the subscriptions from the incorrect serial number and re-map them to the correct one. Once they confirm the fix, a simple &lt;EM&gt;request license fetch&lt;/EM&gt; command on the firewall will resolve the 404 error, and the GUI serial number should update.&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;If you're hitting a different issue then try&amp;nbsp;&lt;SPAN&gt;restarting the management server using the command &lt;EM&gt;debug software restart process management-server&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;Also confirm the follwoing:&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&lt;SPAN&gt;Please verify that the firewall can resolve the DNS name &lt;/SPAN&gt;&lt;A href="http://license.api.paloaltonetworks.com/" target="_blank" rel="noopener" data-aura-rendered-by="1224:36854;a"&gt;license.api.paloaltonetworks.com&lt;/A&gt;&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&lt;SPAN&gt;Verify that the firewall is not blocking traffic to &lt;/SPAN&gt;&lt;A href="http://license.api.paloaltonetworks.com/" target="_blank" rel="noopener" data-aura-rendered-by="1224:36854;a"&gt;license.api.paloaltonetworks.com&lt;/A&gt;&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&lt;SPAN&gt;Verify that the firewall has the correct time and date&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&lt;SPAN&gt;Kind regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-path-to-node="17"&gt;&lt;SPAN&gt;-Kim.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 12:15:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/license-api-paloaltonetworks-com-returned-with-http-response/m-p/1242213#M125519</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2025-11-19T12:15:33Z</dc:date>
    </item>
  </channel>
</rss>

