-
Notifications
You must be signed in to change notification settings - Fork 38
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
Not connecting in ubuntu 20.04 #285
Comments
As a workaround, when connecting, expand My current guess is there's an issue with Edit: After other edit attempts failed, manually editing the compiled Edit 2: I've not been able to figure out the SSL/TLS bug, so I've set up |
Work around SSL/TLS bug on Ubuntu 20.04+ by disabling the "securecore" setting. As the core connection is via 'localhost', the potential impact is reduced. See magne4000/quassel-webserver#285 Also work around a Quassel Webserver bug where the "securecore" setting does not get applied by default if set to false. This can be dropped once the upstream pull request is merged. See magne4000/quassel-webserver#290
Yes i had it localhost and it worked. But now my quasselcore shifted to another machine so now I cannot use this workaround. Seems it is referenced in a commit. Will check that out and see how it works. |
I have just tried it in ubuntu 20.04, my quasselcore is in ubuntu 18.04. Doesn't directly work with ssl core connection enabled in quassel-webserver. I have to disable it once, connect to my core. then logout and then from next time onwards it works with ssl core connection ticked. after that it works like normal. |
This comment can be of interest magne4000/node-libquassel#25 (comment) |
The suggestion above about disabling "SSL core connection" doesn't work for me. The core log still shows even with that option unchecked:
|
Used to work fine in Ubuntu 18.04 but does not work in 20.04. The client connects and disconnects immediately.
There seems to be some tls error. Here are the error logs from quasselcore: https://p.ip.fi/HYvY
The text was updated successfully, but these errors were encountered: