New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Virtualizor Single IP Issue (Kimsufi Server)
Hi everyone,
I'm facing a frustrating issue with Virtualizor on my OVH Kimsufi dedicated server and hoping someone with experience can offer some guidance.
Here's the situation:
- I have an OVH Kimsufi dedicated server.
- I installed Virtualizor and needed to add an additional IP address.
- Initially, I had issues getting the additional IP working.
- The support team added an "IP pool" with my single additional IP.
- Now, when I create VPSs in Virtualizor, they are completely unreachable. I can't SSH or ping them.
- Before virtualizor installation, this additional ip was working fine on the server with another control pannel.
- The support team claims the issue is with my IP provider (OVH), but I'm skeptical, as the IP was working fine before the Virtualizor configuration.
I'm wondering if anyone has experienced similar issues with Virtualizor and single additional IPs on OVH Kimsufi servers.
Here are my key questions:
- Is it common to have connectivity issues on OVH Kimsufi servers when Virtualizor is configured with a single additional IP?
- Are there any specific Virtualizor network settings that I should be checking for OVH Kimsufi servers?
- Any ideas on how to troubleshoot this issue further, especially when the support team is pointing fingers elsewhere?
- What is the correct way to add a single additional ip to virtualizor on a OVH kimsufi server?
- Could a warning during virtualizor installation regarding a chmod error cause this.
Any advice or insights would be greatly appreciated!
Thanks in advance.
Comments
Have you given the vm in Virtualizor the virtual MAC address from the OVH panel?
Hi,
No, I did not assign a virtual MAC address from the OVH panel to the VMs in Virtualizor.
Virtualizor support stated:
"I checked all configuration of ip pool is correct you need to check once with your IP provider, because additional ip range and server ip range is different"
The additional IP address I'm using is 144.XXX.XXX.XXX, and my main IP is 158.XXX.XXX.XXX.
Interestingly, when I installed Debian 12 with HestiaCP, both IP addresses worked perfectly fine.
Do you think the lack of a virtual MAC address assignment could be the reason for the connectivity issues?
I'm not sure if OVH requires you to bind the extra IP to a MAC, but if they do they'll give you the option on their control panel. You can then bind to the same MAC on Virtualizor (within the IP pool, theres an option to assign a MAC to the IPs), and it should work. Make sure you set the right Gateway and Netmask on the IP Pool too.
You would need to create virtual MAC for your IP: 144.XXX.XXX.XX as wmware in ovh panel, and then when you add to virtualizor tick routed network specify the IP 144.XXX.XXX.XX and the MAC created. Gateway would be: 158.XXX.XXX.254 netmask would be: 255.255.255.255 And then it would work.
Thank you so much! Your suggestion worked perfectly.
Creating the virtual MAC address in the OVH panel and then configuring Virtualizor with the routed network, the specified IP, MAC address, gateway, and netmask as you described solved the connectivity issue.
I really appreciate your help. This was a frustrating problem, and your clear instructions made all the difference.
Thanks again!
Glad you solved the issue.
But virtualizor do have DOC specially for OVH
https://www.virtualizor.com/docs/admin/setup-ovh/
Best of luck