uses port 80, which should get the client to HAProxy's Frontend, but either the Frontend is not configured to point to a Backend for artifactory.mylocal, or the Backend is not configured properly to get clients properly routed.

You didn't provide a lot of necessary details so below I'm trying to work out what you are trying to do.Īre you sure your Frontend is configured to consume the Backend? I think typically you get 503 when there is no Backend (HAProxy tried to refer the client to a Backend, but couldn't figure out what to do). It's not configured correctly if you are getting warnings. But I also feel I've already tried that (among other things). In the area of the shared front end probably needing to be on 443 and offloading SSL, with a wildcard certificate covering the *.mylocal domain. I very much think I am missing something on the SSL side. If I add artifactory.mylocal to alternative DNS names (System > Advanced), I get the login to pfsense. Going to gives 503 no service available and going to gives a DNS rebind.

Single server instance with a name, its IP and port, no encrypt and no SSL check I have a virtual IP for the HAProxy internal frontend to consume, 192.168.52.250.ĭNS resolver has an A record for artifactory.mylocal to 192.168.52.250 So, here's the configuration for one of my services, artifactory: I feel like it's configured correctly, but then I get DNS rebind attack warnings. I want to have the reverse proxy in front of it as I don't want to remember port numbers and want the flexibility of moving things around without clients knowing. I also have services that are not public facing. I created a virtual IP for HAProxy to consume and proxy the external-originating-traffic to the service it needs to be destined for. I have HAProxy configured just fine for services exposed externally.

Pfsense haproxy