Search results

if you're working on LAN, why not disable the firewall and try again ? sending a ping used the icmp protocol which has no port number and no state using http to connect to the web interface uses http which gets state from tcp so, with the firewall enabled it is perfectly possible to be able to...

Please read this thread https://forum.proxmox.com/threads/unable-to-connect-to-web-ui-but-ssh-works.159349/ I think it will work for you. I had the same experience with ifreload. If you want to change something in Promox /etc/network/interfaces copy interfaces to interfaces.new, then edit...

Whenever you cannot connect to the Web UI (login failed, please try again) and the logs in /var/log/pveproxy/access.log show HTTP 595 errors on access tickets This is most likely due to failing localhost to localhost communications, try iptables -A INPUT -i lo -s 127.0.0.1 -j ACCEPT iptables...

the VLAN set-up would only be required if the bridge had been made VLAN aware and had VLAN assigned to it it may be the vlan is assigned to the external interface and thus has to 'stretched' onto the bridge

@openminded do you still have a question ? the last post shows leases being offered in response to DHCP discover, so that's fixed?

the solution is to mark the bridge interface on Proxmox as 'vlan aware', then apply this setting

@ggoller after much trial and error I had to give up, then a BIOS update was released, the halts are no longer happening.

Hey, Though it seemed related to the update timers the system was found 'hung' this morning, it failed at 3:10 which is more or less the same time as before. The machine simply stops responding to anything. Keyboard numlock led responds, no console shows anymore, network traffic stops, does...

Running the latest PBS as a stand-alone I've ran into an issue then machine becomes unavailable. Both console and network no longer respond. Sometimes console seems sluggish to respond, then stops. My observation and impression is this is after proxmox-backup-daily-update ran. To that end I...

in case this is still relevant if all you're going to do is run an OPNSENSE FW on that proxmox node the N100 could do for that kind of traffic, if you think minimal IDS/IPS consider OPNSense can run suricata which has considerable performance available, you can tune the ruleset for this CPU...

no need for such an elaborate apology, I'm in year 32 of IT, I've seen way to many forums, communities and newsgroups. I expect/hope stuff would finally just work most of the time. And I'm known to be grumpy. a helpful attitude is obviously admirable also consider the promox webui is just a...

that command was actually a recommended approach by a Proxmox team support member. Due to me growing old and being quite tired I had also rebooted the server instead of restarting it. Multi-tasking only works well when you're young I guess. Time to not do that again. If anything, it shows your...

same as before, don't understand what happened using CLI is my preferred way of working since mosten often this tells me exactly what happened this time however, Proxmox just 'flipped' as I did something incredibly stupid after 'rm -Rf /etc/pve + reboot (not restart)' I'm not sure what made...

If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and...

running a very simple set-up with Proxmox on ZFS I'm looking to have snapshot of everything in /etc and other select directories. Essentially / without rpool and subsequent volumes. Since df -h shows mountpoint to be /root/RPOOL/pve-1 / i tried: zfs snapshot -r rpool/ROOT/pve-1@may2024...

I don't understand what you're asking # pveupdate # pveupgrade

After a mere pveupdate+pveupgrade the standalone Proxmox VE is now broken (again) Things that broke are : a kernel module .conf file (fix= `rm /etc/modprobe.d/e1000e.conf`) the GPU udev rules suddenly contained GROUP== instead of GROUP= (fix: remove = from ==) not 100% sure but the monitor...

thanks, did work for some time but the issue is back and resurfaces after multiple repeats of this sequence

unless you did something not documented here and something I've not tried yet, the issue will resurface my system is a single-node Proxmox set-up, which I think is part of the issue resurfacing

no solutions presented in this thread work and keep working this seems to be an issue which is not addressed as it only seems to happen on non-cluster proxmox ?