![]() # Almost any Apache directive may go into a VirtualHost container. # You may use the command line option '-S' to verify your virtual host # for further details before you try to setup virtual hosts. This is indicated by the asterisks in the directives below. # use only name-based virtual hosts so the server doesn't need to worry about # machine you can setup VirtualHost containers for them. # If you want to maintain multiple domains/hostnames on your The nf (I hope this is the right file, it was not manually edited, does not seem relevant to me): This is how we configured the interfaces (eth0 on the left side, eth1 on the right side, 192.168.100.8 is our Netgear Router): (The network interfaces were configured via a installed Kubuntu-Desktop, I guess the config is nearly empty because of this? Here in the company there is nobody that could administrate a Linux server only via terminal/ssh at the moment, and I know KDE from my private Mint-Installation & Knoppix, so I installed a GUI (first Linux server here, I hope we could solve the problem so we can use more Linux machines in the future!)) # This file describes the network interfaces available on your system Thank you both! :) Here's the reqested information, first the /etc/network/interfaces: I would think the problem it's something very simple (setting of some kind) on the Ubuntu or Apache side, but I don't know where to search now. Perhaps we should not talk about "dmz" any longer, that was the intention of the former admin (I guess) but at last there are two different LANs with different subnets.Īlso, if I login on a local server in the LAN (remote), I can access the webserver from there with both adresses without problems! ("192.168.110.20" = local/eth0, "192.168.100.20" = "DMZ"/eth1) On the router side, we changed simply the IP from the old webserver to the new one for port forwarding (both same port 80 and same subnet ("dmz")). Not only because of the traffic (from outside) is visible while monitoring eth1 ("dmz") which is the way I want it, the same configuration (with the two interfaces and so on) was also used for the former webserver of the company (a "server" based on WinXP. Thanks again for your fast reply! I got your point, but I don't think this is really the reason of this specific problem. It seems that the traffic is lost/dropped between the Ubuntu network stack and the Apache webserver imho. SELinux is not active it seems (Ubuntu default) ![]() ![]() Installed the additional profiles via bash, didn't change anything on that. apparmor is active (Ubuntu default), but no profile for appache present. The Firewall/ufw is (at the moment) deactivated (until public access works) The log files of the Apache does not show anything if you try to access it via public IP The traffic from the other departments server does reach the "public" interface eth1, monitored this via bash (tcpdump) while try to access the webserver via browser! So the router should not be the problem. It can NOT be accessed via Internet (tried not only public IP in the LAN but also remote via a server in a other department of our company, so "really outside the LAN") :( The Apache is listen to "0.0.0.0:80" (should listen on eth0 and eth1 (IPv4)) The Apache can be accessed from other systems in the LAN. We use a Netgear Router/Firewall to access the web. Some details: Ubuntu Server 14.04 LTS (VM on a Windows SRV 2012 R2, Hyper-V), two (virtual) ethernet interfaces, eth0 is local LAN, eth1 is part of a "DMZ" (and connected to the same network as the router/gateway). Some other servers in our Network (Windows Terminalserver) can be accessed from the web. After resolving some minor problems, everything is working now except one thing: The webserver can not be accessed from outside the local network. I've installed Ubuntu Server and the bitnami ruby stack (wich is using Apache 2) for a webserver. I've got a problem with Ubuntu Server and Apache which I could not solve the last days, any help would be much appreciated:
0 Comments
Leave a Reply. |