New MyCloud Sign On

[MugsUpMan]

I guess I'm a little confused about setting up a MyCloud Account.

So if I have a Nas which I set up and call if "FredNas" locally (not the real name...)

When Setting up the MyCloud Account I was unsure if I had to use the same name "FredNas" for my MyCloud nas name or if I could invent a new NAS name?

I created a new NAS Name of "MyFredNas" (which is different the name of the NAS I sign-on locally)
If I go to MyFredNas.myqnapcloud.com, I get a "Hmmmmm.... Can't reach this page error"

If I ping MyFredNas.myqnapcloud.com I get the following...

Ping statistics for 64.126.92.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

Seems to suggest that the site was found

The names "MyFredNas" is not the "real" value in this example as I'm not looking to publish the real name of "My Nas"

What am I doing wrong and what do I need to do to correct?

Thanks in advance for your assistance!!!!

[dolbyman]

what is the plan here?

trying to expose your nas for everyone to enjoy (mainly hackers and criminals)?

Do NOT expose your nas directly to WAN !

[MugsUpMan]

I believe the text of my question explains that the names I provided were NOT REAL NAMES and were changed to ensure that my NAS was not exposed.

Given that, can I possible get an answer?

[OneCD]

I believe the text of my question explains that the names I provided were NOT REAL NAMES and were changed to ensure that my NAS was not exposed.

The point is: your NAS is exposed to the Internet.

[MugsUpMan]

Anyone who uses MyQnapCloud is technically exposed to the Internet, Right?
So are you saying that the MyQnapCloud should not be used? What is the alternative?

[OneCD]

Anyone who uses MyQnapCloud is technically exposed to the Internet, Right?

Right.

And to see why that's a bad idea, search the forum for NAS that have been hacked because they were exposed to the Internet. Don't fall for the marketing BS. QNAPs are not hardened enough for Internet exposure.

So are you saying that the MyQnapCloud should not be used? What is the alternative?

Err, not using myQNAPcloud?

Use a paid online file hosting service instead. Much safer.

[OneCD]

Oh, I forgot about the new myQNAPcloud Link service. https://www.qnap.com/solution/myqnapcloud-link/en-us/

It looks much safer than the original. Might be worth testing?

[MugsUpMan]

Well, I bought the QNAP for sharing files within the family. So you are saying myQNAPCloud is ** and should not be used and I should host all of my family member files (people spread across the USA) multimedia files on a paid service like dropbox. Is that what you are saying?

[jaysona]

Oh, I forgot about the new myQNAPcloud Link service. https://www.qnap.com/solution/myqnapcloud-link/en-us/

It looks much safer than the original. Might be worth testing?

Both require port forwarding and are equally insecure means of accessing the various QTS web pages and apps.

The URL use to port to the nas is different, but it’s still pointing to QTS and all it’s inherent security vulnerabilities.

[OneCD]

Both require port forwarding and are equally insecure means of accessing the various QTS web pages and apps.

The URL use to port to the nas is different, but it’s still pointing to QTS and all it’s inherent security vulnerabilities.

The myQNAPcloud Link service does not require port-forwarding.

[jaysona]

Well, I bought the QNAP for sharing files within the family. So you are saying myQNAPCloud is ** and should not be used and I should host all of my family member files (people spread across the USA) multimedia files on a paid service like dropbox. Is that what you are saying?

You can host the files on your NAS, but remote access should be performed via VPN connection to your network.

QTS and its associated apps are insecure. There are vulnerabilities that do not require authentication (no admin login) to exploit which yields full remote access to the NAS.

There are regular posts here with increasing frequency from people that have had their NAS compromised and data either delete or encrypted by ransomware.

There are other options for sharing stuff on a QNAP NAS such as using Nextcloud, ownCloud, etc. I personally use Nextcloud, however to get it working properly and securely on a QNAP, while not overly complicated, is not an endeavour I would recommend for a non-technically proficienct user to embark on.

[jaysona]

Both require port forwarding and are equally insecure means of accessing the various QTS web pages and apps.

The URL use to port to the nas is different, but it’s still pointing to QTS and all it’s inherent security vulnerabilities.

The myQNAPcloud Link service does not require port-forwarding.

That must have changed from it’s initial roll-out when I looked at it, I’ll have to look into it again to see how it works under the hood. Thanks for the info.

[spile]

The misunderstanding that MyQnapCloud Link (note the Link bit at the end) requires port forwarding keeps coming up...
MyQnapCloud = port forwarding required. NAS exposed to internet
MyQnapCloud Link = port forwarding not required. NAS not exposed to internet therefore.