Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[App Requests] Mumble #124

Open
anecdotal-testimonio opened this issue Feb 3, 2024 · 3 comments
Open

[App Requests] Mumble #124

anecdotal-testimonio opened this issue Feb 3, 2024 · 3 comments

Comments

@anecdotal-testimonio
Copy link

Hey,

I've recently switched over from Yunohost and I must say that I'm really pleased how cosmos server works, great software for self-hosting!

I've tried to get mumble to work with the official docker image, but unfortunately it keeps creating a self-signed cert inside the container and doesn't make use of the let's encrypt certs created with cosmos cloud.

Could you either give me a hint on how to make it work with cosmos cloud or even better, which would surely be helpful to others, create a pre-configured app in the market? Either of it would be very much appreciated!

Thanks for your work and this great software!

@azukaar
Copy link
Owner

azukaar commented Feb 3, 2024

Just let it use its self-signed cert, then when creating a route to the container, do https://mumble:port instead of http. Finally, make sure you tick "allow insecure HTTPS" so the self signed cert is accepted. Cosmos will then re-encrypt the traffic into your LE cert

@anecdotal-testimonio
Copy link
Author

Hello,

thanks for the hint. Unfortunately that did not solve the problem. After setting up a fresh mumble container and applying your proposed settings, I still get a self-signed cert warning (Murmur autogenerated Certificate v2) when connecting to the mumble server via the mumble client.

On the other side the LE cert is used when I connect to the corresponding domain via browser (but of course it shows a blank page, since the server has no UI itself)

Logs show multiple errors like this:
Connection closed: Error during SSL handshake: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate [13]

Any idea?

@anecdotal-testimonio
Copy link
Author

Found a workaround:

cosmos.config.json contains the two LE-cert parts, exctracting them and placing them in the mumble-volume in one file as key.pem + adding them to the config with an environment variable solves the issue - at least as long as the certs are valid.

Still would be cool to have a more straightforward way of solving this 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants