nightstorm

If you follow the process above you should see servers. Other than that the only difference would be a different cloud version, in which case when we do the next update that'll be sorted.
It'll be because the server is whitelisted if you can provide the ID we can remove it and that will prevent it.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

I've messed around with Wireshark a bit but find Netlimiter is much easier to use for this type of thing. It will show a list of all connections that are open on your system (sorted by what program is making the connections) and what IP/port they are using as well as how much bandwidth they are using.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

So fun fact... TCP port 443 is now used for geolocation in general, not just on console. It used to be done on UDP port 3074 and I've been tearing my hair out trying to figure out why it wasn't successfully spoofing my region anymore. You just inadvertently solved my issue
But circling back to OP's problem - imo the best solution is configure Hybrid VPN with an OpenVPN config file from Express VPN, then set it up to only route TCP port 443 and UDP port 3074 (UDP 3074 is still used for matchmaking traffic).
Voila! You now have the same functionality that NoLag VPN provides for much less money. And I see no reason why it wouldn't work on console.

If the goal is only to truncate its geolocation on COD, while keeping the best ping on the closest servers, any VPN can do it.
Geolocation on console works in https on TCP port 443.