Connecting a FUYL Locker to the PC Locs Cloud may require technical knowledge of your organisation’s network configuration.
You can find the locker's MAC addresses on a printed sticker behind the control door and on the locker's packaging.
When onboarding a FUYL Locker, it will attempt to create an outgoing network connection to contact the PC Locs Cloud. The following ports and protocols may need to be whitelisted if your firewall restricts outgoing connections.
| Address | Port | Protocol |
|---|---|---|
| pclocs-firmware-updates-869893548898.s3.us-west-2.amazonaws.com | TCP 443 | https |
| registry.pclocs.io/registry.lockncharge.io | TCP 443 | https |
| a136cfw17adicb-ats.iot.us-west-2.amazonaws.com | TCP 8883 | mqtt |
| a136cfw17adicb-ats.iot.us-east-2.amazonaws.com | TCP 8883 | mqtt |
| a136cfw17adicb-ats.iot.eu-west-2.amazonaws.com | TCP 8883 | mqtt |
| a136cfw17adicb-ats.iot.ap-southeast-2.amazonaws.com | TCP 8883 | mqtt |
| time1.google.com, time2.google.com, time3.google.com, time4.google.com, 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org | UDP 123 | ntp |
Note: The destination domains listed here are load and region balanced within AWS, meaning they may resolve to different IP addresses over time. In addition, some firewalls perform a reverse DNS (PTR) lookup on the resolved IP and may match it against a different AWS FQDN than the one originally requested, which can cause traffic to be blocked if only our listed FQDN has been permitted.
To ensure reliable connectivity, we recommend allow-listing *.amazonaws.com or, ideally, permitting all outbound TCP traffic on port 8883 from the locker's local IP address.