To avoid any connectivity issues to Zeplin from your network, make sure that all zeplin.io domains are allowlisted:

zeplin.io -> main domain
app.zeplin.io -> Zeplin's Web app
api.zeplin.io -> Zeplin's main API
img.zeplin.io -> Zeplin's image scaling and optimizing service
scene.zeplin.io -> Zeplin's public sharing Web app
public.zeplin.io -> Zeplin's public sharing API
pusher.zeplin.io → Zeplin’s real time(socket) service
ext.zeplin.io -> Zeplin's extension service
pkg.zeplin.io -> Zeplin's Windows app and extension distribution service
cdn.zeplin.io -> Zeplin's content delivery network
email.zeplin.io -> Zeplin's email service
zpl.io -> Zeplin's short link service
zeplin.s3-accelerate.amazonaws.com -> Zeplin's image upload service
api.mobile.azure.com -> Zeplin's macOS app distribution service
api.appcenter.ms -> Zeplin's macOS app distribution service
*.appcenter.ms -> Zeplin's macOS app distribution service

For real-time (socket) connectivity issues, make sure that the HTTPS port is open.

You can test your connection using the following diagnostic tools:

Allowlisting IP Addresses

Allowlisting IP addresses can be problematic since Zeplin actually does not use static IPs and shared IPs may change without notice.

However, if your system only works with IPs, you can try allowlisting AWS's IP ranges for Zeplin: us-west-1 and us-west-2, and us-east-1 regions.

You can find more details and a JSON list of AWS’s IP ranges here:

Keywords: allow list, block list, whitelist, white list

Did this answer your question?