I'm very sorry. However, there is a problem of not being able to obtain DNS, and it is impossible to check what the problem is by simply generating a debug log through the WEB UI. Some kind of interactive remote means is necessary.
I am having the same issues as all of the above.
I have attempted using the app on both Windows and MacOS with the same binding failure.
I have tried all of the terminal commands with no resolution to the DNS issues.
I have also update the Comet to v1.3.0 release 1 with no change.
Any help would be appreciated, would prefer not to return the device to amazon but may be forced to,
FYI: Never got a GLI solution for what would seem to be a simple DNS resolution issue. Cannot enter/save a STATIC DNS entry on the Comet units. I have 80+ hardware devices from over a dozen manufacturers all of which have no problem with DNS resolution on Comcast provided router, Linksys Brand Router, Synology Router. Comet(s) did not obtain a valid DNS entry, ever. Went back and forth for WEEKS with GLI. Finally just returned all three units. I purchased (3) COMET UNITS on 05-12-2025. 4 Weeks of GLI emails, then RMA'd all (3) units on 06-15-2025. GLI received the (3) returned comet units on 06-20-2025. Today is 06-30-2025 - still waiting on a refund 10 days after GLI receipt. Update with a solution if you get one please. Good Luck.
Will do.
No issues when just using a GL.iNet router (Slate AX), my main network is also Synology based with a custom DNS and DHCP setup.
I could manually assign a static IP address via the DHCP resolution table, but no luck in getting DNS working on the Synology router.
All my other devices have no issues with DNS as you have found.
UPDATE: Refund processed. Note: I have Synology Routers at two (2) locations and the COMETS would not BIND/DNS resolution on either one. Then I took Synology out of the loop and tried a home Comcast router. as well as a LINKSYS (old) router to no avail. (Reset each unit for each router environment, etc.)
We found that on some users, the problem was caused by the abnormal termination of the connmand process. If you encounter the same problem as in the previous comments where debug log cannot be generate, please try running the command
/etc/init.d/S45connman restart
if it still happened, please try below command to setup dns server manuanlly
echo "nameserver 8.8.8.8" | tee /etc/resolv.conf
/etc/init.d/S49ntp restart
U can use command date and nslookup www.google.com to see if it work normally