# Trying to get domain name routing

**URL:** <https://discourse.haproxy.org/t/trying-to-get-domain-name-routing/8029>\
**Category:** Help!\
**Created:** [October 17, 2022, 4:57pm UTC](https://discourse.haproxy.org/t/trying-to-get-domain-name-routing/8029 "2022-10-17T16:57:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yamazaki](https://avatars.discourse-cdn.com/v4/letter/y/6de8d8/32.png) [@yamazaki](https://discourse.haproxy.org/u/yamazaki)\
**Post date:** [October 17, 2022, 4:57pm UTC](https://discourse.haproxy.org/t/trying-to-get-domain-name-routing/8029/1 "2022-10-17T16:57:31Z")

</div>

I’m trying to route to two different sites, but I always get a 503. I checked the host running haproxy and I am able to curl to the backends, can you please help this newb identify what is wrong with the haproxy configuration, thanks

# 503 Service Unavailable

No server is available to handle this request.

```auto
global
    chroot /var/lib/haproxy
    user haproxy
    group haproxy
    daemon
    stats socket /run/haproxy/admin.sock mode 660 level admin
    log /dev/log local0
    log /dev/log local1 notice
    ssl-default-bind-options no-sslv3 no-tls-tickets no-tlsv10 no-tlsv11
    ssl-default-bind-ciphers ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
    ssl-default-server-options no-sslv3 no-tls-tickets no-tlsv10 no-tlsv11
    ssl-default-server-ciphers ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS
    tune.ssl.default-dh-param 2048

defaults
    mode http
    log global
    log /dev/log local1 notice
    timeout connect 5000ms
    timeout client 50000ms
    timeout server 50000ms
    option httpclose
    option forwardfor except 127.0.0.0/8
    option redispatch
    option abortonclose
    option httplog
    option dontlognull
    errorfile 400 /etc/haproxy/errors/400.http
    errorfile 403 /etc/haproxy/errors/403.http
    errorfile 408 /etc/haproxy/errors/408.http
    errorfile 500 /etc/haproxy/errors/500.http
    errorfile 502 /etc/haproxy/errors/502.http
    errorfile 503 /etc/haproxy/errors/503.http
    errorfile 504 /etc/haproxy/errors/504.http

backend be-argocd
    mode http
    option forwardfor
    server be-argocd 10.43.167.168:443 ssl verify none

backend be-blog
    mode http
    option forwardfor
    server be-blog 10.43.195.117:80

frontend fe-http
    bind 10.0.0.4:81
    mode http
    option httplog
    maxconn 3000
    option forwardfor
    acl acl-argocd hdr(host) -i argocd.myproject.local
    acl acl-blog hdr(host) -i blog.myproject.local
    use_backend be-argocd if acl-argocd
    use_backend be-blog if acl-blog

```

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [October 17, 2022, 5:27pm UTC](https://discourse.haproxy.org/t/trying-to-get-domain-name-routing/8029/2 "2022-10-17T17:27:32Z")

</div>

If you are using a non-standard port like 81, your client will send the host header with that port number, so you probably need:

```
acl acl-argocd hdr(host) -i argocd.myproject.local:81
acl acl-blog hdr(host) -i blog.myproject.local:81

```

---

<div class="post-metadata">

**Author:** ![yamazaki](https://avatars.discourse-cdn.com/v4/letter/y/6de8d8/32.png) [@yamazaki](https://discourse.haproxy.org/u/yamazaki)\
**Post date:** [October 17, 2022, 5:59pm UTC](https://discourse.haproxy.org/t/trying-to-get-domain-name-routing/8029/3 "2022-10-17T17:59:17Z")

</div>

Thanks again Lukas, setting the port number resolved the issue