I had previously been using quassel-web and quassel-core running on the same host. I hadn’t used it in some time, and when I recently tried to use quassel-web I get this error in the web UI:
Error: No status code was provided even though one was expected.
In the quassel-core log:
2023-07-30 22:19:12 [Info ] Client connected from 172.19.0.2
2023-07-30 22:19:12 [Warn ] "Socket error 13: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm"
2023-07-30 22:19:12 [Info ] Non-authed client disconnected: 172.19.0.2
I get the same log messages regardless of whether “SSL core connection” is checked in the quassel-web UI or not. Desktop client connects to the core fine.
I tried setting up an entirely separate docker compose environment with just these two containers to make sure it wasn’t something else going on with my larger compose config and get the same error. The minimal setup is:
version: "2.1"
services:
quassel-web:
image: lscr.io/linuxserver/quassel-web:latest
container_name: quassel-web
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- QUASSEL_CORE=quassel-core
- QUASSEL_PORT=4242
volumes:
- /home/trolley/quassel/quassel-web:/config
ports:
- 64080:64080
restart: unless-stopped
quassel-core:
image: lscr.io/linuxserver/quassel-core:latest
container_name: quassel-core
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
volumes:
- /home/trolley/quassel/quassel-core:/config
ports:
- 4242:4242
- 113:10113 #optional
restart: unless-stopped
I found one reference to exactly this problem, where someone bumped an old issue on the Quassel Web repo but didn’t get a response.