This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.

Failed to create virtual server : Failed to work out externally visible IP address

3 posts / 0 new

Topic locked

Last post

#1 Tue, 02/12/2013 - 11:39

tootle

Failed to create virtual server : Failed to work out externally visible IP address

That's dev server @my home, behind tp-link router.

I no longer can create sub-servers via Virtualmin, Last month everything was OK, now it throws an error: Failed to create virtual server : Failed to work out externally visible IP address

Last thing I did was Virtualmin update and enable DHCP service running for @home PXE boot purposes.

Can <-->ping world both directions. All websites online. But can't create new ones.

I'm using External IP address Same as real address (192.168.1.11)

Operating system CentOS Linux 5.9 / Webmin version 1.620 / Virtualmin version 3.98.gpl GPL

Thanks in advance 4 any help.

#2 Wed, 02/13/2013 - 03:05

tootle

OK, i managed to find the issue

Virtualmin -> System Settings -> Virtualmin Configuration -> Network Settings changed from : "Network interface for virtual addresses" eth0

to

"Network interface for virtual addresses" Detect automatically

Now the issue is gone. I can create new virtualmin servers.

I have only one IF (eth0) and /etc/sysconfig/network-scripts/ifcfg-eth0 hadn't changed so I have no clue what causes this behaviour anyway.

BUT!:Now I have a yellow virtualmin message "Virtualmin's configuration has not been checked since it was last updated. Click the button below to verify it now." and when I click Recheck it switches "Network interface for virtual addresses" option back to eth0 which spoils the coffee over again.

What helps is an IP entry in -> "Default virtual server IP address" 192.168.1.11 in my case. Previously this option was set to "From network interface".

That's weird because all my /etc/httpd/conf/httpd.conf per vhost entries always got < VirtualHost *:80 > and putting that IP does not have any impact on this.

Anyway. Eveything looks & works fine. Have no idea what cause that mess.

#3 Tue, 12/18/2018 - 09:37 (Reply to #2)

humansoft

Thank you. You have to set it up and restart.

- Old man novice

Topic locked