EasyPHP Problem

belial · Jun 26, 2006

I've installed EasyPHP on 2 computers and the effect is the same ... I can't get it. I see my page on localhost and in LAN but not outside to the internet, and it's not a modem problem, I've been reading the configs and I don't see anything wrong with it.
Some help please? =x

Houdini · Jun 26, 2006

This is because it works with localhost and you are not on the internet with it. You need to register a domain and many other things. EasyPHP is for local se not internet. You need to pay somewhere along the line for that, or find someone to host a DNS for your site, so it is above an beyond the question you raised here to have much more than an intra net connection.

thorpe · Jun 26, 2006

You might be interested in http://www.dyndns.com.

belial · Jun 26, 2006

ok .. I didn't expressed well .. I have dyndsn [http://belialy.kicks-ass.net by the way] ...

But is DOESN't access by the dyndns .. my external IP or ANYTHING ... it does to 127.0.0.1 on localhost and on my LAN IP too .. but not outside to the internet.

What I posted on their forum and I didn't got an answer:

"

The problem is this. I instaled EasyPHP and on default it is "Listen 127.0.0.1" meaning only localhost can see the page. I put a "#" which means I have put it on comment.
NOW, now I can access the site on my LAN computers but NOT from the internet. I've read the FAQ, all the config files I found and nothing, I need this working urgently, I've looked everything up, did I let pass any thing that could be provoking this?

I've opened the firewall, configurated the router over and over again, I even tryed to find if there was any WinXP services that would be needed. WHAT am I missing here?

Please, I need to solve this ASAP.

Belial

"

I need to resolve this sh*t!!

thorpe · Jun 27, 2006

Could be any number of things, what can I say.... myserver works here, but I cant go through every step of the process.

Did you setup the dyndns client on your machine?
Is your firewall blocking the dyndns client?
Are you sure your router is forwarding port 80 to the server?
Are you positive your firewall isn't blocking access?

belial · Jun 27, 2006

thorpe wrote:
Could be any number of things, what can I say.... myserver works here, but I cant go through every step of the process.

Did you setup the dyndns client on your machine?
Is your firewall blocking the dyndns client?
Are you sure your router is forwarding port 80 to the server?
Are you positive your firewall isn't blocking access?

"Did you setup the dyndns client on your machine?" Yes, on my server and on the modem. [On the server isn't needed but I have it anyway]

"Is your firewall blocking the dyndns client?" NO

"Are you sure your router is forwarding port 80 to the server?" Yes .. 80 .. 8080 .. I even put my server as the modem's DMZ host [everything is forward to the server if the modem doesn't know where to send the packets]

"Are you positive your firewall isn't blocking access?" I'm sure, when I turn my "Home Web Server" on it works great, but EasyPHP doesn't.

I'm pretty sure it has to be a config of it. Want me to put the config file here? or .. could you send me a config file configured and working already?

Thank you in advance

thorpe · Jun 27, 2006

Want me to put the config file here?

I assume by that you meen the apache config file httpd.conf?

Yeah post it if you like.

belial · Jun 27, 2006

httpd.conf

I had this line on the file:

Listen 127.0.0.1:80

When I changed it to:

#Listen 127.0.0.1:80

I could access the site not only from the localhost [127.0.0.1] but from 10.0.0.25 too [my network IP], which I couldn't before.

.....

But when I asked to ppl to access the site, they always got "Timeout".

BindAddress: You can support virtual hosts with this option. This directive

is used to tell the server which IP address to listen to. It can either

contain "*", an IP address, or a fully qualified Internet domain name.

IMPORTANT

${path} is used to specify EasyPHP installation path

#

Based upon the NCSA server configuration files originally by Rob McCool.

#

This is the main Apache server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:http://www.apache.org/docs/> for detailed information about

the directives.

#

Do NOT simply read the instructions in here without understanding

what they do. They're here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

#

After this file is processed, the server will look for and process

srm.conf and then access.conf

unless you have overridden these with ResourceConfig and/or

AccessConfig directives here.

#

The configuration directives are grouped into three basic sections:

1. Directives that control the operation of the Apache server process as a

whole (the 'global environment').

2. Directives that define the parameters of the 'main' or 'default' server,

which responds to requests that aren't handled by a virtual host.

These directives also provide default values for the settings

of all virtual hosts.

3. Settings for virtual hosts, which allow Web requests to be sent to

different IP addresses or hostnames and have them handled by the

same Apache server process.

#

Configuration and logfile names: If the filenames you specify for many

of the server's control files begin with "/" (or "drive:/" for Win32), the

server will use that explicit path. If the filenames do not begin

with "/", the value of ServerRoot is prepended -- so "logs/foo.log"

with ServerRoot set to "/usr/local/apache" will be interpreted by the

server as "/usr/local/apache/logs/foo.log".

#

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default. It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

#

Section 1: Global Environment

#

The directives in this section affect the overall operation of Apache,

such as the number of concurrent requests it can handle or where it

can find its configuration files.

#

ServerType is either inetd, or standalone. Inetd mode is only supported on

Unix platforms.

#
ServerType standalone

#

ServerRoot: The top of the directory tree under which the server's

configuration, error, and log files are kept.

#
ServerRoot "${path}/apache"

#

PidFile: The file in which the server should record its process

identification number when it starts.

#
PidFile logs/httpd.pid

#

ScoreBoardFile: File used to store internal server process information.

Not all architectures require this. But if yours does (you'll know because

this file will be created when you run Apache) then you must ensure that

no two invocations of Apache share the same scoreboard file.

#
ScoreBoardFile logs/apache_runtime_status

#

In the standard configuration, the server will process httpd.conf (this

file, specified by the -f command line option), srm.conf, and access.conf

in that order. The latter two files are now distributed empty, as it is

recommended that all directives be kept in a single file for simplicity.

The commented-out values below are the built-in defaults. You can have the

server ignore these files altogether by using "/dev/null" (for Unix) or

"nul" (for Win32) for the arguments to the directives.

#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#

Timeout: The number of seconds before receives and sends time out.

#
Timeout 300

#

KeepAlive: Whether or not to allow persistent connections (more than

one request per connection). Set to "Off" to deactivate.

#
KeepAlive On

#

MaxKeepAliveRequests: The maximum number of requests to allow

during a persistent connection. Set to 0 to allow an unlimited amount.

We recommend you leave this number high, for maximum performance.

#
MaxKeepAliveRequests 0

#

KeepAliveTimeout: Number of seconds to wait for the next request from the

same client on the same connection.

#
KeepAliveTimeout 30

#

Apache on Win32 always creates one child process to handle requests. If it

dies, another child process is created automatically. Within the child

process multiple threads handle incoming requests. The next two

directives control the behaviour of the threads and processes.

#

MaxRequestsPerChild: the number of requests each child process is

allowed to process before the child dies. The child will exit so

as to avoid problems after prolonged use when Apache (and maybe the

libraries it uses) leak memory or other resources. On most systems, this

isn't really needed, but a few (such as Solaris) do have notable leaks

in the libraries. For Win32, set this value to zero (unlimited)

unless advised otherwise.

#

NOTE: This value does not include keepalive requests after the initial

request per connection. For example, if a child process handles

an initial request and 10 subsequent "keptalive" requests, it

would only count as 1 request towards this limit.

#
MaxRequestsPerChild 0

#

Number of concurrent threads (i.e., requests) the server will allow.

Set this value according to the responsiveness of the server (more

requests active at once means they're all handled more slowly) and

the amount of system resources you'll allow the server to consume.

#
ThreadsPerChild 50

#

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, in addition to the default. See also the <VirtualHost>

directive.

#
#Listen 3000
#Listen 12.34.56.78:80
#Listen 127.0.0.1:80

#

BindAddress: You can support virtual hosts with this option. This directive

is used to tell the server which IP address to listen to. It can either

contain "*", an IP address, or a fully qualified Internet domain name.

Dynamic Shared Object (DSO) Support

#

To be able to use the functionality of a module which was built as a DSO you

have to place corresponding `LoadModule' lines at this location so the

directives contained in it are actually available before they are used.

Please read the file README.DSO in the Apache 1.3 distribution for more

details about the DSO mechanism and run `apache -l' for the list of already

built-in (statically linked and thus always available) modules in your Apache

binary.

#

Note: The order in which modules are loaded is important. Don't change

the order below without expert advice.

#

Example:

LoadModule foo_module modules/mod_foo.so

#
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule status_module modules/mod_status.so
#LoadModule info_module modules/mod_info.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule anon_auth_module modules/mod_auth_anon.so
#LoadModule dbm_auth_module modules/mod_auth_dbm.so
#LoadModule digest_auth_module modules/mod_auth_digest.so
#LoadModule digest_module modules/mod_digest.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so

LoadModule php4_module "${path}/php/php4apache.dll"

----- imcomplete ----

thorpe · Jun 27, 2006

Im working on my firewall at the moment so cant reach my server to retrieve my httpd.conf file. wouldn't be much use anyway I should imagine, I have a completely different setup with my httpd.conf file spread accross numerous files for different vhosts.

Your configuration seems fine to me, Im sure this is probably more a network issue. You might try changing your Listen to a wildcard..

Listen *:80

But I dont think that is the issue. I cant even ping the address you gave so its not just the Apache that isn't listening, we cant find you.

BindAddress: You can support virtual hosts with this option. This directive

is used to tell the server which IP address to listen to. It can either

contain "*", an IP address, or a fully qualified Internet domain name.

See also the <VirtualHost> and Listen directives.

IMPORTANT

${path} is used to specify EasyPHP installation path

Based upon the NCSA server configuration files originally by Rob McCool.

This is the main Apache server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:http://www.apache.org/docs/> for detailed information about

the directives.

Do NOT simply read the instructions in here without understanding

what they do. They're here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

After this file is processed, the server will look for and process

srm.conf and then access.conf

unless you have overridden these with ResourceConfig and/or

AccessConfig directives here.

The configuration directives are grouped into three basic sections:

1. Directives that control the operation of the Apache server process as a

whole (the 'global environment').

2. Directives that define the parameters of the 'main' or 'default' server,

which responds to requests that aren't handled by a virtual host.

These directives also provide default values for the settings

of all virtual hosts.

3. Settings for virtual hosts, which allow Web requests to be sent to

different IP addresses or hostnames and have them handled by the

same Apache server process.

Configuration and logfile names: If the filenames you specify for many

of the server's control files begin with "/" (or "drive:/" for Win32), the

server will use that explicit path. If the filenames do not begin

with "/", the value of ServerRoot is prepended -- so "logs/foo.log"

with ServerRoot set to "/usr/local/apache" will be interpreted by the

server as "/usr/local/apache/logs/foo.log".

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default. It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

Section 1: Global Environment

The directives in this section affect the overall operation of Apache,

such as the number of concurrent requests it can handle or where it

can find its configuration files.

ServerType is either inetd, or standalone. Inetd mode is only supported on

Unix platforms.

ServerRoot: The top of the directory tree under which the server's

configuration, error, and log files are kept.

PidFile: The file in which the server should record its process

identification number when it starts.

ScoreBoardFile: File used to store internal server process information.

Not all architectures require this. But if yours does (you'll know because

this file will be created when you run Apache) then you must ensure that

no two invocations of Apache share the same scoreboard file.

In the standard configuration, the server will process httpd.conf (this

file, specified by the -f command line option), srm.conf, and access.conf

in that order. The latter two files are now distributed empty, as it is

recommended that all directives be kept in a single file for simplicity.

The commented-out values below are the built-in defaults. You can have the

server ignore these files altogether by using "/dev/null" (for Unix) or

"nul" (for Win32) for the arguments to the directives.

Timeout: The number of seconds before receives and sends time out.

KeepAlive: Whether or not to allow persistent connections (more than

one request per connection). Set to "Off" to deactivate.

MaxKeepAliveRequests: The maximum number of requests to allow

during a persistent connection. Set to 0 to allow an unlimited amount.

We recommend you leave this number high, for maximum performance.

KeepAliveTimeout: Number of seconds to wait for the next request from the

same client on the same connection.

Apache on Win32 always creates one child process to handle requests. If it

dies, another child process is created automatically. Within the child

process multiple threads handle incoming requests. The next two

directives control the behaviour of the threads and processes.

MaxRequestsPerChild: the number of requests each child process is

allowed to process before the child dies. The child will exit so

as to avoid problems after prolonged use when Apache (and maybe the

libraries it uses) leak memory or other resources. On most systems, this

isn't really needed, but a few (such as Solaris) do have notable leaks

in the libraries. For Win32, set this value to zero (unlimited)

unless advised otherwise.