# kryptokronad behind HAProxy

From polar-it on Discord

There is a lot to add to this to fill details, however this is enough for people familar to get going ;)

If you are not familar with HAProxy then check it out if you're a sysadmin/devops person it is pretty great. If you are a Containers/Kubernetes kind of person then this kind of thing is handle by the load balancers, sometimes they are HAProxy under the covers.

Combine the below with iburnmycd's [turtlecoind-ha](https://github.com/turtlecoin/turtlecoind-ha) and [turtlecoin-api-proxy](https://github.com/turtlecoin/turtlecoin-api-proxy) and you should have a farily reliable end point for daemon requests.

```
#---------------------------------------------------------------------
# main frontend which proxys to the backends
#---------------------------------------------------------------------
frontend  main *:11898

    default_backend            trtl-daemon 

#---------------------------------------------------------------------
# round robin balancing between the various backends
#---------------------------------------------------------------------
backend trtl-daemon 
    balance     roundrobin
    option httpchk GET /getinfo
    http-check expect rstring true

# Local node on port 11999
    server  app1 127.0.0.1:11999 check
    server  app2 < node host1 >:11898 check
    server  app3 < node host2 >.11898 check
    server  app4 < node host3 >:11898 check
```

***polar-it:** This actually work on* [*trtl-explorer.xhub.cloud*](https://trtl-explorer.xhub.cloud/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kryptokrona.org/kryptokrona/kryptokronad-behind-haproxy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.