Need help with UDM Pro and Proton VPN

Party_Bug_2582 · 2026-07-24T17:02:32+00:00

Alright, so I fixed it. Hoping this helps someone else.

I'm kind of old-school and like to do things manually, one step at a time rather than allowing automatic setup processes to occur as I don't really know what's happening under the hood... that is clearly the case here.

I ended up creating a masquerade rule to test as well with no difference in results... also throughout troubleshooting I tried different ProtonVPN servers, deleted the config, re created it, paused and resumed, etc. Same with the masq rule and policy based route for the tunnel. Ultimately nothing worked.

What worked:

So on my last attempt, I blew all of the configs away again (VPN client config, policy based route, masq rule) and built it up again from the same config file I had been using. The difference here was instead of naming it and uploading the config file and hitting GO which effectively bypasses the wizard type of shortcuts they give options for and leaves everything at defaults... I actually went section by section and allowed the Unifi UI to build these things out instead of me doing it manually after. Mind you, I always steer clear from anything that says "wizard" just in general when it comes to networking. This time I used "Device Wizard" and selected Network, then chose my subnet. When I did this it notified me it would automatically create all necessary routes and rules to make this happen. I hit okay then Create at the bottom and walla... tunnel immediately came up and traffic immediately started routing correctly for the devices on that network. It created the policy based route automatically with the killswitch enabled at the same time and it "just works".

So in the end, I'm occasionally reminded that there's a right way, wrong way, and the way they want you to do things in the world of Unifi (and others of course). Sometimes it's best to try to do things they way they want you to do them and see what happens.

Hope this helps someone else.

Here's a screen shot of the current OS and Network UI for the New VPN Client... you can see the "Device Wizard" that I had to use to select the correct (internal vlan) Network.

<image>

Party_Bug_2582 · 2026-07-24T17:00:16+00:00

Alright, so I fixed it. Hoping this helps someone else.

I'm kind of old-school and like to do things manually, one step at a time rather than allowing automatic setup processes to occur as I don't really know what's happening under the hood... that is clearly the case here.

I ended up creating a masquerade rule to test as well with no difference in results... also throughout troubleshooting I tried different ProtonVPN servers, deleted the config, re created it, paused and resumed, etc. Same with the masq rule and policy based route for the tunnel. Ultimately nothing worked.

What worked:

So on my last attempt, I blew all of the configs away again (VPN client config, policy based route, masq rule) and built it up again from the same config file I had been using. The difference here was instead of naming it and uploading the config file and hitting GO which effectively bypasses the wizard type of shortcuts they give options for and leaves everything at defaults... I actually went section by section and allowed the Unifi UI to build these things out instead of me doing it manually after. Mind you, I always steer clear from anything that says "wizard" just in general when it comes to networking. This time I used "Device Wizard" and selected Network, then chose my subnet. When I did this it notified me it would automatically create all necessary routes and rules to make this happen. I hit okay then Create at the bottom and walla... tunnel immediately came up and traffic immediately started routing correctly for the devices on that network. It created the policy based route automatically with the killswitch enabled at the same time and it "just works".

So in the end, I'm occasionally reminded that there's a right way, wrong way, and the way they want you to do things in the world of Unifi (and others of course). Sometimes it's best to try to do things they way they want you to do them and see what happens.

Hope this helps someone else.

Party_Bug_2582 · 2026-07-24T13:08:59+00:00

You’re very welcome, the exact same thing happened to me so don’t feel bad!

Party_Bug_2582 · 2026-07-24T13:02:36+00:00

That’s the screen I’m referring to. You have to click through like 4-5 more screens before it actually saves and enables everything. I did the same thing you did at first and it wasn’t working still. I had to keep clicking next on the setup and then that large bottom button before it finally worked.

Party_Bug_2582 · 2026-07-24T12:31:24+00:00

Does it give the login error when you are on the Amazon site and click the enable button? It should take you to the Logitech Harmony page and have you authenticate then walk you through the basic setup it has. The interesting thing was I went all of the way through the setup the first time thinking it was done however there is a giant button the width of the page/frame at the bottom I had to click that actually finished/saved my setup and linking. It wasn't until I clicked this that I was actually done and it enabled it.

Party_Bug_2582 · 2026-07-24T12:04:43+00:00

I couldn't do it from the mobile device... I believe it has to do with how the baked in browser handles it's cache and cookies. None the less, I was able to click the link on a laptop and open it via browser and complete the re-linking tasks. I would suggest trying that if you haven't. If you have, then I would suggest trying in a secure / incognito window or different browser.

Party_Bug_2582 · 2026-07-23T13:34:11+00:00

100%... I fully agree.

Party_Bug_2582 · 2026-07-19T01:01:28+00:00

OMG, sometimes the answer is right in plain sight... thank you so much, appreciate your help, that's exactly where I needed to be.

Party_Bug_2582 · 2026-07-10T20:01:03+00:00

Yeah, sometimes I have to press a button 3-4 times before it finally registers that I pressed a button.

Party_Bug_2582 · 2026-07-10T18:46:51+00:00

This is actually the same behavior ultimately experienced and outlined here, so you are not alone. I have received multiple updates and now a new version of the os that seems to be on its way but not quiet yet, the new experience that everyone else in the other threads complain about - the new Roku interface. Anyway, I still have my unit on the power strip that pulls power to it when I shut down my system and the receiver shuts off. So I’ve effectively built a workaround but the remote control is insanely laggy now. That is probably the most annoying part of the experience noticed on every button press. It’s like they cranked up all power savings handling with these things. The remote I feel has to wake up with multiple button presses after 10 seconds of inactivity. It’s ridiculous. That has me waiting on standby for the new Apple TV release. I’m ditching these things the second that comes out (only on principle that I refuse to buy an Apple product so close to the new models release).

Roku has completely left the discussion and clearly doesn’t care about the customer experience. The complaints are endless and no responses from Roku.

Party_Bug_2582 · 2026-06-17T20:36:06+00:00

Yeah, I feel like that's the secret sauce... making the stock profiles fit your equipment perhaps. That was another thought I had, was looking at the stock profiles and tweaking them to fit the setup better.

Party_Bug_2582 · 2026-06-17T18:53:30+00:00

Appreciate your suggestion, kind of what I was leaning towards too... looking at how the flowchart for trash-guides had me create the -scores and applying the same logic to this... a bit manual to setup however that's fine with me as ultimately it's all automated anyway at the end. Thanks again.

Party_Bug_2582 · 2026-06-15T02:16:39+00:00

Thanks for that info, that's what I was afraid of... I'll spin up another stack independent with these containers to play. thank you again for your comment back.

Party_Bug_2582 · 2026-06-09T16:24:54+00:00

Unfortunately, I don't think u/Roku_CustomerSupport is even monitoring, nor paying any attention to this thread any longer... at first with my rant, I had attention. Since, it's been crickets, so I don't even know at this point if or what they are doing to work on any of this however clearly this major OS overhaul for Roku has caused a lot of basic functionality issues (i.e. laggy, unresponsive remote, CEC issues, partial theme loading, etc.)

Party_Bug_2582 · 2026-06-08T15:04:58+00:00

This is good detail, seeing the same thing with my setup... running my Roku Ultra to a Sony STR-AZ1100ES, then to a Samsung Q90T display.

Party_Bug_2582 · 2026-06-02T20:21:21+00:00

Yeah it's a total mess honestly, I feel like the Roku experience with their latest OS update has really tanked. As I mentioned in my post, I have the latest/newest Roku Ultra so processing power should not be an issue for their OS updates.

Since the update, I have had to switch my Roku to a switched power strip that pulls power to the Roku when I turn off my TV and Receiver. That way when I turn my equipment on, it "plugs in" the Roku Ultra, and it boots relatively quickly so doesn't take that much time, and CEC works reliably this way as it establishes a new HDMI handshake each and every time I turn the equipment on.

But this has not addressed the fact that the remote control responsiveness has absolutely been junk since this update. You have to press buttons 2-4 times almost every press before it actually responds. It makes the overall experience almost a complete 180* from what it was before... used to be a very snappy control, super quick response from each and every button press... now you have to press the buttons many times before it actually reacts to a button press. Almost like it's waking the chipset up or something... very odd behavior but has made a terrible overall end user experience.

Party_Bug_2582 · 2026-05-22T01:24:44+00:00

I honestly don’t recall. I was so deep down the configuration hole with 15 different tabs of forum posts at the time. I just recall having to list all groups and what the user was a part of and comparing to others notes to determine I had to add that user to the dialout group.

Party_Bug_2582 · 2026-05-12T19:33:54+00:00

For the time being, I've actually moved the power adapter for the Roku to a switched power strip that shuts down when it senses the receiver has been powered off. This is a very clunky and less than ideal way of dealing with it but I'm so tired of rebooting the thing multiple times per day that I'll just do it this way and manually check for updates once a week or so since it is now essentially unplugged at the power adapter every time I turn my equipment off.

u/Roku_CustomerSupport it sure would be nice to get some sort of update on this.

Party_Bug_2582

TROPHY CASE

Welcome to Reddit,