So i share a sub directory, but when i tried using myqnapcloud, it didn't work.
but when using the smartlink method it works, why is that? Any ideas why the myqnapcloud method using dyndns does not work? yes i already port forwarded 443 to the correct NAS lan ip on router.
does anyone have a guide for this? i tried the video guides but they don't troubleshoot these types of issues i'm having
Yes i did get sharing to work via smartlink method, but i want to try getting the myqnapcloud dyndns method to work as well.
also what is the recommended setting to safely share? will people you share with be able to access the link, if it's set to private? i refrain from public, i don't want my page to be searchable
for the smartlink, that worked when i added friend to customized access control in cloudlink.
though earlier there was a status abnormal for cloudlink, had to reconnect cloudlink and update the dyndns to myqnapcloud, and that seemed to fix it.
Wheeljack77 wrote:That's probably because your VPN is likely using the same port 443 to transfer data as myqnapcloud. Not sure if it is possible, but one way you could get around the issue is to see if you have a port triggering setting on your router and set your router to access port 443 (just add it to the rules). Port triggering is better that port forwarding because it allows multiple devices or apps to use the setting while port forwarding only forwards one specific port to one specific device.
is this the reason?
i did test disabling qvpn, but it still didn't work. but then again i did not reboot the qnap or router after disabling qvpn if that was required.
Port Trigger allows you to temporarily open data ports when LAN devices require unrestricted access to the Internet. There are two methods for opening incoming data ports: port forwarding and port trigger. Port forwarding opens the specified data ports all the time and devices must use static IP addresses. Port trigger only opens the incoming port when a LAN device requests access to the trigger port. Unlike port forwarding, port trigger does not require static IP addresses for LAN devices. Port forwarding allows multiple devices to share a single open port and port trigger only allows one client at a time to access the open port.
found a guide here
by the way this guide here, does not mention anything about port forwarding... which ought to be crucial for use by the myqnapcloud dynsdns for your link to even work.
https://www.qnap.com/en/how-to/tutorial ... le-station