When attempting to stage a new image to a managed SRX device using Security Director Cloud, the process fails with connectivity-related errors.
Error message:
Reason rpc curl failed, reason: curl: (28) Failed to connect to cdn.juniper.net port 443 after 75054 ms: Couldn't connect to serverrpc <file-copy/> failed, reason: File-fetch failed File fetch failed
/cf/var/tmp:
drwx------ 2 sduser wheel 512 Apr 15 16:03 ...transferring.file.........2cAwea/
drwx------ 2 sduser wheel 512 Apr 15 15:53 ...transferring.file.........9IhFQ8/
drwx------ 2 sduser wheel 512 Apr 15 16:26 ...transferring.file.........MjLXoT/
drwx------ 2 sduser wheel 512 Apr 15 15:43 ...transferring.file.........aEKdji/
Cause: The error indicates a connectivity issue between the SRX devices and the Security Director Cloud portal. The devices are unable to establish HTTPS connections required for image staging.
Troubleshoot to check connectivity from the affected SRX device to the Security Director Cloud portal:
1. Verify Internet Connectivity
Ensure the SRX device can reach the Internet:
> ping 8.8.8.8
2. Confirm required Ports are Open on the affected device:
During staging, Security Director Cloud uses curl over HTTPS (port 443). The following ports must be open:
Test connectivity:
> telnet srx.sdcloud.juniperclouds.net port 7804
> telnet srx.sdcloud.juniperclouds.net port 443
Expected output:
telnet srx.sdcloud.juniperclouds.net port 443
Trying <SDC-IP>..
Connected to srx.sdcloud.juniperclouds.net.
Escape character is '^]'.
^CConnection closed by foreign host.
3. Check for Local Filters
Verify that no firewall filters or security policies on the SRX device or local Network are blocking outbound/inbound traffic to the Security Director Cloud portal.
4. Enable Netconf Traceoptions
For deeper diagnostics, enable Netconf traceoptions:
set system services netconf traceoptions file jtac-netconf-trace
set system services netconf traceoptions file size 10m
set system services netconf traceoptions file files 3
set system services netconf traceoptions flag all
Trace logs may show errors such as:
Apr 15 17:37:23 [NETCONF] - [21985] Incoming: <?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><capabilities><capability>urn:ietf:params:netconf:base:1.0</capability></capabilities></hello>]]>]]><?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="Job-ID" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><file-delete><path>/var/tmp/junos-srxsme-23.4R2-S7.4.tgz</path></file-delete></rpc>]]>]]>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos=http://xml.juniper.net/junos/23.4R2-S6.9/junos message-id="Job-ID">
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:rpc-error>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:error-type>protocol</nc:error-type>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:error-tag>operation-failed</nc:error-tag>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:error-severity>error</nc:error-severity>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <nc:error-message>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: No such file or directory
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: </nc:error-message>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: </nc:rpc-error>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: </nc:rpc-reply>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: ]]>]]>
Apr 15 17:37:23 [NETCONF] - [21985] Incoming: Received ']]>]]>' token which is split in two consecutive streams or has leading/trailing spaces/tabs or both.
<rpc message-id="944611ed-53ba-44dd-8fdc-434643f197fa" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><request-shell-execute><command>curl https:.... --output /var/tmp/junos-srxsme-23.4R2-S7.4.tgz --insecure --no-keepalive</command></request-shell-execute></rpc>]]>]]>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: <output>
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: % Total % Received % Xferd Average Speed Time Time Time Current
Apr 15 17:37:23 [NETCONF] - [21985] Outgoing: Dload Upload Total Spent Left Speed
Apr 15 17:42:23 [NETCONF] - [21985] Outgoing:
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
….
0 0 0 0 0 0 0 0 --:--:-- 0:01:55 --:--:-- 0
0
Apr 15 17:42:23 [NETCONF] - [21985] Outgoing: curl: (28) Failed to connect to <SDC URL> port 443 after 300318 ms: Couldn't connect to server
Apr 15 17:42:23 [NETCONF] - [21985] Outgoing: </output>
Apr 15 17:42:23 [NETCONF] - [21985] Outgoing: </nc:rpc-reply>
Apr 15 17:42:23 [NETCONF] - [21985] Outgoing: ]]>]]>
Apr 15 17:42:23 [NETCONF] - [21985] Incoming: Received ']]>]]>' token which is split in two consecutive streams or has leading/trailing spaces/tabs or both.
Apr 15 17:42:24 [NETCONF] - [21985] Outgoing: <!-- session end at 2026-04-15 17:42:24 MDT -->
If the issue persists after confirming connectivity, contact HPE Juniper Support for further assistance.