Comet POE won't bind — Token Invalid error, factory reset doesn't help

KVM
1

Hey all,

Having a frustrating time trying to bind a new Comet POE to my existing GL.iNet account. I already have two Comet Pros successfully bound, so I'm familiar with the process — this third device is just not cooperating.

Here's what's happening: the device reaches GL.iNet's servers fine (I can confirm network connectivity is not the issue), fetches the CA cert successfully, hits the auth endpoint at gslb-eu.goodcloud.xyz/v2/device/auth, but immediately gets back a -4.0 Token Invalid error. This repeats on every attempt with no variation.

What I've tried:

  • Verified DNS resolves correctly to GL.iNet's servers
  • Confirmed outbound HTTPS connectivity to goodcloud.xyz is open
  • Full factory reset — no change, Token Invalid persists immediately after reset
  • Waiting for NTP to sync before attempting to regenerate the binding code
  • The dynamic binding code UI shows "Binding Code expired. Please regenerate" but regenerating never produces a working code
2

Provide MAC address of your kvm to us

4

94:83:C4:BE:86:14

thank you

5

should be able to bind now, try it

6

Thank you. It worked!

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.