Can't bind controller to cloud

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Can't bind controller to cloud

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can't bind controller to cloud
Can't bind controller to cloud
2023-03-21 20:57:57 - last edited 2023-03-21 21:38:05

Hello,

I have a problem to bind my controller (docker on Synology NAS, version 5.9.9) to cloud. SMTP server is configured correctly - I can send test mail. Mail alerts also is enabled. My error is: 'General error'.

  0      
  0      
#1
Options
11 Reply
Re:Can't bind controller to cloud
2023-03-22 00:43:26

  @solidf 

 

I am running exactly the same setup...5.9.9 in Docker on my 1522+.  Worked flawlessly.  I used host networking not bridged though.  If you bridged the container you should add a default LAN route for 172.17.0.0/16 or whatever the Docker private network is via your NAS's IP on your LAN subnet.

 

 

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options
Re:Can't bind controller to cloud
2023-03-22 08:06:05

  @d0ugmac1 I also use host network:

 

  0  
  0  
#3
Options
Re:Can't bind controller to cloud
2023-03-22 13:26:26

  @solidf 

 

You have previously 'registered' the desired gmail address with the TPlink cloud service?  You have verified you can login into the cloud service via the web?

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#4
Options
Re:Can't bind controller to cloud
2023-03-22 13:36:51

  @d0ugmac1 Yes. I have correctly bind to cloud services another Omada Controller OC200 5.7.6. The problem is only in the docker instance. Should I firstly unbind my OC200?

  0  
  0  
#5
Options
Re:Can't bind controller to cloud
2023-03-22 15:24:10

  @solidf 

 

No, don't detach your OC200.

 

I actually have several docker controllers on the same NAS that are cloud connected.  The active one is 'host' networked, and the test versions are 'bridged' to avoidi port conflicts.  All were registered with the same gmail and password.

 

 

The only port forward I have is to forward my WAN port 8043 to the NAS port 8043, but this shouldn't be necessary as the my OC200 has no such route, it only has the discovery ports (29810-29814) forwarded, but not the 8043.

 

 

 

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#6
Options
Re:Can't bind controller to cloud
2023-03-22 19:17:58

  @d0ugmac1 and this is the error from mobile app, very wierd:

 

  0  
  0  
#7
Options
Re:Can't bind controller to cloud
2023-03-22 20:22:14

  @solidf 

 

Have you tried using the mobile app via a cellular connection...ie with no wif enabled?  I'm wondering if there's something funky with your provider pipe?

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#8
Options
Re:Can't bind controller to cloud
2023-03-23 11:14:56

  @d0ugmac1 

Unfortunately, using the mobile Internet, I will not have access to devices in the local network.

  0  
  0  
#9
Options
Re:Can't bind controller to cloud
2023-03-23 14:24:38

  @solidf 

 

Step 1: gain access to cloud service independently

 

This proves that the gmail account you are using is registered, valid and working as your cloud account

 

Step 2: figure out why the above gmail account is failing to connect from your local controller when you try to bind it to the cloud.

 

So my ask earlier was if you can log into the TPlink website by browser or the mobile app.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#10
Options
Re:Can't bind controller to cloud
2023-03-24 07:08:01 - last edited 2023-03-24 07:08:38

  @d0ugmac1 

 

Yes - I can log in to Omada Cloud with this e-mail via website, where I can see my OC200 correctly bind to cloud:

 

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 1084

Replies: 11

Related Articles