Squid webproxy blocking Discord voice chat?

1

I recently did a full reinstall of IP Fire and restored settings from a backup. After that, Discord will have a great deal of difficulty connecting to an RTC server to join voice channels. It will eventually after several repeated attempts but fails most of the time. If I configure a client to bypass the proxy, Discord can connect without issue.

I have the proxy running mostly defaults with it enabled on green and transparent on green and configured the DHCP rules for WPAD. I disabled the “Deny access to destinations hosted on selectively announced networks” rule because it was causing other issues after the reinstall as well.

I have URL filter enabled and am blocking adult and publicite off of Univ of Toulouse’s list. Discord doesn’t seem to be triggering those, though.

I tried clearing and even disabling the cache. I tried adding *.discord.gg, *.discord.com, *.discordapp.com to the excluded urls list and toggled Windows’ “Automatically detect proxy settings” off and on to try to get it to recognize the bypass list, the connections still fail if the auto detect setting is turned on and succeed if it’s turned off.

I’ve seen no other internet connection issues.

2

Are you using the IPS system.
Check logs for IPS and you may need to look threw the rules to find if.
uncheck and save changes

3

There are no hits in the IPS logs and simply bypassing the web proxy wouldn’t prevent IPS from tripping.

I can’t find anything in any of the logs that seem to correspond to this so far but Discord’s own logs show this:

[2025-06-22 11:31:36.888] [info] [RTCControlSocket(default)] [RECONNECT] wasClean=false code=0 reason=An error with the websocket occurred
[2025-06-22 11:31:36.889] [info] [RTCControlSocket(default)] [CONNECT] wss://c-ord12-0249fb78.discord.media:8443/
[2025-06-22 11:31:36.891] [warn] [RTCControlSocket(default)] [WS CLOSED] (clean: false, code: 0, reason: An error with the websocket occurred) retrying in 5.00 seconds.

4

Did you add ports in proxy for Discord.?

5

Can you be more specific? There is an entry for “1025-65535 # unregistered ports” in “allowed standard ports” (which covers 8443) that I’ve tried commenting out and leaving in, no effect. I also added port 8443 manually to ‘allowed SSL ports’ and it had no effect. Is there a different place I should put it / should I use a different port than 8443?

6

I’m not using proxy.
I’ve had the IPS block Discord in the past.
Not sure I can be of much more help.

7

I think I managed to fix this. I realized in the example for excluded URLS it had

*.ipfire.org*

I didn’t think the wildcard at the end of org was necessary so I put

 *.discord.media

and changing that to

*.discord.media*

with the trailing wildcard seems to have fixed this issue, at least for Discord.

1 Like
8

Hi,
can You please give more details, where You put the exclusion?
In the web-proxy settings page? And if so, where there exactly?
Or in the URL-Filter page - and where there?

I also have this problem with the Discord Webpage - but interestingly it’s working with the Discord-App.

Thank You!

9

Hi, you wrote transparent squid mode?
I think in these times all connections are encrypted and it doesn’t work with encrypted data. Normal squid mode, Discord ports and protocol has nothing to do with squid proxy.