Good thought, will have to test this. Maybe putting a small unmanaged switch on the VM network port and plugging both NUC and laptop into the switch would be easiest? If the container’s web interface is reachable in this scenario, then I know it’s likely a pfSense firewall rule causing the problem.
Discussion
you can do
netstat -tulpen
on the VM after SSHing in to check if your web app is actually listening on the right interface and port.
Thanks, I’ll try that.
No luck adding in a switch and putting the VM machine and my laptop on the same physical subnet. Could still ping and ssh into the Proxmox container but no web interface was reachable.
Really seems like a service issue. Have you checked the logs for Umbrel & Start9?
Are you running these bare on the VM, or using docker containers?
Ensure they're not using the same ports.
Also, ensure you try HTTP & HTTPS.
On Start9 as an example, you need to access http first where it'll give you a signed cert and a root cert to add to your local machine before accessing it over HTTPS.
I'm not using any of the tested software as containers within the VM. I've been installing ubuntu 22.04 as a Proxmox container and doing the one line bash install command for runtipi/umbrel. Start9 is its own OS so that was installed on a Proxmox VM using their ISO.
I've tried both http & https on every attempt. But have not checked logs yet. I can see that for the docker based ones, running
Next I am going to try reinstalling Proxmox and set it to be on the Admin network to see if that changes the results. From what I remember, this is easier than trying to change the gateway on an already installed Proxmox system.
Proxmox should really be zone-agnostic here, so you're able to create VMs across multiple zones as needed, I don't think that's the issue.
You can use Proxmox's Network Tab to setup the 3 zones by either creating 3 separate interfaces and hooking them to each VM/LXC, or bridging the zones across a single one.
As for the applications, just check the logs for each service and it should tell you what's wrong.
Within the respective container, run telnet localhost [Port Number] - If it can't connect, then no web server is running and that's the problem. If you get an "empty" response, then it connected successfully. This can also be done as long as you're within the same network and firewall policies are properly configured. Umbrel gives you SSH access to its system, so may be easier to start there.