Re: [Sks-devel] Question about apache2 configuration

[Todd Lyons]

On Tue, Nov 12, 2013 at 6:45 AM, Filip Stefaniak <address@hidden> wrote:
>
>> Your webserver doesn't return the sks interface when contacted as
>> p80.pool.sks-keyservers.net or even pool.sks-keyservers.net so it
>> can't be used as part of the port80 Pool
>
> Ok. So as I assume I have to add:
> <VirtualHost *:80>
> ServerAlias pool.sks-keyservers.net
> ServerAlias p80.pool.sks-keyservers.net

No, because you are adding to a name-based virtual hosting
configuration.  You would have to add EVERY SINGLE POSSIBLE dns cname
that could be pointed to pool.sks-keyservers.net (such as
keys.gnupg.org).  Instead, use an IP based virtual hosting
configuration, one that doesn't care what Host header gets sent to it.

<VirtualHost your.ip.add.ress:80>
ServerName your.server.name
...
</VirtualHost>

Then verfiy with 'httpd -S' that it is listed in the first VirtualHost
configuration (which is the ip based virtual hosting) :

VirtualHost configuration:
208.89.139.251:80      sks.mrball.net (/etc/httpd/conf.d/sks.conf:23)
208.89.139.251:443     sks.mrball.net (/etc/httpd/conf.d/sks.conf:37)

...instead of in the name-based virtual hosting section:

wildcard NameVirtualHosts and _default_ servers:
*:11371                sks.mrball.net (/etc/httpd/conf.d/sks.conf:8)
_default_:443          mail.mrball.net (/etc/httpd/conf.d/ssl.conf:74)
*:80                   is a NameVirtualHost

This is why the output of httpd -S is *SO* important.  It tells you
how apache is reading and interpreting your configuration.  If you are
having problems, post your entire sks.conf file (assuming you have it
separate like mine) and the output of httpd -S (the full output,
otherwise some other part that you're not showing us could be causing
a problem).

...Todd
-- 
SOPA: Any attempt to [use legal means to] reverse technological
advances is doomed.  --Leo Leporte