JSC HTTPS connection fails due to "ERROR - 4013: Could not resolve Gateway IP address"

JSC clients cannot establish HTTPS connection to the SRX due to "ERROR - 4013: Could not resolve Gateway IP address"

In case JSC clients cannot reach the SRX due to "ERROR - 4013: Could not resolve Gateway IP address" note that this message is displayed when the client is not able to resolve the domain that it is trying to reach, in this case make sure the domain can actually be resolved (from the Windows CMD or a Linux shell).

If the current DNS server is not able to resolve this domain or if there is no reachability to the DNS server then consider using a different private or public DNS server.

If the following conditions are met consider deactivating the JSC config, committing and activating the configuration back:

• The DNS server is reachable
• The DNS server can resolve the domain and retrieve the response to the client
• The SRX's external interface uses dynamic IP addressing
• The PKI certificate used for the HTTPS connection has the Fully Qualified Domain Name (FQDN) on the Alternate Subject Name of the certificate
• The service stopped working after rebooting the SRX

The JSC related configuration that needs to be deactivated includes the IKE gateway, IKE policy, IKE proposal, IPsec policy, IPsec proposal, IPsec vpn, DHCP pool, access profile and security remote-access configuration.