search

magne4000 / quassel-webserver

A web server/client for Quassel
MIT License
210 stars 38 forks source link

Not connecting in ubuntu 20.04 #285

Open the-loudspeaker opened 4 years ago

the-loudspeaker commented 4 years ago

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

digitalcircuit commented 3 years ago

As a workaround, when connecting, expand more options and disable SSL core connection. Not ideal, but if your Quassel core is localhost, it's not the end of the world.

My current guess is there's an issue with node-libquassel with newer (TLSv1.3) setups. Instead of secureProtocol in createSecureContext() options, libquassel should use minVersion… but I'm still figuring out how to test these changes.

Edit: After other edit attempts failed, manually editing the compiled libquassel.js doesn't seem to work, either - setting minVersion still fails.

Edit 2: I've not been able to figure out the SSL/TLS bug, so I've set up securecore: false by default on Ubuntu 20.04+ since it's localhost anyways. Again, not ideal, but ah well.

the-loudspeaker commented 3 years ago

As a workaround, when connecting, expand more options and disable SSL core connection. Not ideal, but if your Quassel core is localhost, it's not the end of the world.

My current guess is there's an issue with node-libquassel with newer (TLSv1.3) setups. Instead of secureProtocol in createSecureContext() options, libquassel should use minVersion… but I'm still figuring out how to test these changes.

Edit: After other edit attempts failed, manually editing the compiled libquassel.js doesn't seem to work, either - setting minVersion still fails.

Edit 2: I've not been able to figure out the SSL/TLS bug, so I've set up securecore: false by default on Ubuntu 20.04+ since it's localhost anyways. Again, not ideal, but ah well.

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.

the-loudspeaker commented 3 years ago

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.

magne4000 commented 2 years ago

This comment can be of interest https://github.com/magne4000/node-libquassel/issues/25#issuecomment-988140501

mtrolley commented 1 year ago

The suggestion above about disabling "SSL core connection" doesn't work for me. The core log still shows even with that option unchecked:

2023-08-02 18:11:42 [Info ] Client connected from 172.18.0.6
2023-08-02 18:11:42 [Warn ] "Socket error 13: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm"
2023-08-02 18:11:42 [Info ] Non-authed client disconnected: 172.18.0.6