Getting SSL worker for NextCloud in a docker container

Hello, hope someone can help. I’ve searched these forums for other people having issues with SSL but can’t seem to find quite the answer I need.

I have a home server running Ubuntu Server. On that I have CasaOS through which I’ve installed NextCloud.

My home router is an Asus that handles DDNS and uses LetEncrypt to apply an SSL certificate to my external domain name. I have wildcards enabled.

I have port forwarding set up to direct traffic from ports 80 and 443 to the relevant ports on my NextCloud installation.

So far so good.

My android device works fine but will only connect using unsecured connection. My partner’s iphone refuses because it insists on secure connection.

I can connect using https to my router interface from outside using the DDNS domain.

I can connect to my CasaOS dashboard on the server using https. So the SSL certificate works so far.

But I can’t connect to NextCloud. For some reason it’s not making that final hop to the docker container NextCloud is running in.

Can anyone explain to me (as you would a toddler!) why this doesn’t work and what I need to do to make it work?

I keep reading about proxy managers like Nginx or traefik - Is that what I need to do? I don’t really want to add another layer of complexity to this, but I will do so if necessary.

As you can probably tell, I only have a very superficial understanding of what I’m doing here, so I’d appreciate any help.

it seems you mix different fact…

and

don’t really match together. The second statement means you allow direct connection from the internet to your nextcloud without any TLS certificates.

You need a “reverse proxy” in between - I’m not aware of any SOHO router capable of doing this. look at 101: reverse proxy.

Thanks for the help, much appreciated. I decided to cut the router out of it and use a proxy manager as you suggested. All working now.

2 Likes

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.