Sponsored Content
Top Forums UNIX for Dummies Questions & Answers multiple interfaces with apache? Post 39181 by RTM on Friday 8th of August 2003 01:03:02 PM
Old 08-08-2003
According to the FAQ, Apache listens to all interfaces by default (which, of course, doesn't make sense of why they then put in a Listen directive! - I kept reading - it's more for adding other ports than interfaces/IPs)

Quote:
Reduce the number of Listen directives. If there are no other servers running on the machine on the same port then you normally don't need any Listen directives at all. By default Apache listens to all addresses on port 80.
Listen directive may work - I have no way of testing.

Note what FAQ question 18 states -

Quote:
Why can I access my website from the server or from my local network, but I can't access it from elsewhere on the Internet?
There are many possible reasons for this, and almost all of them are related to the configuration of your network, not the configuration of the Apache HTTP Server. One of the most common problems is that a firewall blocks access to the default HTTP port 80. In particular, many consumer ISPs block access to this port. You can see if this is the case by changing any Port and Listen directives in httpd.conf to use port 8000 and then request your site using http://yourhost.example.com:8000/. (Of course, a very restrictive firewall may block this port as well.)

Last edited by RTM; 08-08-2003 at 02:08 PM..
 

7 More Discussions You Might Find Interesting

1. IP Networking

Multiple Interfaces and Routes

I have a Unix box with 2 network interfaces on the same IP subnet and would like to add a host route via a specific interface. Any assistance would be greatly appreciated. (3 Replies)
Discussion started by: diemos
3 Replies

2. IP Networking

DHCPD, Multiple interfaces, Single Subnet

I have an OpenBSD 3.7 firewall with five network interfaces on it, one of which is connected to the Internet. I'd like to use the remaining four interfaces as a network switch for a single internal subnet. The main problem I have is that the DHCP daemon doesn't like multiple interfaces matching... (0 Replies)
Discussion started by: vertigo23
0 Replies

3. AIX

Multiple LAN Interfaces

Is there a way to add routes using the add route command in AIX to add different routes and bind them to different NICS installed in the box? (2 Replies)
Discussion started by: Docboyeee
2 Replies

4. Solaris

Adding multiple virtual interfaces on a non global zone.

Hello All, I have a requirement to add multiple virtual interfaces on a non-global zone (Solaris 10). The global zone is a 2 node Veritas Cluster Server. So, my question is do we have to make any modifications to the cluster config (which I think should not be the case)? Can anyone help with me... (11 Replies)
Discussion started by: mahive
11 Replies

5. Solaris

Solaris 8: Multiple primary interfaces connected to the same network

Hello, I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway. assume: * e1000g0: 10.1.1.70 * e1000g2: 10.1.1.72 * e1000g4: 10.1.1.74 * e1000g5: 10.1.1.76 * gateway:... (11 Replies)
Discussion started by: aeg
11 Replies

6. AIX

Problem with multiple network interfaces

Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket. Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B. Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies

7. Solaris

Interfaces and Virtual-interfaces queries

Hi Al, In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified. 1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Discussion started by: satish51392111
1 Replies
APACHECTL(8)							     apachectl							      APACHECTL(8)

NAME
apachectl - Apache HTTP Server Control Interface SYNOPSIS
When acting in pass-through mode, apachectl can take all the arguments available for the httpd binary. apachectl [ httpd-argument ] When acting in SysV init mode, apachectl takes simple, one-word commands, defined below. apachectl command SUMMARY
apachectl is a front end to the Apache HyperText Transfer Protocol (HTTP) server. It is designed to help the administrator control the functioning of the Apache httpd daemon. The apachectl script can operate in two modes. First, it can act as a simple front-end to the httpd command that simply sets any necessary environment variables and then invokes httpd, passing through any command line arguments. Second, apachectl can act as a SysV init script, taking simple one-word arguments like start, restart, and stop, and translating them into appropriate signals to httpd. If your Apache installation uses non-standard paths, you will need to edit the apachectl script to set the appropriate paths to the httpd binary. You can also specify any necessary httpd command line arguments. See the comments in the script for details. The apachectl script returns a 0 exit value on success, and >0 if an error occurs. For more details, view the comments in the script. OPTIONS
Only the SysV init-style options are defined here. Other arguments are defined on the httpd manual page. start Loads the org.apache.httpd launchd job. stop, graceful-stop Unloads the org.apache.httpd launchd job. restart, graceful Unloads, then loads the org.apache.httpd launchd job. fullstatus Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text-based browser such as lynx available on your system. The URL used to access the status report can be set by editing the STATUSURL variable in the script. status Displays a brief status report. Similar to the fullstatus option, except that the list of requests currently being served is omit- ted. configtest Run a configuration file syntax test. It parses the configuration files and either reports Syntax Ok or detailed information about the particular syntax error. This is equivalent to apachectl -t. The following option was available in earlier versions but has been removed. startssl To start httpd with SSL support, you should edit your configuration file to include the relevant directives and then use the normal apachectl start. Apache HTTP Server 2005-09-20 APACHECTL(8)
All times are GMT -4. The time now is 04:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy