Add Wireguard Port 80 to the app

[Sundosa]

Is it a bug?

• 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

It is not possible to set the port to 80 without using an obfuscation method. Connecting manually via wireguard app works though.

Expected Behavior

The app should allow the assignment of port 80 even without using an obfuscation method.

Steps to Reproduce

1. Set obfuscation to off
2. Try assigning port to 80.

Failure Logs

Android version

13

Device model

Generic Android

Mullvad VPN app version

2025.11

Additional Information

The only way I can connect to the VPN is via port 80 & 443 while obfuscation is off. Since port 443 has been reserved for QUIC, however, I can only connect via port 80 via wireguard app for now.
This issue is present in the desktop versions as well.

[MarkusPettersson98]

Hi @Sundosa, settings a custom WireGuard port is now considered an 'obfuscation' method. See #9577 (comment).

[Rawa]

We aim to release a new version of the Android app in the coming weeks, where the wireguard port selection will be part of obfuscation.

[Sundosa]

I see that all of these options have been moved to a new menu in the new versions of the app.
I am specifically talking about the obfuscation protocols such LWO & shadowsocks; none of those work (they connect but no online connectivity).

[Rawa]

I see that all of these options have been moved to a new menu in the new versions of the app. I am specifically talking about the obfuscation protocols such LWO & shadowsocks; none of those work (they connect but no online connectivity).

I'm not following what the bug is here? We do not offer port selection for LWO as of right now. Regarding shadowsocks, only some servers support all ports, most of them only support a small subset, 51900-51949. It would be great to know what you mean by "They connect but no online connectivity", how do you reproduce this?

Regarding port 80, as of right now some relays may support it but it is not included in the published relaylist, I've posted the question internally why this is the case. However, if the request here is for us to add support for port 80 I'd argue this is not a bug report but rather a feature request.

[Sundosa]

I'm not following what the bug is here?

My issue is that my corporate network blocks all obfuscation protocols and all ports on a bare wireguard connections with the exception of port 80 and 443, as mentioned above. My request is to make port 80 available via the app.

"They connect but no online connectivity", how do you reproduce this?

This issue happens on my corporate network. The app says it connected but doesn't have any actual internet.

However, if the request here is for us to add support for port 80 I'd argue this is not a bug report but rather a feature request.

I made it a bug report because I didn't think it would be intended for that port to only be accessible via WireGuard config. This is exactly my request by the way so feel free to change the issue to a feature request (couldn't find a way to change it myself).

[Rawa]

I've converted it to a discussion, as it is more of a feature request (the UDP port 80)

80, 443: TCP is used by UDP-over-TCP
443: UDP is used by QUIC

Some servers have additional in IPs for shadowsocks, where all UDP ports work, this is not most relays though. Regarding port 80 UDP, I've yet to receive a reply internally. Either it is reserved, to be used at a later stage, for something with UDP, or it should be added to the relay list. I'll get back to you when I got an answer.

Regarding the connection issue on the corporate issue with the app saying "Connected" but not being able to reach the internet it sound strange. Is this on both windows and android? Do you get an "out ip" if you expand the Connection panel on the home screen? Are you able to ping anything, e.g 1.1.1.1? Also feel free to reach out to our support, support@mullvadvpn.net that may help out with questions like this.

[Sundosa]

Is this on both windows and android?

yes

Do you get an "out ip"

no, only an "in ip"

Are you able to ping anything

Nope, nothing at all.

Also feel free to reach out to our support

Unfortunately I already had and tried every possible combination of configuration; no luck :(.

[Rawa]

I've not gotten a full response yet, but it seems like port 80 was at some point intended to be used by some other protocol which never fully materialized, thus it was reserved for future use. It seemingly have been repurposed, since it never materialized, and then was offered as a WireGuard port. However, since it is reserved and it has not been included in the app or officially supported.

I've asked if we can add support for it in the app, but I'm not sure if we can get a decision on it, since it is currently a very user-specific request with low demand, and I'm not sure of the future plans for port 80 UDP.

no, only an "in ip"

Then this hints at the traffic most likely are getting blocked. I'm sad to hear that the other obfuscation methods have not worked. :'(