HAproxy unable to login on wordpress/wp-admin page

  • hi all

    fairly/very new on proxy enviroment, so incase im overlooking something silly my apologies,

    i have a PFsence as modem/router wich has the HAproxy packages installed.
    made the rules for 80 and 443 on wanside.
    installed ACME with cloudflare dns challange,
    configured HAproxy for 3 backends,
    1 backend being a wordpress website,
    1 backend being a Synology nas
    1 backend being HASSIO
    when i set all of that up it all seemed to be working.
    then i tried to login my wordpress website on a external location,
    all the pages load without a problem, untill i try to login that is...
    for some reason when i go to domain.nl/wp-admin and type in my username and password, hit enter, it seems like it just refreshes the page?
    no unknown/bad username notification, no login notification, no nothing....

    when i hit show configuration i get > https://paste.ubuntu.com/p/syhtzBdFJd/
    did alter my ip and some domain or subdomain names,

  • @darkalien
    Youve got 1 frontend that listens on both :80 and :443, thats okay.. BUT does not mean that if traffic is directed to 1 backend that it will then use the server with the same port..
    So your wordpress backend has 2 servers, and will 'loadbalance' traffic over both.. Meaning a single client-browser will sometimes connect to and sometimes to I doubt that that is what you intended..? This could be changed by specifying some acl in the backend and use_server action so that https traffic will always hit the :443 server and non-https will go to :80 .. but much clearer would be to make 2 backends out of that configuration, or redirect all :80 traffic to https perhaps on the frontend side already.?.

    Also i wonder, have you configured WordPress 'properly' to function behind a reverse-proxy.? https://www.digitalocean.com/community/tutorials/how-to-use-haproxy-as-a-layer-7-load-balancer-for-wordpress-and-nginx-on-ubuntu-14-04

  • @PiBa

    thankyou for your answer, though i found the issue..
    in wordpress config file i had change the base url and i forgot a / at the end.....

Log in to reply