Ok thank you all for putting up with me, this was my own dumb dumb fault. I relized it this morning when I added another virtual host. I needed to define the SSL virtual host <VirtualHost 192.168.1.100> as well as the _default_.
Andre Andre Cameron wrote:
rbragg wrote:
Check all your logs and try to find out more info that way.
What exacly is the error? also triple check firewall rules.
should be in /var/log/messages, /var/log/httpd/error_log, ssl_error_log,... ssl_access_log...
Rick
I did find this in the virtual host log,
[Mon Oct 06 08:40:55 2003] [error] [client 192.168.1.100] Invalid method in request !|!!!
[Mon Oct 06 08:40:55 2003] [error] [client 192.168.1.100] Invalid method in request !|!!
[Mon Oct 06 08:41:04 2003] [error] [client 192.168.1.100] Invalid method in request !|!!!
[Mon Oct 06 08:41:04 2003] [error] [client 192.168.1.100] Invalid method in request !|!!
[Mon Oct 06 08:42:53 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:43:28 2003] [error] [client 63.76.208.239] Invalid method in request !g!!!
[Mon Oct 06 08:43:28 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:43:34 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:44:57 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:47:44 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:47:50 2003] [error] [client 63.76.208.239] Invalid method in request !g!!
[Mon Oct 06 08:50:15 2003] [error] [client 63.76.208.239] Invalid method in request get
[Mon Oct 06 08:57:05 2003] [error] [client 63.76.208.239] Invalid method in request !L!!
[Mon Oct 06 08:57:20 2003] [error] [client 63.76.208.239] Invalid method in request !L!!
Looks like all my https requests from work to the server and the local lynx call for the private.... Strange. Think this is a problem with Apache?
Andre Cameron wrote:
Andre Cameron wrote:
rbragg wrote:
I think it is a DNS or a local hosts file issue.
Rick
Could be DNS, the domain resolves to the public IP, not the private one. Soooo should I put bind on the box and run an internal DNS server as well as the external one or is there a way arround it?
Ok so it is NOT DNS, Just setup bind, setup zones, restarted services did a dig to confirm proper configuration and still does not allow connections from off the box. Any other ideas?
Andre
Andre Cameron wrote:
I am at a loss here, from the server through lynx I can do:
https://localhost https://127.0.0.1
from lynx I can NOT do https://192.168.1.100, from my other PC I can not do https://192.168.1.100 but I CAN do http://192.168.1.100.
I never installed the Linux firewall because I use the router, which is not part of the problem here because I am using all private IPS insidde the LAN.
So just for the fun of it I telneted from 192.168.1.101 to 192.168.1.100 on port 443, I connected. So its not getting blocked, it is working locally, and I have no freaking idea where else to look.
Andre
Andre Cameron wrote:
Hello,
Sorry but I am new to Apache 2.x and need to get SSL installed and working, the RH binaries used to have Apache preconfigured with SSL so it was a no brainer. Can anyone give me a hand or point me to an online doc? Everything I find makes me recompile everything which I would really rather not do.
Oh and one side thing, how can I remove RPMS by wild card like *gnome*?
aNc
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
