How to test connectivity to updates.paloaltonetworks.com from the CLI?
1319
Created On 01/21/26 00:40 AM - Last Modified 03/06/26 20:52 PM
Objective
- To verify that the firewall’s management plane can successfully reach the Palo Alto Networks Update Server via HTTPS.
- Successful connectivity ensures the firewall can download the software, dynamic updates (Antivirus, Apps & Threats), and WildFire signatures.
Environment
- Next-Gen Firewalls or Panorama
- Supported PAN-OS
Procedure
- Log in to the firewall CLI via SSH.
- Enter the following command to test the HTTPS connection to the update cloud:
test http-server protocol HTTPS address updates.paloaltonetworks.com
- Analyze the Results:
- Success: If the output displays
Connection to: https://updates.paloaltonetworks.com:443 succeeded,the firewall has reachability and can perform the SSL handshake. - Failure: If the command returns a timeout or connection refused, proceed to verify DNS settings and Security Rules for the Management Interface.
- Success: If the output displays
- If you need to test the connection on a specific port, you can add the port argument:
test http-server port 443 protocol HTTPS address updates.paloaltonetworks.com
Additional Information
- The command is used when the firewall is failing to download updates. It is more effective than a standard ping for several reasons:
- Bypasses ICMP Restrictions: Many networks block ping (ICMP), but allow HTTPS (Port 443). If a ping fails, this command helps determine if the actual web service is still reachable.
- Verifies SSL Handshake: It confirms that the firewall can negotiate a secure connection, ensuring there are no certificate or protocol version mismatches.
- Tests Management Connectivity: It specifically tests the path from the Management Interface (or whichever Service Route is configured for updates) to the internet.
- Service Routes: By default, this traffic goes out of the Management (MGT) interface. If your environment uses a data port for updates, ensure the Service Route is configured correctly under Device > Setup > Services.
- DNS Dependency: This command relies on the firewall's ability to resolve FQDNs. If the test fails immediately, check DNS resolution using: ping host updates.paloaltonetworks.com
- Common Ports: This command defaults to port 443.
- Ensure that the perimeter firewall (if this unit is behind another one) allows traffic from the MGT IP to the internet on port 443.