Recent network changes?

[#1]

I'm having issues with our NAS connecting to the outside world, it has worked previously and we've made no changes to the NAS nor the broadband setup. I've contacted the NAS supplier to try and chase the fault but they're pointing at our network setup (which we've not changed since the device was working) so I was wondering if there have been any changes made by Plusnet themselves? The specifics of the NAS vendor requirements are:

Also, I would request you to contact your Internet Service Provider (ISP) to verify whether your router’s security settings are blocking local queries or filtering incoming traffic. Specifically, ensure that ports 8443 and 443 are not being blocked, as these are essential for device communication.

Any info which points to a plusnet change (or lack of!) would be useful.

Thanks

Chris

[#2]

@cmg 

I do not know about this matter, but similar questions are raised here :

https://community.plus.net/t5/My-Router/hub2-firmware-inbound-80-443-problems/m-p/2056273

[#3]

Moderator's note:
Thread moved from Broadband to Everything Else 

[#4]

@cmg 

Have you tried testing whether ports 443 and 8443 are externally visible using a port scanner such as GRC ShieldsUP! ?

[#5]

Opening ports to a NAS puts you at risk of ransomware and attacks. 

[#6]

Thanks for the replies. I don't really understand how the external connections work on new devices like my Nas. I didn't need to open any ports to allow it to work for the first few years of ownership and I haven't changed my firewall settings. My gut feel is something has gone wrong with the nas software. I have other devices which can still be accessed so that makes me think more a nas issue.

[#7]

For the first few years did the NAS come with a subscription to an external service that has now expired ?

[#8]

Exposing a NAS by opening ports (port forwarding) is typically done to access your storage away from home or to share files. However, direct port forwarding exposes your NAS to automated internet scans and potential exploits, making it a major security risk.

A safer approach for personal access is using a self-hosted VPN like WireGuard or a mesh network like Tailscale (both free). These can run on a compatible router, a Raspberry Pi, or the NAS itself, creating a secure, encrypted tunnel to your home network without exposing open web interfaces to the public internet.

[#9]

I think the question from the NAS vendor was really, is the ISP blocking OUTBOUND connections to ports 8443 and 443.

Hopefully "Shields Up" and similar will show no response from any port for an incoming connection.

Generally the remote access to a NAS provided by the manufacturer has a mid-point at which you create an account.

The Synology version is QuickConnect

Synology NAS External Access Quick Start Guide - Synology Knowledge Center

Personally I would use a router that supports Wireguard and not use the NAS suppliers service. I really wouldn't forward ports on a router to a NAS.

That doesn't explain why yours has stopped working however!  

[#10]

I agree outbound blocking would make more sense, yes shields up shows no response. I'm using a WD mycloud, but as Mark says remote access is provided by WD with an account. I have similar with our CCTV and smart thermostat both from different manufacturer and both of which continue to work.

[#11]

I used to have a WD MyCloud.

It was the white one, 4TB.

It stopped being supported and it was painfully slow (even on the same LAN).

In the end I bought a Synology and used the drive in that. it was infinitely better than the MyCloud.

What you can't do is just move the drive. You have to transfer all the data.

If yours has stopped working, I might start with asking WD.

[#12]

Thanks I started with WD they're pointing at the ISP but I'm not convinced. We used the mycloud for a while no issues then the PSU failed and I had to convince WD to replace it, this is the replacement which worked for a few months and is now no longer connecting to the outside world, the discs are fine but I won't be buying WD systems again.

[#13]

If you have a friend or relative where you could try the device on their connection it's probably worth a go.

I don't think it will help but it will provide some evidence to tell WD.

I also assume it's fine on your home network.

[#14 · Accepted solution]

Thanks for the suggestion, I've now tried on another network and have the same issue, I think I can safely say it's not a plus net issue it's a WD issue I'll go back to chasing them!

[#15]

@cmg 

In the longer term, if you want to remotely access your NAS I recommend buying a router that supports Wireguard.

That removes any NAS manufacturer "man in the middle" and is fairly secure.