by YuriVoinov

Signal Messenger

Warning: Any example presented here is provided "as-is" with no support or guarantee of suitability. If you have any further questions about these examples please email the squid-users mailing list.


The default configuration file for Squid only permits only HTTPS port 443 to be used with CONNECT tunnels.

Signal Messenger uses custom ports 4433 and 8443.


This configuration is useful to pass Signal Messenger traffic through a Squid proxy.


As described above, Squid (in most cases) deny Signal bootstrap connect.

How initial Signal bootstrap works?

Signal Messenger tries to perform an HTTP CONNECT to via port 80, 4433, 8443. When two or more attempts are successful, it initiates a WebSocket connection to the available server port.

Squid Configuration File

Paste the configuration file like this:

acl SSL_ports port 4433 8443 # Signal Messenger

With the above your regular access permissions for any given client are applied to Signal. Just the same as if it were performing HTTPS connections.

  • {X} Note that port 80 is still too unsafe to allow generic CONNECT to happen on it. However, Signal client often can't do initial connect without permission CONNECT to port 80 at You are warned.

If your proxy is configured to use Features/SslPeekAndSplice, also add this to configuration:

acl DiscoverSNIHost at_step SslBump1

acl NoSSLIntercept ssl::server_name

ssl_bump peek DiscoverSNIHost
ssl_bump splice NoSSLIntercept
# other SSL-bump rules ...

and reconfigure.


ConfigExamples/Chat/Signal (last edited 2021-07-03 09:49:50 by FrancescoChemolli)