Just update my GL-RM1PE to the latest firmware WITHOUT keeping the settings. My device ended up showing as OFFLINE on cloud service and trying to bind with code gives me the above error! Choosing the option to bond to KVMCloud also produces another error with “Access KVMCloud failed”. Resetting device to factory default and reinstalling the firmware manually and I am still unable to connect to the cloud service. Never had this issue with previous updates or with my previous KVM model (GL-RM1). Any help or pointers here would be appreciated.
Downgraded down to 1.5.1 release 2 and the KVM connected automatically back to the cloud and showing up as online. Not clear as to what is going on with the new firmware release and whether anyone else has noticed the same issuse.
Hi,
Could you please provide us with your device's MAC address.
Updated: If convenient, please upgrade again to the 1.7 version to reproduce the problem and export the device log to us for analysis.
Sincerely appreciate your cooperation and patience.
My test results are normal. Could you provide a 1.7.0 log file for us to troubleshoot?
Thanks to @Kyrie and @_zhang .
Tried a fresh upgrade again without keeping setting to no avail unfortunately. On old firmware cloud service appears to be working perfectly:
And IMMEDIATELY after upgrade, no connection at all with errors as shown:
I think that I might have managed to locate the bug. With the new firmware installed, as soon as I turn my VPN client OFF on my router - Flint 2 - (I am using VPN Client - Windscribe) the KVM cloud service immediately connects. As soon as I VPN client is back ON, the cloud connection is lost. This problem has not been an issue with the prevous firmware and is reproducible all the time despite this:
Any fix would be appreciated as I keep my VPN client on all the time.
Based on your log post, I replied to you via private message. Please check it. I'm also using this VPN to conduct some tests.
1 Like
hi im having the exact same issue i was on 1.7 and now have upgraded to 1.7.1 but still cannot bind through the client app or on the cloud site.
In the client app the device shows up sometimes when trying to add and when i click bind it fails
Hi, could you please locally access to the RM1PE and export the log to us for analysis.
Also, please check if the device's DNS service is normal by ping google.com in Terminal and the time zone is correctly set.
You can send it to haoyu.zheng@gl-inet.com.
Sorry for the inconvenience caused.
How is the LED status, is it solid white which means a stable Internet access.
Hi Kyrie
I just install a GL-iNET RM1. I updated it to the last firmware 1.7.2
I can access it and my server without problem. But if I try to register it to the cloud, I get the same error `Access to KVMCloud fail’ and ‘ ‘Generate dinamic code failed, please try again later’
Ping to google through the terminal work without problem.
.----------------. .----------------. .----------------. .----------------. .----------------.
| .--------------. || .--------------. || .--------------. || .--------------. || .--------------. |
| | __ | || | __ | || | __ __ | || | __ __ | || | __ __ | |
| | .' ___ | | || | |_ | | || | | ||_ | | || || | | | | || || \ / || |
| | / .' _| | || | | | | || | | |/ / | || | \ \ / / | || | | / | | |
| | | | __ | || | | | _ | || | | **'. | || | \ \ / / | || | | |\ /| | | |
| | \ .___] _| | || | _| |__/ | | || | _| | \ \_ | || | \ ' / | || | _| |_\/_| |_ | | | | ..' | || | || | || | |||**| | || | _/ | || ||||_____|| |
| | | || | | || | | || | | || | | |
| '--------------' || '--------------' || '--------------' || '--------------' || '--------------' |
'----------------' '----------------' '----------------' '----------------' '----------------'
bash-4.4# ping google_com
PING google_com(2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b)) 56 data bytes
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=1 ttl=108 time=21.1 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=2 ttl=108 time=28.2 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=3 ttl=108 time=45.4 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=4 ttl=108 time=30.5 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=5 ttl=108 time=48.1 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=6 ttl=108 time=27.3 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=7 ttl=108 time=46.2 ms
64 bytes from 2800:3f0:4003:c08::8b (2800:3f0:4003:c08::8b): icmp_seq=8 ttl=108 time=36.0 ms
^C
--- google_com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 11010ms
rtt min/avg/max/mdev = 21.191/35.400/48.195/9.517 ms
bash-4.4#
I replace the . in google_com because of restriction for new users
It seems there are some compatibility issues in the IPv6 environment. Is it possible to configure Comet to work in the IPv4 environment?
glkvm cloud cannot work in a pure IPv6 environment.
Hi Minmie,
Pinging using option ipv4
bash-4.4# ping -4 google_com
PING google_com (172.217.192.101) 56(84) bytes of data.
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=1 ttl=107 time=21.5 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=2 ttl=107 time=29.1 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=3 ttl=107 time=25.4 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=4 ttl=107 time=26.3 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=5 ttl=107 time=22.2 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=6 ttl=107 time=24.1 ms
64 bytes from cf-in-f101_1e100.net (172.217.192.101): icmp_seq=7 ttl=107 time=25.2 ms
^C
--- google_com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6008ms
rtt min/avg/max/mdev = 21.537/24.867/29.102/2.380 ms
bash-4.4#
Hi Minmie
Is posible to force the dhcp client to use ip4 addresses only. My environment has both IP protocols.
I check the ip configuration of the GL-iNET RM1 and it has a valid ipv4 configuration.
bash-4.4# ifconfig
eth0 Link encap:Ethernet HWaddr 94:83:C4:BB:2D:F3
inet addr:192.168.68.53 Bcast:192.168.71.255 Mask:255.255.252.0
inet6 addr: fe80::9683:c4ff:febb:2df3/64 Scope:Link
inet6 addr: 2803:9810:322f:8400::1003/128 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:170475 errors:0 dropped:33993 overruns:0 frame:0
TX packets:174573 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20305821 (19.3 MiB) TX bytes:32137834 (30.6 MiB)
Interrupt:54
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2851 errors:0 dropped:0 overruns:0 frame:0
TX packets:2851 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:540671 (527.9 KiB) TX bytes:540671 (527.9 KiB)
bash-4.4#
That's not the issue then. I suggest you send us a debug log for analysis.
Hi Minmie
I am sending log export to email account haoyu.zheng@gl-inet.com
We have processed this document for you. Please check if it is working properly now.
This is a bug from an older version upgrade. If you didn't save your configuration, it might cause the authentication information for your device's connection to the cloud platform to be lost. We have resent the authentication information to you.
Hi _zhang
Thanks it work without problem.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.