Search results

I should have maybe explained in greater detail what I’m trying to accomplish. I want to allow traffic from everywhere on the internet (have already limited the access to http only using external fw and portforwarding) but I want to start dropping all traffic from an IP once that has fallen...

I've been hitting my head to the brick wall that is iptables inside a Debian 11.3 container in Proxmox. I cannot seem to get it to block anything and there seems to be some contradicting discussions about if iptables should even work inside LXC. I do use Proxmox firewall as well, and it is...

https://10.100.1.2:8006/?console=kvm&novnc=1&vmid=100&vmname=myvmname&node=mynodename I see, that seems simple enough. Now I just have to think of a way to set up the authentication cookie beforehand somehow, as entering that address just seems to yield "Error 401: No ticket". I recon there is...

But security points aside, you see that technically using Proxmox's noVNC would be possible somehow? From an iframe on another site, after getting the login token? My Proxmox and Home Assistant installations are only for fun and games, and both strictly available in my home LAN only...

This is my goal exactly as well, but have not found any simple way so far. I'd like to have a tab (a view) in my Home Assistant dashboard that would have an iframe to Proxmox's noVNC, providing quick access to a VM. I have a user account and API Token for it set up with appropriate permissions...

You suggest a batch script run by the user on their local device before they attempt to connect to the VM? That certainly could work but not as automatic as I’d like: The device they’re connecting from could be Windows, macOS, Android or iOS, all of which would require their own scripts, right...

Has there been any advancements here lately? I’ve been searching for this particular feature as well, due to having a few old Windows XP VMs that seem to take a fair amount of resources even when idling, and they are needed weekly at best so keeping them up 24/7 is just dumb. I was wondering if...

So this was indeed a stupid user issue as I thought, thanks a lot for the tip! Disabling DHCP for IPv6 made the network service start without issues. The sys-kernel-config.mount and systemd-journald-audit.socket do still fail but I suppose that's not critical. At least I have not noticed that...

Some further details of the failing services from within the container: root@debian:~# systemctl UNIT LOAD ACTIVE SUB DESCRIPTION -.mount loaded active mounted Root Mount dev-.lxc-proc.mount...

Hello. New to Proxmox and LXC in general, so this is probably just some stupid user issue but after updating from v6 to v7 I've found that with any container I create, there are strange errors getting their services up. So far tried debian-10-turnkey-zoneminder_16.1-1_amd64 and the default...