How to setup a public VaultWarden using Docker Compose when you don't own or control your own domain?

[Hammit]

I have sucessfully setup VaultWarden locally and used the DuckDNS instructions to get HTTPS working. The problem with that is that it only works locally and a port forward on my router doesn't work when accessed externally.

I don't own or control a domain but would like to host VaultWarden myself and access external to my network (publicly). Is this possible? How if so?

[stefan0xC]

You have setup a DuckDNS domain which is pointing to your routers public IP, no? You port forward requests from your router to your server and got HTTPS to work (presumably with Let's encrypt)?

What exactly does not work? Can you explain your setup a bit more because I don't think I understand from the provided information. Does your container listen on the correct interface? Do you use a reverse proxy? Does the DuckDNS domain point to the correct IP address? Which ports do you forward? Have you port forwarded the HTTPS port as well?

If it works locally you can also enable the /admin panel and provide the support string (which might help identify other issues).

[Hammit]

Ok. Your answer was helpful and perhaps early confusion about how things worked needed setting aside. I believe it's working now.
What got it finally working was forwarding both HTTP and HTTPS ports.

Thank you again :)