Issue with Comet GL-RM1 Tailscale binding

KVM
1

I just got a Comet GL-RM1, it works great for KVM, but I have a problem getting it registered to Tailscale.

Following the doc here: Remote access via Tailscale - GL.iNet KVM Docs
The “bind” link is not working correctly, when I click the link the progress animation is just spinning, but I am never redirected to the tailscale login page.

image
image671×416 45.3 KB

(This just keeps on spinning…)

I have tried 3 different browser, Firefox, Brave, Edge og different computers.

Firmware version is: v1.7.2 release1 (RM1)

Is there a known workaround for this issue? maybe some CLI commands I can run via SSH?

2

You should be able to use tailscale login via SSH.

3

Might want to check if the GL-RM1 has sync’ed time.

ssh root@{hostname} 

date

If it comes back at December 31, 1969 or January 1, 1970, then it has not sync’ed time.

4

Thanks for the suggestions, I was able to fix the issue by running “tailscale update” via the webterminal.
Now the Bind device link is working correctly and redirecting me to the tailscale login page.

1 Like
5

Ialso have problem with binding my comet to tailscale…
Trying to update tailscale in terminal but get a timeout.

I can ping 8.8.8.8
I can not ping google. com

Seems to be a DNS-problem
FW = V1.7.2 release1

[root@glkvm:~]# tailscale update
fetching latest tailscale version: Get "https://pkgs.tailscale.com/stable/?mode=json&os=linux": dial tcp: lookup pkgs.tailscale. com on 127.0.0.1:53: read udp 127.0.0.1:51080->127.0.0.1:53: i/o timeout
[root@glkvm:~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=2.55 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=2.36 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=117 time=2.30 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 2.303/2.407/2.553/0.120 ms
[root@glkvm:~]# ping www.google. com
ping: www.google. com: Temporary failure in name resolution
[root@glkvm:~]#

6 
#manual DNS
connmanctl config `connmanctl services |grep ethernet|awk -F' '  '{print $3}'|head -1` nameservers 192.168.113.244

setup dns by connmand , It seems your router might not be distributing DNS configurations automatically, so you may need to set it up manually.

7

It was a DNS-issue…
My Pi-hole was down :blush:
Now working perfect…