View Full Version : why is this happening?
b.trayn
2004-11-04, 18:14 PM
Hi
sorry 4 the vague subject heading. My problem is this. I purchased new domain and pointed the nameservers to ns1.geodns.net & ns2.geodns.net. The problem is, i can only view the page if i go through proxy server. If i go through without it only shows where domain is parked on port 81. Here is the virtualhost directive i have used.
<VirtualHost 69.44.157.156>
ServerAdmin webmaster@boneidleuk.com
DocumentRoot /var/www/html/bi
ServerName boneidleuk.com
ServerAlias www.boneidleuk.com
ErrorLog logs/boneidleuk.com-error_log
CustomLog logs/boneidleuk.com-access_log common
</VirtualHost>
If someone could check it out by going to the site and see what they get. http://www.boneidleuk.com it is a site i am setting upo for my sons music. hope someone can help. Thx
If it only works when you go through a proxy, it sounds like a local configuation error that is causing the problem, not the server. There could be a bad resolver or the ISP is caching incorrect DNS information.
You should check if it is resolving to the correct IP address from your computer.
fastduke
2004-11-05, 01:04 AM
resolves just fine for me like QT says it's probably a local dns problem
b.trayn
2004-11-05, 08:58 AM
thx 4 reply guys. If i enter without proxy here is the message i get:
ERROR
The requested URL could not be retrieved
--------------------------------------------------------------------------------
While trying to retrieve the URL: http://boneidleuk.com:81/
The following error was encountered:
Connection Failed
The system returned:
(61) Connection refused
The remote host or network may be down. Please try the request again.
Your cache administrator is webmaster.
If however i put in the ip address http://69.44.157.156/bi it logs into the boneidle folder.
I do not know why the :81 port is showing up. I wonder if it could be something to do with the company where i purchased the domain? I have changed the nameservers to my sb server. What else can i do? Thx
fastduke
2004-11-05, 10:38 AM
Does your error log shed any light?
b.trayn
2004-11-05, 12:25 PM
Here r the last entries 4 the error_lof file.
[Thu Nov 04 16:33:57 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
[Thu Nov 04 16:35:08 2004] [warn] child process 17221 still did not exit, sending a SIGTERM
[Thu Nov 04 16:35:08 2004] [warn] child process 17223 still did not exit, sending a SIGTERM
[Thu Nov 04 16:35:08 2004] [warn] child process 17224 still did not exit, sending a SIGTERM
[Thu Nov 04 16:35:08 2004] [warn] child process 17226 still did not exit, sending a SIGTERM
[Thu Nov 04 16:35:08 2004] [notice] caught SIGTERM, shutting down
[Thu Nov 04 16:37:54 2004] [notice] Digest: generating secret for digest authentication ...
[Thu Nov 04 16:37:54 2004] [notice] Digest: done
[Thu Nov 04 16:37:55 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
[Thu Nov 04 16:40:12 2004] [warn] child process 17275 still did not exit, sending a SIGTERM
[Thu Nov 04 16:40:12 2004] [warn] child process 17277 still did not exit, sending a SIGTERM
[Thu Nov 04 16:40:12 2004] [warn] child process 17278 still did not exit, sending a SIGTERM
[Thu Nov 04 16:40:12 2004] [warn] child process 17280 still did not exit, sending a SIGTERM
[Thu Nov 04 16:40:13 2004] [notice] caught SIGTERM, shutting down
[Thu Nov 04 16:40:21 2004] [notice] Digest: generating secret for digest authentication ...
[Thu Nov 04 16:40:21 2004] [notice] Digest: done
[Thu Nov 04 16:40:22 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
[Thu Nov 04 16:43:31 2004] [warn] child process 17309 still did not exit, sending a SIGTERM
[Thu Nov 04 16:43:31 2004] [warn] child process 17311 still did not exit, sending a SIGTERM
[Thu Nov 04 16:43:31 2004] [warn] child process 17312 still did not exit, sending a SIGTERM
[Thu Nov 04 16:43:31 2004] [warn] child process 17314 still did not exit, sending a SIGTERM
[Thu Nov 04 16:43:31 2004] [notice] caught SIGTERM, shutting down
[Thu Nov 04 16:43:38 2004] [notice] Digest: generating secret for digest authentication ...
[Thu Nov 04 16:43:38 2004] [notice] Digest: done
[Thu Nov 04 16:43:39 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
[Thu Nov 04 16:45:48 2004] [warn] child process 17339 still did not exit, sending a SIGTERM
[Thu Nov 04 16:45:48 2004] [warn] child process 17341 still did not exit, sending a SIGTERM
[Thu Nov 04 16:45:48 2004] [warn] child process 17342 still did not exit, sending a SIGTERM
[Thu Nov 04 16:45:48 2004] [warn] child process 17344 still did not exit, sending a SIGTERM
[Thu Nov 04 16:45:48 2004] [warn] child process 17345 still did not exit, sending a SIGTERM
[Thu Nov 04 16:45:48 2004] [notice] caught SIGTERM, shutting down
[Thu Nov 04 16:45:55 2004] [notice] Digest: generating secret for digest authentication ...
[Thu Nov 04 16:45:55 2004] [notice] Digest: done
[Thu Nov 04 16:45:56 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
[Fri Nov 05 04:02:13 2004] [notice] SIGHUP received. Attempting to restart
[Fri Nov 05 04:02:13 2004] [notice] Digest: generating secret for digest authentication ...
[Fri Nov 05 04:02:13 2004] [notice] Digest: done
[Fri Nov 05 04:02:14 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured -- resuming normal operations
No obvious errors.
Tino Didriksen
2004-11-05, 13:16 PM
http://boneidleuk.com/ works.
http://boneidleuk.com:81/ does not.
1) Your vhost does not specify what port you want that vhost to be valid for, and as such it will be valid for the default port (80).
2) Is Apache even listening on port 81?
3) Does the firewall allow incoming traffic on port 81?
...or is the whole point that you don't want it to use port 81, but it does anyways? I don't see anything that redirects to port 81.
vBulletin® v3.6.8, Copyright ©2000-2008, Jelsoft Enterprises Ltd.