On Fri, Jul 20, 2018 at 10:34:12AM +0200, john doe wrote: > > I have no idea what NM is ... can you provide a path to a configuration > > file? i will reply with it's contents.
Jeez, I go away for a few days and look what happens. NM is "Network Manager", which is one of the optional ways to configure a network interface in Debian. Usually used in conjunction with a Desktop Environment (GNOME, etc.). Usually not used on web servers, but it's allowed. The typical way to learn that NM is in charge of your interfaces is by the comment signature that it leaves at the top of /etc/resolv.conf, which is why you were asked to examine your /etc/resolv.conf file. I also saw something up-thread which showed Network Manager output in the logs of some service or other. Also you don't have your interface defined in /etc/network/interfaces at all, which is another good indicator that you might be using Network Manager. Then again, your /e/n/i/ contains the "source /etc/network/interfaces.d/*" line and you didn't tell us whether you've got your interface configured in there. You PROBABLY don't, but we can't be 100% certain since you didn't bother to look there and find out. So, it's probably NM (Network Manager) which configures your interface. Now, I know absolutely nothing about NM (except that it leaves behind a comment in /etc/resolv.conf), so I can't help you with that part. You need to figure out how to ensure that Apache isn't started until NM has brought up your interface. (Perhaps this machine didn't start out as a web server. Perhaps you installed it as a desktop machine, and then added Apache to it. That would explain why it's got NM.) At some point you also need to figure out the name of your interface. It might be eth0, or it might not. This is basic stuff. If you don't know the name of your interface, start with "ip link". That should show you all of your interfaces, and some of their current settings. Blindly putting "auto eth0" in /e/n/i when "eth0" might not even be the name of your interface is not productive. My original suggestion was to CHANGE the line "allow-hotplug whatever" to "auto whatever", which was written under the assumption that you're using /e/n/i in the first place, rather than NM (a reasonable guess for a web server). If your interface isn't named in /e/n/i AT ALL, then don't touch /e/n/i. You can't change something that's not there. Also, someone mentioned that you might have told Apache to bind to a specific IP address instead of binding to all addresses. Well, that would be pretty silly, now wouldn't it? If you've done that, undo it. Tell Apache to listen/bind on all interfaces, which is the default behavior.
