Access services via HTTPS

[Nealwi]

Hi all,

Not sure if this is a QNAP thing, a general web thing or something different (I am very new and learning this stuff).

I have Ombi running in Docker on the QNAP (TS251D) and everything was works fine.
I had a domain linked to it (originally running through No-IP for DDNS services and) and that worked fine using HTTP, all traffic was coming in on specific port. I am double NAT'd so had the incoming port mapped from the modem (actually a router setup as just a modem) through to my actual router (Asus RT- AC85P), then forwarded from there to my NAS on the port OMBI is using. I am double NAT at the moment as my ISPs router (TalkTalk) is garbage and has numerous known issues, but I needed something to provide the modem functions to the ASUS which I can config better.

I then wanted to take it a step further and set it all up to use HTTPS but am having some problems.

I have setup a new domain which is HTTPS enabled using Lets Encrypt. I have setup web forwarding for that domain directly through to my home IP on the same port for testing, but it doesn't work. I get a response telling me "The Connection for this site is not secure"

I did previously have MyQNAPCloud disabled as I never needed it, however did enable it last Friday as I may have needed to access it from my parents. That is the only thing I have changed on the server, disabling it again does not resolve the issue. MyQNAP Cloud is also using the default Lets Encrypt certificate.

Should point out I can't even get in using HTTP now, not sure if there is some setting that has been changed somewhere that I am missing?

Can anyone give me some pointers or things to look at?

I suspect this is may be a relatively simple thing and I am falling foul of my lack of experience.

Any help appreciated.

[FSC830]

Read the link(s) in my signature and the other threads concerning malware/ransomware.
A lot of this happens because of the use of myqnapcloud!
Even QNAP does recommend not to use myqnapcloud any longer!
If you need access from internet to your LAN, use a VPN - nothing else!

Regards

[spile]

Even QNAP does recommend not to use myqnapcloud any longer!

Are you sure you meant that link?

“ Set up myQNAPcloud on the NAS to enable secure remote access and prevent exposure to the internet.”

[FSC830]

If you read the whole advisory, you will see that QNAP recommends "Deselect Enable UPnP Port forwarding" and "Deselect all items under Publish" and in further steps they advise how to setup myqnapcloudlink.

Regards

[spile]

If you read the whole advisory, you will see that QNAP recommends "Deselect Enable UPnP Port forwarding" and "Deselect all items under Publish" and in further steps they advise how to setup myqnapcloudlink.

Regards

It’s the recommendation to enable “MyQnapCloud” (note no Link”) that is a potential source of confusion in that particular page.

[FSC830]

It’s the recommendation to enable “MyQnapCloud” (note no Link”) that is a potential source of confusion in that particular page.

I did not use any of this stuff, but as far as I know myqnapcloud is needed to setup myqnapcloudlink?
In steps 6 to 8 the setup of myqnapcloudlink and accessing the NAS with smartlink is advised.
So my understanding is that the "typical" myqnapcloud access was done by UPnP and port forwardinge, both are not any longer recommended in that advisory.

Is that wrong?

Regards

[spile]

It’s the recommendation to enable “MyQnapCloud” (note no Link”) that is a potential source of confusion in that particular page.

I did not use any of this stuff, but as far as I know myqnapcloud is needed to setup myqnapcloudlink?
In steps 6 to 8 the setup of myqnapcloudlink and accessing the NAS with smartlink is advised.
So my understanding is that the "typical" myqnapcloud access was done by UPnP and port forwardinge, both are not any longer recommended in that advisory.

Is that wrong?

Regards

Personally I would not recommend using either.