Zyxel FWA series routers, such as the FWA505, FWA710, and FWA510, are modern 5G/LTE routers that support integration with the Nebula Cloud platform. While these devices are not fully managed via Nebula, they can be monitored and offer limited cloud-based features. This guide specifically references the FWA505, but the solutions provided are applicable to the other models in the FWA series as well.
Scenario: Device Offline in Nebula
- Internet connection is stable and working fine.
- SIM card is active and transmitting data.
- Device is added to the Nebula organization on nebula.zyxel.com.
- However, the device shows as Offline in the Nebula platform.
The example below is what the local status looks like when there are problems:
The example below is what the local status looks like when there is no problem:
Possible Causes and Solutions
Nebula Discovery - can be turned off
If you manually added a device to Nebula or scanned a code from the device, you might not be aware that Nebula Discovery is disabled in the local web interface. As a result, the device may never come online. To resolve this, access the device’s web interface and enable Nebula Discovery.
Incorrect or Incompatible APN Settings
Description: Nebula requires a stable IPv4 connection. Some providers (e.g., Telekom DE) may set the APN with an IPv6 priority, which could interfere with Nebula’s Cloud Monitoring services.
Solution:
- Access the device's local web interface:
http://192.168.1.1Or check on the device - Go to Network Settings → Broadband → Cellular APN.
- Enable APN Manual Mode and manually enter:
For Telekom Germany:
- APN:
internet.telekom- IP Type:
IPv4or IPv4/IPv6
- Apply the settings and reboot the device.
Auto APN Setting Not Suitable
Description: The Auto APN feature might not select the correct APN for the provider or cloud services, preventing the device from properly connecting to Nebula.
Solution:
- Disable Auto APN and configure the correct APN manually, even if the device is getting an IP address.
Blocked Ports by the Provider
Description: Some mobile providers block ports or use NAT configurations that are incompatible with Nebula Cloud Monitoring.
Solution:
Ensure that the following ports are not blocked:
| Purpose | Protocol | Port |
|---|---|---|
| Nebula Cloud Management | TCP | 443 |
| Nebula Device Registration | UDP | 123 (NTP), 53 (DNS) |
| Time Synchronization Services | UDP | 123 |
| Nebula Services (reverse connection) | TCP | 6667, 4335, 5190 |
Additionally:
- Ensure the device has a public IP and is not behind a CGNAT.
- If the provider uses strict NAT, this may prevent Nebula from connecting back to the device.
Device Not Fully Registered
Description: The device may be added to Nebula but not fully registered, or it may fail to connect due to a lack of internet access during the registration process.
Solution:
- Verify that the device is visible on your local network.
- Check for access to
nebula.zyxel.comusing ping/traceroute. - Remove and re-add the device to Nebula using its MAC address and serial number.
Firmware Version Outdated
Description: Older firmware versions may have compatibility issues or bugs that affect Nebula monitoring features. Updating to the latest firmware will ensure full compatibility and resolve potential issues
Solution:
- Log in to the device’s web interface.
- Go to Maintenance → Firmware Upgrade.
- Check for updates and perform the firmware upgrade.
For FWA series devices, it is not necessary to update the radio module separately, as is required for NR series devices. This is because FWA devices include radio module updates within the main firmware.
Additional Tips
- If the problem persists, contact Zyxel support via the Zyxel Support Portal.
Conclusion
If your Zyxel FWA device (such as the FWA505) is showing as offline in Nebula despite having a working internet connection, the cause may be related to incorrect APN settings, blocked ports, or issues with device registration. Adjusting the APN settings, verifying network ports, and ensuring the firmware is up to date should resolve the issue.

Comments
0 commentsPlease sign in to leave a comment.