Cant access NAS after default port change

[DataGeek]

Long term DS418 user, love the product, I changed my default ports from 5000/5001 (and checked the convert http to https), but now cant access using previous local browser technique? Get error message:

The webpage at https192.168.1.199:50xx might be temporarily down or it may have moved permanently to a new web address.
ERR_UNSAFE_PORT

I can still access via Quickconnect ok. I cant bypass this error. Have I picked a restricted port? I did see a similar thread here that mentions a new cert is needed?

 

[DataGeek]

My router Verizon Fios G1100, does have loopback/hairpin/reflection functionality, but I cant see where its configured.

I can use my DDNS Name with external IP locally, so it must be turned on.

This DDNS name is configured? using my Routers external IP address....? Do I need to add port number (port forwarding for nas ip .199 to get to my NAS?

update, making headway, using DDNS name, with unique https port, gains me local access, but still get "not secure". DSM shows green cert for this name? Here is pix:

But my DSM shows my cert as green:

 

[DataGeek]

update, making headway, using DDNS name, with unique https port, gains me local access, but still get "not secure". DSM shows green cert for this name? Here is pix:

View attachment 27629

But my DSM shows my cert as green:

View attachment 27630

More Progress:

"Configured" cert from .199 to DDNS name, it cleared the https strikethrough, but still get "not secure"?

 

[DataGeek]

More Progress:

"Configured" cert from .199 to DDNS name, it cleared the https strikethrough, but still get "not secure"?

 

[Telos]

Is the security linked to the "system" under certificate configuration (control panel).

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

View: https://i.imgur.com/gSFB974.png

 

[DataGeek]

Is the security linked to the "system" under certificate configuration (control panel).

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

View: https://i.imgur.com/gSFB974.png

I think its linked to my DDNS Name? wont let me change it to synology default?

 

[DataGeek]

I think its linked to my DDNS Name? wont let me change it to synology default?

View attachment 27712

 

[DataGeek]

View attachment 27713

Update!! Just rebooted my win11PC and the "Not Secure" flag has gone away!

Here is Pix:

 

[DataGeek]

Update!! Just rebooted my win11PC and the "Not Secure" flag has gone away!

Here is Pix:

View attachment 27715

I'll summarize this Journey in the morning, ty all for your help (and training)!!!

 

[DataGeek]

This thread started due to my losing NAS mgmt access (but nas was still functioning) after making a change to the default ports (5000/5001) to improve security per popular guidelines. My access method was a Password manager who’s NAS URL was based on an IP address (192.168.1.199). Brain trust here recommended using DDNS/FQDN with router hairpin and Lets encrypt (LE) certificate to promote consistent (same URL) for both local and remote access to NAS server. Quick connect still worked, My newly assigned HTTPS port number appeared to be problematic, so I changed that, added (and cleaned up) my router port forwarding entries (added new HTTPS port forwarded to local nas IP), updated my NAS cert “configure” info (dsm/control panel/security/cert/configure), but still was getting “not secure” (but cert ok) on url window of my connected NAS. A final boot of my Win11PC cleared this condition (cleared browser cache?) to finally get a secure connection without alert flags. TY Rusty, Akahan, Telos for the guidance and training…

 

[DataGeek]

please mark solved...