Problems with SSL/DuckDNS

Hello.
I have searched around and still in trouble.
I Can´t get the SSL to work.
I get the ERR_SSL_PROTOCOL_ERROR when I try to acess through Google home, and through Google Chrome.

First some info.
RPI 2
copy from configuration.yaml
http:
base_url: mydomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

Copy from setup in duckdns addon:
{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “my token from duckdns”,
“domains”: [
“mydomain dot duckdns dot org”
],
“seconds”: 300

Log from Duckdns:

INFO: Using main config file /data/workdir/config

  • Account already registered!
    Fri Dec 28 13:26:38 UTC 2018: OK
    My WAN IP
    NOCHANGE

INFO: Using main config file /data/workdir/config

Processing domain

  • Checking domain name(s) of existing cert… unchanged.
  • Checking expire date of existing cert…
  • Valid till Mar 27 17:48:52 2019 GMT (Longer than 30 days). Skipping renew!

Ports in my router, I went crazy, when it did not work so:
443-443 to Pi IP
443-8123 to Pi IP
8123-443 to Pi IP
8123-8123 to Pi IP

In the start I only had 443-443 and 8123-8123
The domain is working fine with HTTP, not HTTPS
I also tried in the configuration.yaml to have https:// at my domain, nothing changes.

Can you tell me where the error is?

I have a similar error. Apparently the let’s encrypt has configured the fullchain and privkey successfully. I also have the port forwarding on the router (443 -> 8123 & testing 80 -> 8123).
If I try to connect from internet to http://mydomain.duckdns.org, it works. If I try https, it doesn’t only if I use the http with :443 is goes through…
Is that normal?