DELETE MUMBLE CERTIFICATE ON SERVER CODE

DELETE MUMBLE CERTIFICATE ON SERVER CODE

I have not looked in the code base to see if the current certificate is tied in any way to Access Tokens set on clients (or somehow it forms part of what makes a 'server' and clients see it as a new connection and drop the access tokens?). If applicable, add screenshots to help explain your problem.ĭesktop (please complete the following information): Restarting murmur to pick up a new certificate that was generated should not remove any Mumble client settings for Access Tokens for that server. Client-side server access token is missing on mumble clients of various OS/version/platform connecting to it.Replace an SSL/TLS certificate configured via sslCert= and sslKey=.Add an access token from a client connecting to the server.I quite like using Let's Encrypt and really don't want to issue a longer-term self-signed certificate if indeed client-side (Mumble) access tokens are somehow tied to issued Murmur Server certificates. If so is there a way to turn this off? Lets Encrypt renews their certificates every 60-90 days or so and it'd be a real hassle for people to re-add the same Access Token just because the certificate is changed. There's not a lot in the murmur server logs, but I can confirm the access token for my client was also missing and needed to be re-added.Īre access tokens (from a client perspective) tied to the identity of a server + unique certificate at the time? Is there a defacto expiration time for tokens otherwise? (I wouldn't think so). I couldn't understand why replacing the TLS/SSL certificate and restarting murmur would cause a client side change unless Access Tokens are based on the current certificate? On this server we use Access Tokens to grant certain access to some channels and clients needed to re-enter their access token as it was missing on all their Mumble clients after the SSL/TLS certificate was renewed and the Murmur server restarted. This of course replaces the SSL certificate but it still utilizes the same key/cert name in my mumble.ini. I run a murmur server that utilizes Lets Encrypt certificates, when there's a SSL/TLS renewal for the domain I use the post-hook functionality of Certbot to restart mumble.

Delete mumble certificate on server