GL.iNet routers are trusted worldwide for secure, customizable networking—especially among digital nomads, privacy-conscious users, and remote workers. Many users, however, find themselves stuck when trying to enable tracking features, whether for device monitoring, parental control, GPS integration, or network analytics.
If you’re wondering how to allow tracking on your GL.iNet router and running into errors or confusing menus, you’re not alone. This guide outlines the 10 most common issues and how to fix them quickly and safely, ensuring your tracking features are working as intended.
1. Tracking Not Enabled by Default
The Problem:
Many users assume tracking is active as soon as the device is powered on. However, GL.iNet routers do not allow tracking or remote monitoring features by default—this is part of their privacy-first design.
How to Fix It:
To manually enable tracking:
Log in to the GL.iNet admin panel (usually 192.168.8.1)
Go to Applications > GoodCloud (or Cloud → Remote Access)
Enable GoodCloud or other remote/cloud services for monitoring
Toggle the required tracking option, such as device list logging, data usage monitoring, or location history
Don’t forget to save changes and restart your router if needed.
2. Outdated Firmware Preventing Tracking Functions
The Problem:
Old firmware may lack necessary features or have bugs affecting tracking modules.
How to Fix It:
Log in to your router dashboard
Navigate to System > Upgrade
Click “Check for updates”
If a new version is available, update the firmware
After updating, recheck your tracking settings to see if the issue is resolved.
Caution: Always back up your settings before updating firmware.
3. Disabled GoodCloud Account Integration
The Problem:
GL.iNet’s GoodCloud platform allows remote device tracking, logging, and control—but it only works if the router is properly linked to your cloud account.
How to Fix It:
Register or log in to [https://www.goodcloud.xyz](https://www.goodcloud.xyz)
On your router’s admin panel, go to Cloud > Remote Access
Enable Cloud Management, then bind your router to your GoodCloud account
Once linked, you can manage tracking, logs, and alerts remotely
Tip: Check if the router shows “Online” in GoodCloud. If not, there may be a connection error or firewall blocking access.
4. Location Tracking Not Working on LTE Routers
The Problem:
If you’re using a GL.iNet LTE-enabled router (like the MV1000, Spitz, or Puli), the GPS tracking features may not function due to disabled modules or blocked SIM data.
How to Fix It:
Make sure your SIM card supports data and location sharing
Enable GPS under the Modem Settings tab
Ensure the required GPS modules and drivers are installed (check via Advanced Settings > LUCI Interface)
You may also need to:
Activate APN manually
Enable serial port communication for GPS
Some models require firmware patches to access GPS—check GL.iNet’s support forums for model-specific guidance.
5. Third-Party VPN Blocking Tracking Logs
The Problem:
If you’re using a VPN service (like WireGuard, OpenVPN, or NordVPN), you might unknowingly block the router from sending tracking data to GoodCloud or logging connected device activity.
How to Fix It:
Go to VPN Settings > VPN Policies
Add GoodCloud, tracking scripts, or local subnet addresses to the “Do Not Use VPN” list
Restart router and re-sync tracking dashboard
This allows internal logging and device discovery while still protecting external traffic.
6. Parental Control Logs Not Saving
The Problem:
Some users enable Parental Control to track and restrict device usage, but later find that logs aren’t saving or accessible.
How to Fix It:
Check if Parental Control is fully enabled: Go to Applications > Parental Control
Set up time schedules and devices
Enable Logging Mode
Make sure your router has sufficient storage (some features require microSD or USB expansion)
Bonus Fix: Use OpenWRT’s LUCI interface to monitor deeper logs if you’re an advanced user.
7. Inaccurate Device Tracking or IP Leaks
The Problem:
Tracking might show incorrect device names, IPs, or unknown connections—often due to IP conflicts, MAC address randomization, or static IP setups.
How to Fix It:
Assign static IPs or device names under Clients > Manage Devices
Use MAC binding to track each device reliably
Restart all connected devices to clear cache
Check for duplicate device entries and remove them
Also disable “Private Wi-Fi Address” on iOS/Android if accurate tracking is needed.
8. GL.iNet App Not Syncing with Router
The Problem:
The GL.iNet mobile app helps manage your router remotely, but tracking features may not sync due to login mismatches or network restrictions.
How to Fix It:
Ensure your mobile app uses the same GoodCloud account linked to your router
Update the app from the App Store or Google Play
Restart the app and router
Allow app permissions for location and notifications
You may also need to open ports or allow UPnP if you’re on a restricted mobile network.
9. No Tracking After Reset or Factory Restore
The Problem:
Resetting your router wipes tracking preferences, GoodCloud bindings, and custom configurations.
How to Fix It:
Reconnect to the GL.iNet admin panel
Restore from your backup configuration (if you saved one)
Re-link your GoodCloud account
Re-enable tracking, logging, and parental controls manually
Make it a habit to export configurations after making significant changes to avoid repeat setups.
10. Firewall Blocking Data Logging
The Problem:
Custom firewall settings, especially if imported from another OpenWRT device, might block tracking logs or cloud services.
How to Fix It:
Go to Advanced Settings > Firewall
Check that GoodCloud and remote logging ports (usually 443, 8883) are open
Temporarily disable strict firewall rules to test functionality
Reboot and monitor logs under System Log > Kernel Log
If using AdGuard Home or custom DNS, allowlist GL.iNet’s remote services.
Conclusion: Tracking with GL.iNet Doesn’t Have to Be Hard
Allowing tracking on your GL.iNet router opens up a powerful suite of tools: from monitoring connected devices to controlling usage and accessing remote diagnostics. But due to the router’s strong focus on privacy and security, many tracking features are disabled by default or hidden behind advanced settings.
By following the 10 fixes above, you can troubleshoot common problems with tracking and get your setup working smoothly. Whether you’re a parent, remote worker, or tech enthusiast, GL.iNet gives you granular control over your network—as long as you know where to look.
FAQs
1. Is tracking enabled automatically on a new GL.iNet router?
No. Most tracking features like GoodCloud, Parental Control, and device logging must be manually enabled via the admin panel.
2. Is GL.iNet tracking safe and private?
Yes. GL.iNet prioritizes user privacy, and any tracking you enable stays within your local network or encrypted cloud (if you opt into GoodCloud).
3. Can I track device activity without using GoodCloud?
Yes. You can view connected devices, usage history, and logs locally via the admin panel. GoodCloud adds remote access and mobile app control.
4. Why is my tracking data missing after a power outage?
Tracking data may be lost if stored in temporary memory (RAM). For persistent logging, use external storage (USB or SD card) or enable GoodCloud sync.
5. Which GL.iNet routers support tracking and GPS features?
All models support basic tracking. GPS-enabled models include Spitz (GL-X750), Puli (GL-XE300), and Brume 2 (GL-MT2500) with external modules.
