out of no where today when I started mumble all my favorite servers were gone and when I tried connecting to my friend's server, this error message came up.
[10:30:24 PM] Reconnecting.
[10:30:24 PM] SSL Verification failed: The host name did not match any of the valid hosts for this certificate
[10:30:24 PM] SSL Verification failed: The certificate is self-signed, and untrusted
I have tried:
re-installing
the certificate thingy
ipconfig /release and /renew
*EDIT*
I went to C:\Users\squish\AppData\Roaming\Mumble and moved mumble.sqlite out of my folder and it resolved one issue but created another.
[10:37:38 PM] Connecting to server chi4.tragicservers.com.
[10:37:38 PM] Connected.
[10:37:38 PM] Server connection rejected: Wrong certificate or password.
(server connecting to does not have a password)
lol i fixed it I just had to change my name from squish to squishh
out of no where today when I started mumble all my favorite servers were gone and when I tried connecting to my friend's server, this error message came up.
[10:30:24 PM] Reconnecting.
[10:30:24 PM] SSL Verification failed: The host name did not match any of the valid hosts for this certificate
[10:30:24 PM] SSL Verification failed: The certificate is self-signed, and untrusted
I have tried:
re-installing
the certificate thingy
ipconfig /release and /renew
*EDIT*
I went to C:\Users\squish\AppData\Roaming\Mumble and moved mumble.sqlite out of my folder and it resolved one issue but created another.
[10:37:38 PM] Connecting to server chi4.tragicservers.com.
[10:37:38 PM] Connected.
[10:37:38 PM] Server connection rejected: Wrong certificate or password.
(server connecting to does not have a password)
lol i fixed it I just had to change my name from squish to squishh
pretty sure ur certificate was just corrupted or something, it's happened to me b4. if you make a new certificate, you can't keep your old name because the name from the old certificate is registered in the mumble and therefore another ticket cannot have that name. if it happens to you again, make a new ticket with a new name
pretty sure ur certificate was just corrupted or something, it's happened to me b4. if you make a new certificate, you can't keep your old name because the name from the old certificate is registered in the mumble and therefore another ticket cannot have that name. if it happens to you again, make a new ticket with a new name
you were connecting using the same name but different certificate
you were connecting using the same name but different certificate