Signal Desktop cannot connect to chat.signal.org on Linux, preventing QR code from loading

Using a supported version?

• I have searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Bug description

Signal Desktop starts normally on my Arch Linux / Omarchy system, but it cannot connect to the Signal service and therefore never displays the QR code for linking the desktop client.

The application shows:

Something went wrong — failed to connect to server

Clicking Try again does not make the QR code appear.

Environment

• OS: Omarchy Linux / Arch Linux
• Architecture: x86_64
• Desktop environment: Wayland
• Signal Desktop: installed from the Arch/AUR package
• Signal Desktop executable: /usr/bin/signal-desktop
• User is attempting to link Signal Desktop to an existing mobile Signal account

Question

Could someone confirm whether chat.signal.org is currently expected to accept TLS connections from Signal Desktop in this configuration, and whether there is a known issue affecting Linux/Arch/Wayland clients?

The fact that:

• signal.org is reachable
• updates.signal.org is reachable
• chat.signal.org is reset during the TLS handshake
• the problem persists with UFW disabled
• the problem persists on a completely different network/mobile hotspot
• the QR code consequently never appears

makes me suspect either a Signal Desktop networking issue, a current server-side/network-path compatibility issue, or a change in the endpoints/protocol used by the current Signal Desktop release.

Steps to reproduce

Steps to reproduce

1. Install Signal Desktop on Omarchy/Arch Linux
2. Launch signal-desktop
3. Wait for the initial connection/linking screen
4. Signal displays "Something went wrong — failed to connect to server"
5. Click "Try again"
6. QR code never appears

Expected result

Expected behavior

Signal Desktop should successfully connect to Signal's servers and display the QR code so that the desktop client can be linked to the mobile Signal application.

Actual result

Actual behavior

The desktop client cannot establish a connection to the Signal service and the QR code never loads.

Network diagnostics

General Signal connectivity works:

curl -I https://signal.org

HTTP/2 200

The update server also works:

curl -I https://updates.signal.org

HTTP/2 200

However, chat.signal.org consistently fails:

curl -4 -I https://chat.signal.org

curl: (35) Recv failure: Connection reset by peer

I also tested both resolved IPv4 addresses directly:

curl -4 -v --resolve chat.signal.org:443:76.223.92.165 https://chat.signal.org

and:

curl -4 -v --resolve chat.signal.org:443:13.248.212.111 https://chat.signal.org

Both connections reach the TLS ClientHello stage and are then reset:

TLSv1.3 (OUT): TLS handshake, Client hello (1)
Recv failure: Connection reset by peer
OpenSSL SSL_connect: Connection reset by peer

I also tested using OpenSSL:

openssl s_client -connect chat.signal.org:443 -servername chat.signal.org

Result:

CONNECTED(00000003)
write:errno=104
no peer certificate available
SSL handshake has read 0 bytes and written 1557 bytes

The connection is therefore being reset before the server sends a TLS certificate.

Additional tests

I tested the connection while connected to my normal Wi-Fi and again using a mobile phone hotspot. The result was the same on both networks.

I also temporarily disabled UFW:

sudo ufw disable

and tested again:

curl -4 -I https://chat.signal.org

The connection was still reset:

curl: (35) Recv failure: Connection reset by peer

UFW was then re-enabled.

There are no HTTP/HTTPS proxy environment variables:

env | grep -i proxy

returned no output.

System time is synchronized:

System clock synchronized: yes
NTP service: active

Signal Desktop terminal output

Launching Signal with:

signal-desktop

shows the following GPU/Wayland warning:

ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249
'--ozone-platform=wayland' is not compatible with Vulkan.
Consider switching to '--ozone-platform=x11' or disabling Vulkan

However, Signal continues running and the primary problem remains the failure to connect to the Signal service.

Screenshots

No response

Signal version

8.27.0-1

Operating system

Omarchy Linux

Version of Signal on your phone

No response

Link to debug log

No response