Weird error in Apache error log

11 posts / 0 new
Last post
#1 Thu, 01/14/2010 - 16:22
Owdy

Weird error in Apache error log

I get tons of these:

[Thu Jan 14 23:59:06 2010] [error] [client 88.193.93.] Invalid method in request \x16\x03\x01 [Thu Jan 14 23:59:28 2010] [error] [client 88.193.93.] Invalid method in request \x16\x03\x01 [Fri Jan 15 00:01:11 2010] [error] [client 88.193.93.] Invalid method in request \x16\x03\x01 [Fri Jan 15 00:01:40 2010] [error] [client 88.193.93.] Invalid method in request \x16\x03\x01 [Fri Jan 15 00:02:03 2010] [error] [client 88.193.93.**] Invalid method in request \x16\x03\x01

Google says its SSL error but i have no idea whats wrong.

Thu, 01/14/2010 - 16:43
ronald
ronald's picture

google also says:

The fix is to specify the port in all of your VirtualHost & NameVirtualHost directives in your apache httpd config.
NameVirtualHost 196.168.1.100:80
NameVirtualHost 196.168.1.100:443
VirtualHost www.foobaz.com:80
VirtualHost www.foobaz.com:443

Thu, 01/14/2010 - 16:42
andreychek

Well, are your users seeing some kind of problem, or did you just happen to notice some errors like the above in your logs?

If your users are seeing a problem, what error are they seeing in their browser?

-Eric

Fri, 01/15/2010 - 00:06 (Reply to #3)
Owdy

Users havent sayd anything, just saw that in log.

Fri, 01/15/2010 - 00:12
Owdy

Ronald, my httpd.conf file is empty.

Fri, 01/15/2010 - 01:43
ronald
ronald's picture

this configuration file should not be empty..per haps it is called differently on your server.

Fri, 01/15/2010 - 01:46
Owdy

Well i havent touched it, i have used Virtualmin at start.

Fri, 01/15/2010 - 03:25
Owdy

I commented out 'Listen 443' in /etc/apache2/ports.conf , lets see how it goes.

Fri, 01/15/2010 - 09:37
andreychek

Yeah, the various distros call their config files different names -- CentOS/RHEL use httpd.conf, and Ubuntu/Debian use apache2.conf.

However, I don't recommend removing port 443 from your ports.conf file :-)

I'd only do that if you don't want to use SSL at all.

The key isn't to remove ports, it's to make sure that anytime an IP address or hostname is mentioned in a NameVirtualHost or VirtualHost definition, it's also accompanied by a port.

-Eric

Fri, 01/15/2010 - 09:43
Owdy

I added this in Apache2.conf

NameVirtualHost *:443

But now:

sudo /etc/init.d/apache2 restart Restarting web server: apache2[Fri Jan 15 14:43:11 2010] [warn] NameVirtualHost *:443 has no VirtualHosts ... waiting .[Fri Jan 15 14:43:13 2010] [warn] NameVirtualHost *:443 has no VirtualHosts

Fri, 01/15/2010 - 10:01
andreychek

It's possible that, if your users aren't seeing any problems, tinkering with the config file may end up breaking more things than it's fixing :-)

You shouldn't use "*" for anything in NameVirtualHost or VirtualHosts -- you'd want to use explicit IP addresses and hostnames. Same with ports, don't use a *, use the actual port names.

-Eric