You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is an issue with the app, and contacting Mullvad support is not relevant.
I have checked if others have reported this already
I have checked the issue tracker to see if others have reported similar issues.
Current Behavior
When WireGuard obfuscation is set to automatic, the app appears to no longer try UDP port 53 when a connection cannot be made, meaning the user must either disable obfuscation or manually set the WireGuard port to 53 if they wish to try this method of circumventing censorship.
Expected Behavior
The app should still try UDP port 53 even when WireGuard obfuscation isn’t disabled as this is the only solution to bypass censorship on some networks.
Steps to Reproduce
Make sure WireGuard obfuscation is set to automatic
Attempt to connect on a censored network
Observe that as Mullvad cycles through possible solutions, UDP port 53 is not one of them
Failure Logs
No response
iOS version
17.4.1
Mullvad VPN app version
2024.2-beta3, but broken since WireGuard obfuscation was added
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Is it a bug?
I have checked if others have reported this already
Current Behavior
When WireGuard obfuscation is set to automatic, the app appears to no longer try UDP port 53 when a connection cannot be made, meaning the user must either disable obfuscation or manually set the WireGuard port to 53 if they wish to try this method of circumventing censorship.
Expected Behavior
The app should still try UDP port 53 even when WireGuard obfuscation isn’t disabled as this is the only solution to bypass censorship on some networks.
Steps to Reproduce
Failure Logs
No response
iOS version
17.4.1
Mullvad VPN app version
2024.2-beta3, but broken since WireGuard obfuscation was added
Additional Information
No response
The text was updated successfully, but these errors were encountered: