URGENT ISSUE TO BE FIXED: Can't create new virtual server after upgrading Webmin from 1900 to 1910

16 posts / 0 new
Last post
#1 Fri, 05/10/2019 - 12:09
step's picture

URGENT ISSUE TO BE FIXED: Can't create new virtual server after upgrading Webmin from 1900 to 1910

I have a serious issue with some Virtualmin installation that today stopped to create virtual server after upgrading Webmin from 1900 to 1910. The issue seems to be related to the fact that the IPv4 address is no more recognized from the Webmin networking manager and than from the Virtualmin virtual server creation process.

Trying to create a new VIrtual Server in the usual way I now get this error: "Failed to create virtual server : New virtual server has no IP address! Perhaps Virtualmin could not work out the system's default IP."

This happens because the configured IPv4 seems to be no more catched by the Virtual Server creation process: going to the "Create Virtual Server" page and than in the "IP address and forwarding" tab, the option "Network interface" -> "Shared, on IP" is cheched as usual, BUT the machine IPv4 is no more listed near it!!

The same option in the "IPv6 network interface" still regularly shows the IPv6 address.

Going to the WEBMIN -> NETWORKING -> NETWORK CONFIGURATION, the NETWORK INTERFACES page says that the network interface I'm using has a 'No address configured' inside the IPv4 Address column, but I can connect to webmin using the IPv4, so I presume that the issue it related to a wrong way Webmin is now using to pass the IPv4 address information to the Create Virtual Server process

Is there a way to fix this issue?

Thank you in advance for any hint

(virtualmin in installed on a CentOS Linux 7.6.1810 virtual machin, on ESXi v 6.5, and all was working normally before upgarding webmin....)

Thu, 05/16/2019 - 11:24

Same problem here. Suddenly we can't create virtualhosts. Any help here?

Thu, 05/16/2019 - 11:39

Essentially we just hardcoded the internal IP into the Default virtual server IPv4 address section and that seems to have gotten us by. It's minor but concerning that the IP is not being picked up from the interface. We are also using CentOS 7 on and ESXi v6.5 setup so perhaps that is a hint into the issue and why the forum is not loaded with similar reports.

Thu, 05/16/2019 - 15:00


There does indeed appear to be a bug that affects some people regarding this, due to changes in the output of some networking commands.

Jamie is working out the final details for an updated patch, but a temporary workaround would be to go into System Settings -> Virtualmin Config -> Network Settings, and to explicitly set "Default virtual server IPv4 address" to the correct default IP address, rather than having it automatically detect one.

The current patch Jamie is working on is here:


Sun, 06/23/2019 - 04:32
step's picture

I finally get few time to test the suggested patch, but after applying it I can't still get the new server creation working on my machines... I still get the error message "Failed to create virtual server : New virtual server has no IP address! Perhaps Virtualmin could not work out the system's default IP", nothing seems to be changed. I'm getting this both on ESXi and VirtuaBox hosted machines. Any hint??? Regards

Mon, 07/29/2019 - 10:11

Hi! Also, Virtualmin validation fails, as it states that:

Virtualmin could not work out the default IPv4 address for virtual servers on your system. You will need to update either the <b>Network interface for virtual addresses</b> or <b>Default virtual server IP address</b> fields on the <a href='../config.cgi?virtual-server'>module configuration</a> page.Configuration errors found

Webmin version here is 1.921, CentOS 7.6.1810, Kernel 3.10.0-957.21.3, QEMU virtualized host.

Mon, 07/29/2019 - 22:01

same issue after upgrade to 1.921

virtualmin in installed on a CentOS Linux 7.6.1810

Wed, 07/31/2019 - 17:46

same issue here

CentOS Linux 7.6.1810

Upgraded to 1.921

Thu, 08/01/2019 - 21:15

I have this issue too after updating. If it helps, when I recheck the configuration I get:

Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add to the , or turn off the BIND feature on the page.


Fri, 08/02/2019 - 03:11

Do you have "Either add to the list of DNS servers," in resolv.conf.

If not do that first to try.

if after reboot the resolv.conf is overwritten then you can protect this files with chattr +i resolv.conf command

if reallly using DHCP, then i don't know.

Fri, 08/02/2019 - 17:16

After update, I have the same problem. Edited the resolv.conf Added to the list of nameservers

Tried new Virtual Server Creation Received this error: "Failed to create virtual server : New virtual server has no IP address! Perhaps Virtualmin could not work out the system's default IP."

Running: CentOS 7.6.1810 Webmin: 1.921 Virtualmin: 6.07 Usermin: 1.771 Authentic theme 19.38

I tried the immutable setting and rebooted. Reboot yielded the nameserver still in the immutable resolve.conf file. Tried Virtual Server Creation Same problem same error message.

Have tried to hard code the IP in the "IP address and forwarding" drop down menu to no luck.

This problem seems to be still a problem as of the composition of this email.

Mon, 08/05/2019 - 15:45

After hard setting it under system settings, and rebooting it seems to work,.

Wed, 08/07/2019 - 15:29

Can you elaborate on what you did under "system settings" to make it work.

Did you have BIND running?

Did you alter the resolve.conf file and and set immutable?

Everything I try keeps failing.

For example sake: my WAN ip would be xxx.xxx.xxx.xxx and my LAN IP for server would be yyy.yyy.yyy.yyy

currently network settings are "default virtual server IPv4 address" is "from network interface" did you enter yyy.yyy.yyy.yyy here and select the IP address?

I am just wondering exactly how you hard coded the information in and step by step what you did to make it work.

Wed, 08/07/2019 - 15:43

1) Open Virtualmin 2) Select System Settings 3) Virtualmin Configuration 4) Select the section Network Settings 5) Turn Off Detect Automatically ... Your Network interface name for virtual addresses should populate 6) Next row down - Default virtual server IPv4 address... turn off From Network Interface ... Select the next box ... Put in your IP address for your shared virtual domains

This is what worked for me ... your mileage may vary

Wed, 08/07/2019 - 16:22

rthomas - thank you I guess I was just being dense because I had been fighting this problem off and on everyday since it broke with the upgrade. I could not see the forest because of the trees. I did as you outlined and my sandbox came back and worked as it should. I then applied the same to the production servers and they are good to go. Thank you for taking the time to send your post.

My mileage seems to be going good.

Sat, 11/09/2019 - 01:26
wolflarsen11's picture

Thankful such an awesome sum for sharing this glorious information! I am envisioning see more posts by you. paper writer

Topic locked