On 2015-04-23 17:11, Baptiste wrote:
On Thu, Apr 23, 2015 at 4:18 PM,
wrote:
SSLv3 is not allowed anywhere in our infrastructure, it is disabled
already.
You did not catch the point.
HAProxy may use SSLv3 to get connected to the server.
so disable sslv3 on the server side on haproxy just t
On Thu, Apr 23, 2015 at 10:01:19AM +0200, Willy Tarreau wrote:
> Hi Simon,
>
> On Thu, Apr 23, 2015 at 02:51:25PM +0900, Simon Horman wrote:
> (...)
> > This series attempts to address that problem by first disentangling the
> > state and colour of servers in the first two patches, which are new -
Hi All,
I’m playing with the new set-path feature and encountered a bug. I’m using
1.6-dev1 plus all the patches up to Apr 22nd, I think we’re all clear that
set-path was not working at all in 1.6-dev1 itself. It does now work but not in
all situations I’d expect.
My config is below. I do nc -
On Thu, Apr 23, 2015 at 4:18 PM, wrote:
> SSLv3 is not allowed anywhere in our infrastructure, it is disabled already.
>
You did not catch the point.
HAProxy may use SSLv3 to get connected to the server.
so disable sslv3 on the server side on haproxy just to ensure this is
not the root of the pr
On 23/04/2015 6:01 PM, wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi!
>
> I'm having trouble with one of our HAProxy-Servers that uses a backend
with TLS. When starting HAProxy the backend will report all servers as down:
>
>> Server web_remote/apache_rem_1 is DOWN, reason: L
Afficher la version web. (http://trk.mix.uneoffredeouf.com/view/5rs-kwV3.php) |
Me désinscrire. (http://trk.mix.uneoffredeouf.com/usb/5rs-kwV3.php) | Signaler
comme courrier indésirable. (mailto:ab...@dgcnit.fr)
http://trk.mix.uneoffredeouf.com/tk/5rs-kwV3-bPE.php
http://trk.mix.uneoffredeouf
SSLv3 is not allowed anywhere in our infrastructure, it is disabled
already.
On 2015-04-23 16:09, Baptiste wrote:
maybe the server refuses sslv3...
Can you disable sslv3 on the server side?
Baptiste
On Thu, Apr 23, 2015 at 3:38 PM,
wrote:
I've checked again, but the time on those servers
maybe the server refuses sslv3...
Can you disable sslv3 on the server side?
Baptiste
On Thu, Apr 23, 2015 at 3:38 PM, wrote:
> I've checked again, but the time on those servers is correct..
>
> On 2015-04-23 14:16, Daniel Schneller wrote:
>>
>> Have you checked the time/date on the Haproxy host
I've checked again, but the time on those servers is correct..
On 2015-04-23 14:16, Daniel Schneller wrote:
Have you checked the time/date on the Haproxy host?
If they are wrong, the certificate might look bad from HAProxy’s
point of view.
Daniel
--
Daniel Schneller
Infrastructure Architect /
Have you checked the time/date on the Haproxy host?
If they are wrong, the certificate might look bad from HAProxy’s point of view.
Daniel
--
Daniel Schneller
Infrastructure Architect / Developer
CenterDevice GmbH
> On 23.04.2015, at 10:00, i...@linux-web-development.de wrote:
>
> -BEGI
Hi Simon,
On Thu, Apr 23, 2015 at 02:51:25PM +0900, Simon Horman wrote:
(...)
> This series attempts to address that problem by first disentangling the
> state and colour of servers in the first two patches, which are new -
> arguably a worthwhile clean-up in its own right. The remaining two patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
I'm having trouble with one of our HAProxy-Servers that uses a backend
with TLS. When starting HAProxy the backend will report all servers as
down:
Server web_remote/apache_rem_1 is DOWN, reason: Layer6 invalid
response, info: "SSL handsha
12 matches
Mail list logo
