In rare cases, a failed previous fetch or a software bug can leave "stale" certificate fragments in the firewall's internal storage, blocking new generation attempts.
Note: For some TPM-specific devices, you may only need request certificate fetch without the OTP. 3. Advanced CLI Recovery In rare cases, a failed previous fetch or
If "TPM public key match failed" remains after trying the above, it usually requires Palo Alto TAC intervention. Support must often initiate a to gain root access to the device shell. This allows them to manually purge the invalid hardware-bound certificate files from the /opt/pancfg/mgmt/ssl/private/ directory, which is not accessible to standard admin users. Advanced CLI Recovery If "TPM public key match
set deviceconfig system setting management-interface-mtu 1374 Use code with caution. In rare cases
request certificate fetch request device-telemetry collect-now Use code with caution. Refresh the WebUI to check for a "Success" status.
In rare cases, a failed previous fetch or a software bug can leave "stale" certificate fragments in the firewall's internal storage, blocking new generation attempts.
Note: For some TPM-specific devices, you may only need request certificate fetch without the OTP. 3. Advanced CLI Recovery
If "TPM public key match failed" remains after trying the above, it usually requires Palo Alto TAC intervention. Support must often initiate a to gain root access to the device shell. This allows them to manually purge the invalid hardware-bound certificate files from the /opt/pancfg/mgmt/ssl/private/ directory, which is not accessible to standard admin users.
set deviceconfig system setting management-interface-mtu 1374 Use code with caution.
request certificate fetch request device-telemetry collect-now Use code with caution. Refresh the WebUI to check for a "Success" status.