?
Solved

Webpage Error: Website Declined to Show Page

Posted on 2011-10-12
9
Medium Priority
?
979 Views
Last Modified: 2012-05-12
I had a client install the files needed for an internal web mapping application using Apache, MapServer and GeoMoose.  They installed the files onto a Windows Server 2003 machine.  When they tried to access the internal website by using the following address: http://server_name/app_name/index.html they received the following error message "Website Declined to Show Page".

The server is also running IIS and Exchange.

What can I do to grant them access to the internal website?

Unfortunately I don't have any access to this server. I will be going through a third party IT service, so it may take awhile to get answers to you questions.
0
Comment
Question by:GreyHippo
  • 5
  • 4
9 Comments
 

Author Comment

by:GreyHippo
ID: 36958561
The client is able to get to the default Apache web page by going to http://servername.
0
 
LVL 8

Expert Comment

by:H
ID: 36958598
Are they trying to access the website locally on the server or remotely from a different machine?

Its possible inbound to port 80 is blocked...
0
 

Author Comment

by:GreyHippo
ID: 36958687
They have tried both.  If port 80 is blocked why would I be able to access http://localhost.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 8

Expert Comment

by:H
ID: 36958704
Well http://localhost.only works on the local machine...Inbound to port 80 may be blocked by the ISP for remote.
0
 

Author Comment

by:GreyHippo
ID: 36958815
http://server_name will bring a default webpage on both the client and server.  The ISP won't be involved because they will only be accessing the website internally on their LAN.
0
 
LVL 8

Expert Comment

by:H
ID: 36958924
Can you attach the output of a    netstat -n   command

Also can you attach Apache error.log if there is one and httpd.conf   files?
0
 

Author Comment

by:GreyHippo
ID: 36963626
Below is the result of netstat -n, followed by the error log.

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:80           127.0.0.1:1736         FIN_WAIT_2
  TCP    127.0.0.1:80           127.0.0.1:1737         FIN_WAIT_2
  TCP    127.0.0.1:389          127.0.0.1:1037         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1061         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1091         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1129         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1135         ESTABLISHED
  TCP    127.0.0.1:389          127.0.0.1:1145         ESTABLISHED
  TCP    127.0.0.1:1037         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1061         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1091         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1129         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1135         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1145         127.0.0.1:389          ESTABLISHED
  TCP    127.0.0.1:1736         127.0.0.1:80           CLOSE_WAIT
  TCP    127.0.0.1:1737         127.0.0.1:80           CLOSE_WAIT
  TCP    192.168.0.2:135        192.168.0.2:1724       ESTABLISHED
  TCP    192.168.0.2:139        192.168.0.100:1032     ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1050       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1075       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1096       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1097       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1098       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1101       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1102       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1104       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1105       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1106       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1107       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1108       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1131       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1132       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1141       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1147       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1152       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1213       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1567       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1681       ESTABLISHED
  TCP    192.168.0.2:389        192.168.0.2:1682       ESTABLISHED
  TCP    192.168.0.2:691        192.168.0.2:1210       ESTABLISHED
  TCP    192.168.0.2:691        192.168.0.2:1215       ESTABLISHED
  TCP    192.168.0.2:691        192.168.0.2:1216       ESTABLISHED
  TCP    192.168.0.2:691        192.168.0.2:1217       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1052       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1176       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1208       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1298       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1595       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1718       ESTABLISHED
  TCP    192.168.0.2:1026       192.168.0.2:1725       ESTABLISHED
  TCP    192.168.0.2:1050       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1052       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1072       192.168.0.2:3268       ESTABLISHED
  TCP    192.168.0.2:1073       192.168.0.2:1189       ESTABLISHED
  TCP    192.168.0.2:1075       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1093       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1096       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1097       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1098       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1101       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1102       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1104       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1105       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1106       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1107       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1108       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1110       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1111       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1113       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1114       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1115       192.168.0.2:3268       CLOSE_WAIT
  TCP    192.168.0.2:1116       192.168.0.2:3268       CLOSE_WAIT
  TCP    192.168.0.2:1128       192.168.0.2:3268       ESTABLISHED
  TCP    192.168.0.2:1130       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1131       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1132       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1140       192.168.0.2:3268       ESTABLISHED
  TCP    192.168.0.2:1141       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1142       192.168.0.2:1188       ESTABLISHED
  TCP    192.168.0.2:1146       192.168.0.2:3268       ESTABLISHED
  TCP    192.168.0.2:1147       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1152       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1176       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1188       192.168.0.2:1142       ESTABLISHED
  TCP    192.168.0.2:1189       192.168.0.2:1073       ESTABLISHED
  TCP    192.168.0.2:1208       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1210       192.168.0.2:691        ESTABLISHED
  TCP    192.168.0.2:1213       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1215       192.168.0.2:691        ESTABLISHED
  TCP    192.168.0.2:1216       192.168.0.2:691        ESTABLISHED
  TCP    192.168.0.2:1217       192.168.0.2:691        ESTABLISHED
  TCP    192.168.0.2:1261       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1298       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1567       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1595       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1603       192.168.0.2:389        CLOSE_WAIT
  TCP    192.168.0.2:1681       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1682       192.168.0.2:389        ESTABLISHED
  TCP    192.168.0.2:1718       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1724       192.168.0.2:135        ESTABLISHED
  TCP    192.168.0.2:1725       192.168.0.2:1026       ESTABLISHED
  TCP    192.168.0.2:1730       192.168.0.2:135        TIME_WAIT
  TCP    192.168.0.2:1731       192.168.0.2:135        TIME_WAIT
  TCP    192.168.0.2:1732       192.168.0.2:135        TIME_WAIT
  TCP    192.168.0.2:1733       192.168.0.2:1026       TIME_WAIT
  TCP    192.168.0.2:3268       192.168.0.2:1072       ESTABLISHED
  TCP    192.168.0.2:3268       192.168.0.2:1128       ESTABLISHED
  TCP    192.168.0.2:3268       192.168.0.2:1140       ESTABLISHED
  TCP    192.168.0.2:3268       192.168.0.2:1146       ESTABLISHED
  TCP    192.168.0.2:3389       24.3.176.106:13232     ESTABLISHED

Open in new window





u Oct 13 09:16:48 2011] [error] [client 127.0.0.1] client denied by server configuration: D:/ms4w/apps/ftmagisapp_v2/htdocs, referer: http://127.0.0.1/
[Thu Oct 13 09:20:17 2011] [error] [client 127.0.0.1] client denied by server configuration: D:/ms4w/apps/ftmagisapp_v2/htdocs
[Thu Oct 13 11:25:30 2011] [warn] pid file D:/ms4w/Apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Thu Oct 13 11:25:30 2011] [notice] Apache/2.2.17 (Win32) configured -- resuming normal operations
[Thu Oct 13 11:25:30 2011] [notice] Server built: Oct 18 2010 01:58:12
[Thu Oct 13 11:25:30 2011] [notice] Parent: Created child process 1940
[Thu Oct 13 11:25:30 2011] [notice] Child 1940: Child process is running
[Thu Oct 13 11:25:30 2011] [notice] Child 1940: Acquired the start mutex.
[Thu Oct 13 11:25:30 2011] [notice] Child 1940: Starting 64 worker threads.
[Thu Oct 13 11:25:30 2011] [notice] Child 1940: Starting thread to listen on port 80.
[Thu Oct 13 12:51:09 2011] [error] [client 127.0.0.1] client denied by server configuration: D:/ms4w/apps/ftmagisapp_v2/htdocs, referer: http://127.0.0.1/

Open in new window

0
 
LVL 8

Accepted Solution

by:
H earned 2000 total points
ID: 36963745
What about the httpd.conf file?  Those errors in your log above are usually easily fixed in you httpd.conf  file...

especially look for the </directory> tags in the file..

you can also try adding this to the  httpd.conf file

<directory /ms4w/apps/ftmagisapp_v2/htdocs>
allow from all
</directory>

0
 

Author Closing Comment

by:GreyHippo
ID: 36964134
Thanks Hollecar.

That was it, somehow that file got copied to the wrong directory.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Over the last year I have answered a couple of basic URL rewriting questions several times so I thought I might as well have a stab at: explaining the basics, providing a few useful links and consolidating some of the most common queries into a sing…
In Solr 4.0 it is possible to atomically (or partially) update individual fields in a document. This article will show the operations possible for atomic updating as well as setting up your Solr instance to be able to perform the actions. One major …
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question