- 4,027
- 1,378
- NAS
- DS4l8play, DS202j, DS3623xs+, DSM 7.3.3-25847
I'm attempting to end port-forwarding and using Cloudflare tunnels to do so. But connecting to the NAS seems odd to me. Some background...
Presently I use RP to reach my NAS DSM login. For example, in a browser URL I enter:
RP "translates" this as
https://<nsa_ip>:<nas_https_port>
That seems simple and it works.
After creating a CF tunnel, I added a "public hostname" with a subdomain of "nas1.mydomain.com", and a "service" of
https://<nsa_ip>:<nas_https_port>
However... no connection is possible... however if I change the "service" to
http://<nsa_ip>:<nas_http_port>
entering:
brings up the DSM login screen with a secure padlock.
Why is there a difference between RP and Cloudflare tunnel, that explains why HTTPS does not work with the tunnel, but seems to with the RP?
Have I done somthing wrong here?
Presently I use RP to reach my NAS DSM login. For example, in a browser URL I enter:
https://nas1.mydomain.com
RP "translates" this as
https://<nsa_ip>:<nas_https_port>
That seems simple and it works.
After creating a CF tunnel, I added a "public hostname" with a subdomain of "nas1.mydomain.com", and a "service" of
https://<nsa_ip>:<nas_https_port>
However... no connection is possible... however if I change the "service" to
http://<nsa_ip>:<nas_http_port>
entering:
https://nas1.mydomain.com
brings up the DSM login screen with a secure padlock.
Why is there a difference between RP and Cloudflare tunnel, that explains why HTTPS does not work with the tunnel, but seems to with the RP?
Have I done somthing wrong here?