Apache is throwing a 500 error. the log reads:
/.htaccess: without matching section
It's a wordpress block and here is the .htaccess (which was working fine
on another server. ubuntu 12.04 LTS with Apache 2.2.22
The offending .htaccess file follows. Anyone have any ideas?
# BEGIN WordPr
Thanks Colin, yes I did know that :-) I like the idea of just being able to cut
and paste any url I want to protect into a list without the worry of regex
though.
Date: Fri, 25 Oct 2013 14:08:28 +0200
From: co...@sharpheart.org
To: users@httpd.apache.org
Subject: Re: [users@httpd] protecting a l
Solved!
The new certificate was issued with a new private key but I did not receive
info about that.
I have now received both the crt and the private key and apache is up and
running again.
Thanks
-Original Message-
From: Rainer M. Canavan [mailto:rainer.cana...@sevenval.com]
Sent:
I thought each section has non-mod_cloudflare workarounds - I see only some
do.
The Apache documentation for mod_proxy has a suggestion for changing the
format of the log file (can paste a link from this device, but it should e
easy enough to find) to also include the header, but if you want to rep
> The X-Forwarded-For header is set by Apache automatically (
> http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#x-headers ). Your inside
> servers need to know to use it. >CloudFlare has some documentation about how
> to handle this on different servers:
> https://support.cloudflare.com/hc/
Hi Edward,
You do know that Location supports regular expressions? You should be able
to collapse all 3 into a single Location something like the following:
AuthType Basic
AuthName "Administrators"
AuthBasicProvider ldap-centos
Require valid-user
See http://http
On Oct 25, 2013, at 13:25 , Øyvind Lode wrote:
> Hi Harald.
>
> No.
>
> I just received the new certificate from Comodo.
>
> I assume they used the original csr file which I have stored somewhere :)
>
> I thought I documented what I did to set up the cert but can't for the life
> of me find
Hi Harald.
No.
I just received the new certificate from Comodo.
I assume they used the original csr file which I have stored somewhere :)
I thought I documented what I did to set up the cert but can't for the life of
me find it now.
So I probably just need to create a new private key but memo
Øyvind,
It sounds like the configured private key does not match your new
certificate.
did you create a new private key and CSR when you ordered the new
certificate?
Harald
On 10/25/2013 12:59 PM, Øyvind Lode wrote:
> Hi list!
>
> The ssl cert on my apache server have expired.
>
> It is actuall
Hi list!
The ssl cert on my apache server have expired.
It is actually a server at work - a important one as well so I'm a bit stressed
at the moment.
The cert is renewed and I have received the cert files.
I'm now trying to install them but I can't get it to work.
I thought it was as simple
Hi group,
I have a list of specific urls I want to protect, for example:
/site1/abc
/site2/tux
/site3/zzz
which I can configure in separate location blocks like below and that works
fine. However I was wondering if there is a simpler way I can do this like a
url whitelist file instead?
Thanks
11 matches
Mail list logo
