Home Network Community > All Threads > Can't connect to Reolink cameras remotely
< All Threads

Can't connect to Reolink cameras remotely

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

Can't connect to Reolink cameras remotely

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can't connect to Reolink cameras remotely
Can't connect to Reolink cameras remotely
2023-02-12 04:48:57
Tags: #Reolink
Model: Deco X68  
Hardware Version: V1
Firmware Version: 1.1.1 Build 20221115 Rel. 52180

Hello, I have been using the Deco X68 since October 2022 and I am amazed at its performance.

 

However, since a few days ago I realized that I can't access my reolink cameras remotely. I do not remember if this failure is from October, since we had not accessed the cameras until recently.

 

I have multiple smart devices and they all work fine.

 

I have tried another router and the remote connection works correctly.

 

I have tried resetting the cameras and it doesn't work.

 

When clicking on the remote connection in the reolink app, the Deco X68 generates the following log:

 

Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.84. start_ip: C0A80896, ind: 4294967230. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.23. start_ip: C0A80896, ind: 4294967169. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.20. start_ip: C0A80896, ind: 4294967166. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.7. start_ip: C0A80896, ind: 4294967153. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.50. start_ip: C0A80896, ind: 4294967196. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.85. start_ip: C0A80896, ind: 4294967231. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.44. start_ip: C0A80896, ind: 4294967190. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.42. start_ip: C0A80896, ind: 4294967188. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.88. start_ip: C0A80896, ind: 4294967234. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.30. start_ip: C0A80896, ind: 4294967176. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.34. start_ip: C0A80896, ind: 4294967180. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.46. start_ip: C0A80896, ind: 4294967192. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.36. start_ip: C0A80896, ind: 4294967182. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.32. start_ip: C0A80896, ind: 4294967178. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.47. start_ip: C0A80896, ind: 4294967193. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.81. start_ip: C0A80896, ind: 4294967227. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.5. start_ip: C0A80896, ind: 4294967151. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.24. start_ip: C0A80896, ind: 4294967170. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.87. start_ip: C0A80896, ind: 4294967233. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.82. start_ip: C0A80896, ind: 4294967228. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.1. start_ip: C0A80896, ind: 4294967147. Return NULL ping state.
Sun Feb 12 00:32:56 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:56 2023 user.err lua: Error: connect
Sun Feb 12 00:32:57 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:57 2023 user.err lua: Error: connect
Sun Feb 12 00:32:57 2023 daemon.notice nrd[13557]: ar_apinfo_collect[line 1043]: AP sync timer expires!
Sun Feb 12 00:32:58 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:58 2023 user.err lua: Error: connect
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbUpdateAssoc: Station 68:FF:7B:E8:6B:38 roams itself
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbEntry_updateARBtmThreshold: update threshold of client 68:FF:7B:E8:6B:38 for reason 2
Sun Feb 12 00:33:07 2023 daemon.err nrd[13557]: ar_config_set_thres[line 28]: Null thres!
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbUpdateAssoc: Station 68:FF:7B:E8:6B:38 roams itself
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbEntry_updateARBtmThreshold: update threshold of client 68:FF:7B:E8:6B:38 for reason 2
Sun Feb 12 00:33:07 2023 daemon.err nrd[13557]: ar_config_set_thres[line 28]: Null thres!
Sun Feb 12 00:33:08 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:09 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:09 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:10 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:11 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:11 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:12 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:13 2023 daemon.err client_mgmt: Lua: call failed. 2
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.84. start_ip: C0A80896, ind: 4294967230. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.23. start_ip: C0A80896, ind: 4294967169. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.20. start_ip: C0A80896, ind: 4294967166. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.7. start_ip: C0A80896, ind: 4294967153. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.50. start_ip: C0A80896, ind: 4294967196. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.85. start_ip: C0A80896, ind: 4294967231. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.44. start_ip: C0A80896, ind: 4294967190. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.42. start_ip: C0A80896, ind: 4294967188. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.88. start_ip: C0A80896, ind: 4294967234. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.30. start_ip: C0A80896, ind: 4294967176. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.34. start_ip: C0A80896, ind: 4294967180. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.46. start_ip: C0A80896, ind: 4294967192. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.36. start_ip: C0A80896, ind: 4294967182. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.32. start_ip: C0A80896, ind: 4294967178. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.47. start_ip: C0A80896, ind: 4294967193. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.81. start_ip: C0A80896, ind: 4294967227. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.5. start_ip: C0A80896, ind: 4294967151. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.24. start_ip: C0A80896, ind: 4294967170. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.87. start_ip: C0A80896, ind: 4294967233. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.82. start_ip: C0A80896, ind: 4294967228. Return NULL ping state.
Sun Feb 12 00:32:47 2023 daemon.err client_mgmt_arp: Invalid ip addr 192.168.8.1. start_ip: C0A80896, ind: 4294967147. Return NULL ping state.
Sun Feb 12 00:32:56 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:56 2023 user.err lua: Error: connect
Sun Feb 12 00:32:57 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:57 2023 user.err lua: Error: connect
Sun Feb 12 00:32:57 2023 daemon.notice nrd[13557]: ar_apinfo_collect[line 1043]: AP sync timer expires!
Sun Feb 12 00:32:58 2023 user.err lua: Error: ssh_connect: Timeout connecting to 192.168.11.252
Sun Feb 12 00:32:58 2023 user.err lua: Error: connect
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbUpdateAssoc: Station 68:FF:7B:E8:6B:38 roams itself
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbEntry_updateARBtmThreshold: update threshold of client 68:FF:7B:E8:6B:38 for reason 2
Sun Feb 12 00:33:07 2023 daemon.err nrd[13557]: ar_config_set_thres[line 28]: Null thres!
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbUpdateAssoc: Station 68:FF:7B:E8:6B:38 roams itself
Sun Feb 12 00:33:07 2023 daemon.notice nrd[13557]: stadbEntry_updateARBtmThreshold: update threshold of client 68:FF:7B:E8:6B:38 for reason 2
Sun Feb 12 00:33:07 2023 daemon.err nrd[13557]: ar_config_set_thres[line 28]: Null thres!
Sun Feb 12 00:33:08 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:09 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:09 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:10 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:11 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:11 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Sun Feb 12 00:33:12 2023 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sun Feb 12 00:33:13 2023 daemon.err client_mgmt: Lua: call failed. 2

 

FYI:

 

  1. 192.168.11.252 is a deco m3w satellite.
  2. 192.168.11.253 is a deco x68 satellite.
  3. 192.168.8.1 is my main pc.
  4. 192.168.8.80-89 all reolink cameras

 

Hoping you can help me,

 

Thank you.

 

 

  0      
 
  0      
 
#1
Options
4 Reply
Re:Can't connect to Reolink cameras remotely
2023-02-13 07:59:41

  @Conker 

Hi, Thank you very much for the feedback.

Here are several methods for the remote access to Reolink cameras and I wouder which one you tried before:

https://support.reolink.com/hc/en-us/articles/360003539394-How-to-Access-Reolink-Products-Remotely

 

Would there be any error message when the remote access failed?

And on Deco X68, Have you set up any parental control profiles for Reolink cameras?

Please also refer to the suggestions on this link:

https://support.reolink.com/hc/en-us/articles/360039401593-Fail-to-Connect-Reolink-IP-Cameas-When-Remotely-Accessing-them-

 

Best regards.

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! ▶Deco X50-5G-V1-1.2.0 Supports WireGuard VPN, Hybrid Mesh and More Try to leave a Message if urgent help is required.
  0  
  0  
#2
Options
Re:Can't connect to Reolink cameras remotely
2023-02-27 03:31:42

  @David-TP Hi, the cameras are already added and can be viewed locally. If I disconnect the deco and turn on my old router, remote access works without problems. The error is "connection failed".

  0  
  0  
#3
Options
Re:Can't connect to Reolink cameras remotely
2023-02-27 03:32:12

  @David-TP I set up a parental control profile and remote access still doesn't work.

  0  
  0  
#4
Options
Re:Can't connect to Reolink cameras remotely
2023-06-09 19:56:08

  @Conker - Did you every happen to get this resolved? I also have the X68 system with no issues. Trying to connect my new NVR via Lan is not working at all. Would love to hear if anything worked for you.

  1  
  1  
#5
Options

Information

Helpful: 0

Views: 1490

Replies: 4

Tags

Reolink
Related Articles
Reolink unable to connect to M9 plus router
2835 0
Reolink wifi camera fails to connect to deco m5 system
1650 0
Deco goes offline when reolink camera nvr system is connected
1618 0
Reolink wifi cams
482 0
Can't connect
622 0
M5 - Can't Connect to mail.google.com
819 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.