Connecting a FUYL Locker to the FUYL Portal may require technical knowledge of your organization’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 FUYL Portal. 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 | 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 | UDP 123 | ntp |
Note: While these are the destination domains that the FUYL Locker requests, they are load and regionally balanced in AWS, so can resolve to different IPs over time. We therefore recommend whitelisting all outbound TCP traffic over 8883 from the locker's local addresses!