Overview
Setting up the FUYL Smart Locker System may require technical knowledge and access to your organization’s network configuration.
FUYL™ Locker MAC addresses
You can find the locker's MAC addresses on a printed sticker behind the control door and on the locker's packaging.
If you have recently purchased FUYL Lockers and would like to be supplied with their MAC addresses prior to delivery, please complete this form.
FUYL™ Locker & FUYL™ Kiosk Firewall Requirements
When onboarding a FUYL™ Locker, it will attempt to create an outgoing network connection to contact the FUYL™ Enhanced service. We recommend allowing all outgoing traffic from the FUYL Locker and Kiosk over ports 443 & 8883.
At a minimum, however, the following ports and protocols will need to be allowed if your firewall restricts outgoing connections. For simplicity and to prepare for future updates, you may wish to use a *.fuyl.io wildcard.
| Destination | Source | Purpose | Protocol | Port |
|---|---|---|---|---|
| fuyl.io | Any device accessing FUYL Portal | FUYL Portal | HTTPS (TCP) | 443 |
| api.fuyl.io |
Any device accessing FUYL Portal FUYL Kiosk |
Comms with service | HTTPS (TCP) | 443 |
| auth.fuyl.io | FUYL Kiosk | ID & Barcode authentication | HTTPS (TCP) | 443 |
| reporting.fuyl.io |
Any device accessing FUYL Portal FUYL Kiosk |
Telemetry | HTTPS (TCP) | 443 |
| signing.fuyl.io |
Any device accessing FUYL Portal FUYL Kiosk |
Authentication page Redirects to SSO provider |
HTTPS (TCP) | 443 |
| admin.fuyl.io | Any device accessing FUYL Portal | Configure SSO & Provisioning | HTTPS (TCP) | 443 |
| auth-api.fuyl.io |
Any device accessing FUYL Portal FUYL Kiosk |
Authentication Service Briefly used during redirects |
HTTPS (TCP) | 443 |
| iot.fuyl.io | FUYL Tower | Tower comms | MQTTS (TCP) | 8883 |
| firmware.fuyl.io | FUYL Tower | Tower update | HTTPS (TCP) | 443 |
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 traffic over the specified ports from the locker's local addresses.