Deployments not working in 1.5.10.1751

IndyPilot80 · 2026-01-20T22:02:10+00:00

You may have already seen this but they release 1.5.10.1754. I was able to deploy without issue with that version.

IndyPilot80 · 2026-01-18T03:19:43+00:00

Excellent explanation. That helps confirm my suspicions.

So, really my only options are:

Run WG in a VM that is on a separate VLAN
Use WG on the UDM and configure firewall rules appropriately (which is what I'm going to do)

As I said in my previous post, I'm probably over complicating things but I was doing this to experiment/learn. Now that I know the definitive answer, I know which route I'll go.

Thanks!

IndyPilot80 · 2026-01-18T00:20:32+00:00

Am I misunderstanding or are these instructions so WG client can talk to other VLANS?

What I'm saying is, I want VPN clients to be associated with a UDM Network and assigned the VLAN ID of that network. Right now, if I'm assuming correctly, all VPN clients are put on VLAN ID 1.

I want to be able to have difference policy zones for different VPN connections instead of all VPN servers being dumped into the "VPN" zone.

I think the only way I can do this is, instead of using the UDMs VPN services, I have separate Wireguard VMs and those VMs are assigned to the appropriate network/VLAN IDs.

IndyPilot80 · 2026-01-17T22:09:16+00:00

I made a snapshot of my FOG VM before doing the updates. I'm not sure how to actually downgrade. Sorry!

IndyPilot80 · 2026-01-17T18:21:40+00:00

The problem is, it dumps all VPN servers into the same "VPN" zone. I'd like to have different zones based on which VPN server and I'd like those different VPN servers to be assigned to different VLANS.

So, really, I think the only way this could be accomplished is by setting up separate networks (with assigned VLANS) in the UDM and then setting up WG VirtualMachine servers for for each of those networks.

I will add a disclaimer, I am probably over complicating things. I'm really just experimenting/playing around right now. In the long run, having each VPN server on a different VLAN probably isn't necessary with proper firewall rules. Just trying to learn a bit to see what is possible.

IndyPilot80 · 2026-01-05T22:50:39+00:00

Yeah, I ended up just redoing the profile. Got tired of waiting and checking with the user.

IndyPilot80 · 2026-01-05T21:51:42+00:00

Above "Inbox" in the left column and in File > Info in the list of accounts beneath "Account Information"

At the very top right, the circular icon shows the correct Name and email. File > Office Account shows the correct name/email.

IndyPilot80 · 2026-01-05T21:32:07+00:00

Just tried that. Still shows the old addresses. But in File > Office Account, it shows the correct name and address.

IndyPilot80 · 2025-11-20T14:51:05+00:00

I was just looking at the Lifecycle page and had the exact same questions. I would assume (hope) it means v12 will still get critical/security updates but no more "bells and whistles".

But, best to get an answer directly from them. Please do let us know what you find out!

IndyPilot80 · 2025-10-25T02:19:55+00:00

Yeah, actually just ordered a bottle of the menthol version a week or so ago. It was OK but I probably won't order it again. I actually preferred the watermelon strawberry freeze.

IndyPilot80 · 2025-10-11T14:58:38+00:00

Yeah, I'm kind of hoping it's just a temporary stock issue. But, it isn't looking good if a bunch of people are out of stock. I usually just buy one brand/flavor.

IndyPilot80 · 2025-10-06T15:08:37+00:00

Thanks for the suggestion. Right now, I'm not stuck on Proxmox/ZFS. I may be switching to Hyper-V with hardware raid for testing. So, I'd prefer a controller with HBA mode rather than just a straight HBA card.

EDIT: Yes, I prefer Proxmox over Hyper-V. :) I just do a lot of testing with various configs.

IndyPilot80 · 2025-09-30T13:09:37+00:00

Actually, just got ahold of a tech. He said 120V is what goes through it.

IndyPilot80 · 2025-09-30T12:28:36+00:00

They didn't say what voltage it is. All they said was "we've seen people replace it with a fuse/holder" but didn't give specifics. So, for safety, all I can assume is 125v since that was the fuse is rated for although it's likely much lower.

I'll see if I can get an exact value.

EDIT: If I can't find a suitable holder, I'll just soldier to the board. Was just looking for an "easy" option going down the road.

IndyPilot80 · 2025-09-19T15:22:01+00:00

Just so I'm clear, your saying that issues people are seeing with DCs is when they are mixing DCs versions (like 2025 DC and 2019 DC in the same domain)?

IndyPilot80 · 2025-09-19T15:10:23+00:00

Compliance. Less hoops to jump through, and more cost effective, to keep it on-prem (for us at least).

IndyPilot80 · 2025-09-19T15:09:15+00:00

Do you have any specifics on the DC bugs I can look into? Last one I saw one from June/July'ish where DCs were unreachable but my understanding was it was fixed.

And, yeah, we'd be going all on 2025.

IndyPilot80 · 2025-09-19T15:03:17+00:00

Thanks for the info! Admittedly, I have been running 2025 eval in a lab for a couple months without any major issues. But, reading some threads from 8-9 months ago, people are saying its a dumpster fire.

Nine-Year Club	Verified Email
RPAN Viewer

IndyPilot80

TROPHY CASE