If I may ask one more thing, how did you find out what port or protocol is needed ? I sadly have very little clue about network stuff but would love to be able to solve that by my own i the future.
And also i am surprised how well WoW runs on linux. Maybe i am biased but I feel like i have slightly more frames than on Windows.
Iām having this exact same problem and Iāve spent the last five hours trying to solve it.
It happened after Dragonflightās release. āConnectingā takes like 60 seconds now and the exact same error you describe is happening. A new install did not fix the issue.
If I stop firewalld, all of my problems are solved. So I guess I canāt forward the ports. Iāve tried many.
Am I even doing this right?
Edit: I should point out a temporary workaround for the massive frame spikes. You can delete the voice proxy executable. The error for that will stop appearing, but launching the game later will likely redownload it.
Sorry for double post, not allowed to send two pictures in one forum post apparently. Iāve found this on the Blizzard forums.
Just posting to say I have the same issue.
When I disable firewalld everything works great. When I re-enable firewalld it takes about 30 seconds longer to login, then the VoiceError message pops up every 30s with a juttering lag.
I tried sudo firewall-cmd --add-port=3724/udp but I get:
Warning: ALREADY_ENABLED: ā3724:udpā already in āFedoraWorkstationā
success
Which leads me to believe it should already be open?
Anyone have any advice who has fixed this?
Iām thinking itās because thatās the wrong port.
If you disable your firewall temporarily, everything works.
Iāve tried enabling every port imaginable from their forums and it just isnāt working.
Edit: I also have no idea how more people arenāt noticing this. Seems like there are enough Linux gamers that thereād be more attention to this issue. It makes me wonder if thereās just a few of us actually having this problem.
Those are the ports iāve found. It worked temporarily. Iāve since switched my firewall to OpenSnitchd instead. The only thing I can think of is firewalld blocking any communication between WowVoiceProxy.exe and Wow.exe. I donāt know enough about firewalld or felt like going into documentation to resolve it, and OpenSnitch is my preferred choice anyway.
Also the port it is trying to listen to is 6724 from the voice logs:
11/18 11:47:46.179 Voice Log Initialize.
11/18 11:47:16.186 WowConnectionNet: Initialize
11/18 11:47:16.186 MakeSocketPair attempt: 0, 1, 0, -1, 0
11/18 11:47:16.187 MakeSocketPair attempt: 0, 23, 0, 0, 0
11/18 11:47:16.287 VoiceProxy attempting to listen on 127.0.0.1:6724
11/18 11:47:46.288 WowConnectionNet: Shutdown
11/18 11:47:46.288 Voice Log Destroy.
Hello!
Iāve got the same issue with WowVoiceProxy.exe crashing continuously.
Iām using Fedora 37 at the moment and noticed the issue does not happen with firewalld 1.0.5, but does with 1.2.1.
It would be great if such specific downgrade fixes the issue for you as well!
I have same problem. Fedora 37.
Added all ports listed here, only disabling firewalld works.
Just thought I would post again to say the only thing working for me is to stop firewalld, then play wow, then reenable it once Iām done.
Donāt care too much now that I know it fixes it but probs not the best for security lol
Have you posted this over with the Fedora developers so they are aware of the issue?
I believe this is a Firewalld issue and not distro specific.
I have been having the same issues on up-to-date Arch, without having firewalld installed. Iāve also tried installing firewalld and starting/stopping it. As most reports here, the issues started after the release of 10.0. The login screen gets stuck at āConnectingā, but instantly connects after pushing the āReconnectā button that appears after ~60 seconds. While in game, I get the VoiceError 17 (and sometimes also 16).
Willov what firewall are you using on Arch?
I switched to UFW and it seems to be working normally now, I am on F37-KDE.
Talking to someone on Discord having the same firewalld issue on Endeavour. Does switching to UFW fix the issue?
It did for me, if it works for others please post here so we can verify the fix works. Login now takes about 3 seconds as well.
It is not really a fix if you change firewall software, more of a workaround if anything. If it was a fix it would still be using firewalld.
But yes it does work for obvious reasons, seeing as we donāt use firewalld then and the issue seems to be somewhere in firewalld.
I was using nftables/iptables. Now Iāve been testing firewalld.
Update: stopping firewalld resolves the issues. Perhaps I might have been running firewalld previously without rememberingā¦
Iāve been having this exact issueā¦takes a super long time to actually log in then ālost connection to the voice chat serviceā spam.
Iām on Fedora 37 wasnāt having this issue in 36 so something changedā¦
Can you forward ports in firewalld? Iāve actually never messed with it before.
Not entirely sure if that is the issue, but the 127.0.0.1 is in the zone Block, for me I donāt know if that zone always block communications outwards. But even opening ports in that zone doesnāt help
Or maybe it is because my own connection is in a FedoraWorkstation zone which seems to be the same as the Block zone (at least the description is the same)
Conent from FedoraWorkstation.xml file:
GNU nano 6.4 FedoraWorkstation.xml
<?xml version="1.0" encoding="utf-8"?>
<zone>
<short>Fedora Workstation</short>
<description>Unsolicited incoming network packets are rejected from port 1 to 1024, except for select network services. Incoming packets that are related to outgoing network connections are accepted. Outgoing network connections are allowed.</description>
<service name="dhcpv6-client"/>
<service name="ssh"/>
<service name="samba-client"/>
<service name="mdns"/>
<port port="1025-65535" protocol="udp"/>
<port port="1025-65535" protocol="tcp"/>
<forward/>
</zone>