https: am I wrong?

[sonusfaber 17]

Hello,

I discovered something strange on my Emby server behaviour. Really can not understand even after reading many times the guide.

Emby running on an Ubuntu VMWare VM. I want to reach Emby from the public network with https.
I have a personal domain, DNS and certificate and everything was running fine... let me say... I was supposed to think that was fine.
Yesterday the certificate expired, but... from the public network, pointing to the the url https://myemby.mydomain.it:8444 I get the message that the certificate is expired then the browser fallbacks to http and I can access Emby !!!!!

I do not want such behaviour at all: i need http on the LAN and only https on the WAN
I have a rule on the router that forward incoming connections to the public 8444 to 8920 on the LAN. No other rules are defined.
According to this, I supposed that nothing was being forwarded to other ports, just to the 8920 that is configured for https, but it responds also http.

Emby Network config page:
- LAN Networks: blank
- Local IP: blank
- Local http port: 8096
- Local https: 8920
- Allow remote connections: allowed
- Remote IP filter: blank
- Filter mode: whitelist
- Public http port: 80... but whatever I put does not change the story (router just forward 8444 to 8920)
- Public httpS port: 8444 (the one the router is listening from)
- External domain: blank
- Secure connection mode: required for all remote connections
- Auto port mapping: not checked
 

Am I wrong?

Many thanks

[Luke 43534]

Hi. What makes you think it falls back to http ?