• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Plesk and Bridged Network

tkalfaoglu

Silver Pleskian
I'd like to install KVM hypervisor on the machine that's running plesk.
That involves creating a bridge, and assigning the ethernet to it. The ethernet itself becomes without an IP, and the br0 picks up the IP address. Likewise, the other IP addresses that are normally assigned to eth0:1 or 2 or 3 etc should presumably be assiged to br0:1 or 2 or 3 etc.

Any ideas how to implement bridging and alias IP addresses without breaking plesk?
Many thanks, -t
 
Last edited:
Probably not. I assume having KVM virtual machines and running Plesk in one or more of them is quite common, but having Plesk on the actual hardware node alongside the VMs isn't common at all.

That being said, there are alternative KVM networking setups that don't require creating a bridge with the server's NIC. A tap network with the help of qemu hooks, perhaps?

I had something like this in production but our hardware nodes were quite minimal and I have no idea what adding something like Plesk would do.
 
Back
Top