Quassel-web can't connect to quassel-core: SSL error

LSIO Discussion Container Support
,
1

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.

1 Like
2

Digging a little more I wonder if it’s this: libquassel won't connect to quassel core that only supports TLS 1.3 · Issue #25 · magne4000/node-libquassel · GitHub

1 Like
3

I am also getting this!

1 Like
4

I don’t know what prompted me to check this again, but it’s now working in my setup.

5

Turns out it’s more complicated than my last reply. It works fine in Firefox 118.0.1 on a Mac, but doesn’t work in Firefox 118.0.1 on Windows 11. The one thing I can think that’s changed since I last tried it is I updated to macOS Sonoma.

Windows:

2023-10-07 11:52:53 [Info ] Client connected from 172.18.0.8
2023-10-07 11:52:53 [Warn ] "Socket error 13: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm"
2023-10-07 11:52:53 [Info ] Non-authed client disconnected: 172.18.0.8

Mac:

2023-10-07 11:56:05 [Info ] Client connected from 172.18.0.8
2023-10-07 11:56:05 [Info ] Client 172.18.0.8 initialized and authenticated successfully as "trolley" (UserId: 1).
2023-10-07 11:56:05 [Info ] Client does not support extended features.

I removed my “Solution” tag from my previous post since it’s not completely solved.