Site not resolving over Dynamic DNS address

[muxketeer]

I'm currently running cherry, via docker, like this:

docker run -d --name cherry \
-v /home/user1/dockerfiles/cherryBookmarks/data:/data \
-p "8032:8000" \
-e "JWT_SECRET=mys3cr3cts0StronG43!" \
-e "ENABLE_PUBLIC_REGISTRATION=1" \
-e "USE_INSECURE_COOKIE=1" \
haishanh/cherry

I had to use the USE_INSECURE_COOKIE because it wouldn't let me login without that being set.

And now I'm able to wonderfully access it on my local network at http://192.168.1.25:8032. I.e. where my server is on my local network. I'm able to access that as long as, of course, I'm connected to my local network. That works great.

I'm using Chrome web browser through all this.

The problem now starts with me using my router's dynamic dns. We'll call it: https://mysynologyrouter.publicdynamicdns.com. I've configured my router to port forward the public port 33847 to my local port 8032. So, when I go to https://mysynologyrouter.publicdynamicdns.com:33847, I get a ERR_SSL_PROTOCOL_ERROR that says "This site can’t provide a secure connection."

I've tried to just access via plain http via a http://mysynologyrouter.publicdynamicdns.com:3387. However, my dynamicDNS provider appears to always auto forward http to https and then receives the same error. I know my dynamicDNS has all its letsencrypt certs in place because I have other services, such as Bitwarden, successfully using this dynamicDNS URL.

How do I get passed this ERR_SSL_PROTOCOL_ERROR error that says "This site can’t provide a secure connection" whenever I try to access Cherry via my dynamicDNS host name?