Why do I need to intermittently reconnect CloudLink?

[hudra]

Downgrade helped me to fix the problem

[zopanda.pake]

The downgrade has NOT worked for me, unfortunately. I still have the exact same problem. Now with nagging messages to upgrade my apps...

Has anyone got the downgrade to work on a QNAP TS-451+ NAS?

[ts251plus]

I have the same problem. It just don't work anymore even I rebooted the NAS
Here is my log file

Code: Select all

[1;32m06/16/17 19:23:03: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:24:03: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:24:03: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:24:03: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:24:03: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:24:20: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:24:32: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:24:32: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:25:32: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:25:32: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:25:32: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:25:32: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:25:49: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:26:01: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:26:01: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:27:01: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:27:01: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:27:01: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:27:01: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:27:18: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:27:30: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:27:30: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:28:30: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:28:30: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:28:30: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:28:30: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:28:56: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:29:09: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:29:09: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:30:09: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:30:09: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:30:09: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:30:09: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:30:26: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:30:38: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:30:38: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:31:38: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:31:38: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:31:38: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:31:38: eagent.c: 397: start_p2p_agent():P2P tunnel server start with 4W17CBSUJAUV3SLC111A[0m
[1;32m06/16/17 19:31:55: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: 4W17CBSUJAUV3SLC111A, rc :-1[0m
[1;30m06/16/17 19:32:05: eagent.c: 463: run_eagent():start_p2p_agent start, vlinkid:SPHSXRRNCNLEYL9C111A[0m
[1;32m06/16/17 19:32:05: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:32:05: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:32:05: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:32:05: eagent.c: 397: start_p2p_agent():P2P tunnel server start with SPHSXRRNCNLEYL9C111A[0m
[1;32m06/16/17 19:32:23: eagent.c: 423: start_p2p_agent():Tunnel start failed, id: SPHSXRRNCNLEYL9C111A, rc :-1[0m
[1;32m06/16/17 19:32:23: eagent.c: 138: write_event_log():LD_LIBRARY_PATH=/usr:/usr/lib; /sbin/log_tool -t 0 -a "[myQNAPcloud] CloudLink service for mobile and PC applications is not available. You may not be able to access your QNAP device via QNAP mobile apps or PC utilities via CloudLink. Please make sure your device is connected to the Internet and the UDP traffic is not blocked. error code: [-1]"[0m
[1;30m06/16/17 19:32:35: eagent.c: 435: stop_p2p_agent():P2PTunnelServer_Stop & P2PTunnelServerDeInitialize[0m
[1;32m06/16/17 19:32:35: eagent.c: 496: run_eagent():Restart p2p after: 60[0m
[1;32m06/16/17 19:33:35: eagent.c: 382: start_p2p_agent():p2p_io version: 10e1200[0m
[1;32m06/16/17 19:33:35: eagent.c: 383: start_p2p_agent():p2p_agent version: 1040a00[0m
[1;32m06/16/17 19:33:35: eagent.c: 392: start_p2p_agent():P2P tunnel server init okay!![0m
[1;32m06/16/17 19:33:35: eagent.c: 397: start_p2p_agent():P2P tunnel server start with SPHSXRRNCNLEYL9C111A[0m

[sallysensation]

This happens because Qnap is a buggy piece of garbage and we should have bought a Synology instead. I give up with this thing.

[napper1237]

Hi

I've started getting this only recently. It's a pain in the proverbials.

Has there been any progress on it of late?

[dolbyman]

report it to qnap...make them aware

[zopanda.pake]

Has anyone solved this problem? I've waited for a few firmware upgrades and software updates... still no luck to what would seem to be an easy code fix. Cloudlink just needs to automatically try to "Normal"-ize itself if it finds itself needing to reconnect, as opposed to an Admin manually logging into the system and clicking "Reconnect", which by and large is all it takes for me to fix this annoyance. I'm presently off-site, CloudLink is down, and I won't be next to the device to hardwire direct to it, so I basically have a lump of coal for a week unable to access any of my data via VPN nor Cloudlink... QNAP...!

[osbrook]

Has anyone solved this problem? I've waited for a few firmware upgrades and software updates... still no luck to what would seem to be an easy code fix. Cloudlink just needs to automatically try to "Normal"-ize itself if it finds itself needing to reconnect, as opposed to an Admin manually logging into the system and clicking "Reconnect", which by and large is all it takes for me to fix this annoyance. I'm presently off-site, CloudLink is down, and I won't be next to the device to hardwire direct to it, so I basically have a lump of coal for a week unable to access any of my data via VPN nor Cloudlink... QNAP...!

I have the same issue. Each night it disconnects but does not reconnect unless I logon locally and press reconnect.

It should try to do this automatically. So that it maintains the link.

[osbrook]

Is there a command line I can run from Crontab to get it to reconnect so I don't have to log on locally?

Mine disconnects at the same time each day (03:05) but fails to reconnect when it retries a few minutes latter. However when I do it manually latter in the day (08:00) it works. So thought I could force a reconnect sometime early morning (pre 08:00) when remote access is not required.

Over simplistic but it should just reconnect, in fact it shouldn't disconnect unless there is an external IP address change.

[AJumpp]

Same here...It has been acting up intermittently for months...But today is the worst. I received a text from an engineer who needed to grab work from the NAS. Now I can't remotely connect, but it says things are fine. Then when I check locally it shows errors on the UPNP settings. Even manually setting those in the router doesn't work.

[btekcan]

I have also same problem on my TS-453A

[schumaku]

Use the Helpdesk App on your NAS or alternately https://helpdesk.qnap.com/ to report.

[oyvindo]

Use the Helpdesk App on your NAS or alternately https://helpdesk.qnap.com/ to report.

I think Kurt is right. We should all report this to QNAP. That's the only way to get some attention.
I too had this issue after the most recent upgrade. It happens sometimes 2-3 times per day, other times it can go for several days without any issue.
I often use myqnapcloud to connect remotely to my servers, and have no issues with it - but of course, chance had it this error never occured while I was remotely connected, so I don't know what would happen if it did.

[oyvindo]

Qnap NAS UPnP is very buggy & unreliable as far as opening ports (some ports you really have to manually port forward on router). If it sees something in conflict it will switch external ports. So sometimes you'll notice that the NAS port is different than the External port. You can uncheck those ports & do what I've mentioned above.

There is no reason at all to ever use uPnP on your router. In fact - from a security perspective - you should never allow it!
It is not needed in order to use myQNAPcloud, and the problem referred to in this thread has nothing to do with uPnP.

[osbrook]

Qnap NAS UPnP is very buggy & unreliable as far as opening ports (some ports you really have to manually port forward on router). If it sees something in conflict it will switch external ports. So sometimes you'll notice that the NAS port is different than the External port. You can uncheck those ports & do what I've mentioned above.

There is no reason at all to ever use uPnP on your router. In fact - from a security perspective - you should never allow it!
It is not needed in order to use myQNAPcloud, and the problem referred to in this thread has nothing to do with uPnP.

Agreed. I found a way round by NOT using Cloud link. Simply set the ports on the router. Provided DDNS has been configure and you append the port number to the URL you will be fine. Obviously you can use the Cloudlink (Mycloud) URL that is set with DDNS.