Hostname(s) | IP Address | Usage |
second-tier-ca.zpecloud.com device-api.zpecloud.com device-apiv2.zpecloud.com | 35.233.194.48 (old) 34.49.235.253 (new) | Required to sign the CSR to connect to Remote Access. Required to Upload/Restore Backups. Required to upload output from executed profiles. |
api.astarte.zpecloud.com | 34.83.86.148 (old) 34.49.39.37 (new) | Required for Pairing API - without it, device is not able to authenticate against PubSub service and consequently connect to Cloud. |
access.zpecloud.com | 35.230.32.156 (old) 34.49.235.61 (new) | Required for Remote Access - without it, device is not able to connect to Remote Access socket. |
broker.astarte.zpecloud.com | 34.83.67.57 (old) 34.49.26.197 (new) | Required for Broker connection - without it, device is not able to connect to PubSub service and consequently connect to Cloud. |
proxy-access.zpecloud.com api.zpecloud.com | 34.83.37.8 (old) 34.120.236.72 (new) | Required for Enrollment. Required to SSO from Cloud to Nodegrid appliance; also needs to be enabled on the Nodegrid appliance under Security :: Authentication :: SSO. |
Hostname(s) | IP Address | Usage |
second-tier-ca.zpecloud.eu device-api.zpecloud.eu device-apiv2.zpecloud.eu | 34.107.16.100 (old) 34.128.171.100 (new) | Required to sign the CSR to connect to Remote Access. Required to Upload/Restore Backups. Required to upload output from executed profiles. |
api.astarte.zpecloud.eu | 34.107.15.10 (old) 34.49.228.213 (new) | Required for Pairing API - without it, device is not able to authenticate against PubSub service and consequently connect to Cloud. |
access.zpecloud.eu | 34.107.6.32 (old) 34.128.152.77 (new) | Required for Remote Access - without it, device is not able to connect to Remote Access socket. |
broker.astarte.zpecloud.eu | 34.107.54.54 (old) 34.36.11.79 (new) | Required for Broker connection - without it, device is not able to connect to PubSub service and consequently connect to Cloud. |
proxy-access.zpecloud.eu api.zpecloud.eu | 34.83.37.8 (old) 34.111.34.34 (new) | Required for Enrollment. Required to SSO from Cloud to Nodegrid appliance; also needs to be enabled on the Nodegrid appliance under Security :: Authentication :: SSO. |
Transition FAQ:
What will happen after September 13, 2024? Will the current IPs stop working? Is there any impact on the services?
After September 13, 2024, only the new IP addresses will be used for ZPE Cloud service. This change is automatic, and no action is needed on the Nodegrid device or ZPE Cloud side.
There will be no impact on services as long as firewalls are not blocking the new IP addresses.
Can I change my firewall whitelists now?
Yes, you can add the new IPs to your firewall whitelist now. Be sure to add the new IPs while keeping the existing ones in the firewall whitelist.
What business benefit does this offer to customers?
This change increases ZPE Cloud scalability and service availability, providing customers with a more reliable experience.
What happens if I don’t update my firewall whitelist?
If the whitelist is not updated, device access to ZPE Cloud will be blocked on September 13, 2024, until the new IP addresses are added.
If I don’t use firewall whitelists, do I need to take any action?
No action is required.
Are the new IPs currently active?
No, the new IPs will become active after September 13, 2024. However, it's advisable to add them to your whitelists in advance to ensure readiness for the transition.
Does this change require modification to Nodegrid configuration?
No, it does not require any modification to Nodegrid configuration.
Should you have any questions or concerns, please don't hesitate to reach out to our support team.