Submitted by Adam on Sat, 04/20/2013 - 18:54
As per the title, after carrying out an internal IP update (after stopping an Amazon instance), the old IP is left in apache2.conf as per below, causing a 'NameVirtualHost OLD.IP.ADDRESS:80 has no VirtualHosts' error on Apache start up.
NameVirtualHost OLD.IP.ADDRESS:80 NameVirtualHost NEW.IP.ADDRESS:80
Removing the old IP line stopped the error.
Status:
Active
Comments
Submitted by JamieCameron on Sat, 04/20/2013 - 20:55 Comment #1
Yes, Virtualmin currently doesn't clean up those lines. However, the warning about an un-used IP is harmless - it shouldn't effect the behavior of Apache in any way.