> On Jul 10, 2020, at 9:15 PM, Gabri Tofano <ga...@tofanos.com> wrote: > > Here: > > LAB1-LB1$ relayctl sh sum > Id Type Name Avlblty Status > 1 redirect http active > 1 table web_servers:80 active (1 hosts) > 1 host 172.16.101.31 4.87% up > 2 table nc_servers:80 active (1 hosts) > 2 host 172.16.101.32 4.86% up > 2 redirect https down > 3 table web_servers:443 empty > 3 host 172.16.101.31 0.00% down > 4 table nc_servers:443 empty > 4 host 172.16.101.32 0.00% down >
Does http work with redirects? It wasn’t clear if it did or not in your first post. Indications from your pf anchor rules and the down status above, and the check http attribute on the https forward to directives tell me relayd isn’t liking your check http configuration for port 443. Start by switching to check icmp or check tcp or something else, see if it works, unless you can fix the check http based on logs or otherwise. > The low availability is due too the web servers were turned off. > > Thanks! > >> On 2020-07-10 17:41, Sebastian Benoit wrote: >> Gabri Tofano(ga...@tofanos.com) on 2020.07.07 15:38:17 -0400: >>> When using redirections, no listening ports are open (I guess due to >>> relayd using pf nat rules) >> correct >>> and I'm unable to reach both backend servers. >> show the output of "relayctl sh sum". >
