frollard

Gonna need to know a bit more information: Are you running your own nginx to handle the letsencrypt part, or saying that you are using the discourse letsencrypt/nginx? If running your own - Do other https apps work correctly? Your nginx/SWAG config file is the most likely culprit. If you're getting far enough that the browser is saying it's not secure, it tells me nginx isn't configured correctly yet. Discourse does run its own internal nginx/letsencrypt which is configured through the built in config yml files.

Given the small heart attack I just had with leaky-vessel vulnerabilities, podman might be a really smort alternative. URL for vulnerability, remove if not allowed.

The thread groups up all of the packages released by this one author - not one thread per package as one might normally expect...so it's very scattered. The defaults for the mumble install should work so long as you don't want fancy features like proper SSL out of the box. What sort of errors are you running into? Default ports, pick a good superuserpassword (I believe it can't have any spaces in it), and start the container. I personally like using br0 mode where I can force the docker container IP address to something known that won't get clobbered on my network by the router dhcp server. ...then just connect with the regular mumble client. It will throw the error that the cert is self signed, and that's okay.

I can't for the life of me get this to work. Am I missing something in the forum formatting adding/removing spaces where there shouldn't be any?