Hi all,
I am testing haproxy as follows:
System1: 24 Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz, 64 GB. This system
is running 3.19.0 kernel, and hosts the following servers:
1. nginx1 server - cpu 1-2, 1G memory, runs as a Linux
container using cpuset.cpus feature.
Hello Baptiste,
We have access to some non-public networks. These networks are only accessible
via its own proxy server. So based on the IP-address the http-traffic must be
proxied to the correct proxy server.
I have realized the routing using squid:
cache_peer 172.16.0.1 parent 3128 0
Whoops my fault while testing.
Indeed, on the backends I connect to 1935 again, I see a connection
coming in but no clear data. That part is actually my issue and
difficult to trace.
2015-03-29 16:11 GMT+02:00 Baptiste bed...@gmail.com:
frontend rtmp_https
bind
I think I’ve found the issue. During test, I’m visiting a hostname
http://example/. But the acl condition req.hdr_ip(host) will only work if I
visit http://192.168.0.1/.
Is it possible to let haproxy resolve the domain name and then check the IP
address?
Op 29 mrt. 2015, om 14:04 heeft
Matt,
I won't do your configuration since I have no idea what you want to do.
Share what you did exactly, share more information about the issues
(logs, etc...) and we may help.
Baptiste
On Sun, Mar 29, 2015 at 3:53 PM, Matt . yamakasi@gmail.com wrote:
Hi,
I have tried all, also TCP,
frontend rtmp_https
bindxxx.xxx.xxx.xxx:443 name
xxx.xxx.xxx.xxx:443 ssl crt /var/etc/haproxy/mycert.pem
modetcp
log global
maxconn 9
timeout client 60
Hi,
I have tried all, also TCP, I'm configuring it using pfsense so I need
to grab it from there.
Do you have a small example of what should work ? I can paste that to
pfsense to than.
In my app I just should connect rtmps to port 443 on ha, offload and
connect to normal rtmp 1935 again was my
Bapiste,
No that was not the idea but I was debugging with someone of
pfsense/haproxy so suggestions were good.
This is what I use for RTMP:
frontend rtmp_https
bindxxx.xxx.xxx.xxx:443 name
xxx.xxx.xxx.xxx:443 ssl crt /var/etc/haproxy/mycert.pem
mode
Hello,
I’m trying to route http-requests based on destination IP address. I’ve got the
following configuration, but unfortunately its not working:
frontend proxy :3128
acl host_destip req.hdr_ip(host) 192.168.0.1
use_backend a if host_destip
default_backend b
I’m expecting
On Sun, Mar 29, 2015 at 1:05 PM, Matt . yamakasi@gmail.com wrote:
Hi Guys,
I'm trying to offload a rtmp connection where I connect using rtmps to
ha proxy and offload the ssl layer there.
In some strange way I can't get it working but I can with other
services the same way.
Is RTMP a
Hi,
No HAProxy won't do this.
Instead, if you could explain us clearly what is your problem, we may
be able to help you.
For now you just explain what you tried to achieve.
Baptiste
On Sun, Mar 29, 2015 at 3:33 PM, Abdelouahed Haitoute
ahaito...@rinis.nl wrote:
I think I've found the issue.
Hi Matt,
Le 29/03/2015 16:19, Matt . a écrit :
Whoops my fault while testing.
Indeed, on the backends I connect to 1935 again, I see a connection
coming in but no clear data. That part is actually my issue and
difficult to trace.
Then can you re-provide the expected configuration ? Because
Hi Cyril,
Thanks, I'm indeed using red5 in my setup, client is flex.
Just non ssl at all, so only 1935 over HA works prefectly. When I set
my frontend to ssl offloading on TCP 443 I see on my red5 server my
client coming in when connecting but than it hangs, no other data in
de red5 log.
I will
Hi Guys,
I'm trying to offload a rtmp connection where I connect using rtmps to
ha proxy and offload the ssl layer there.
In some strange way I can't get it working but I can with other
services the same way.
Is RTMP a hard one in this case ?
Thanks,
Matt
14 matches
Mail list logo
