Cannot set up route/entry for Wordpress in docker-compose

[Currrupted]

Hey there! I stumbled across your project and I am really digging it so far! I am trying to set up Reproxy as a reverse proxy in my Docker Compose set up. I want to build a setup for my husband's web presence, using Docker.

Unfortunately, I am currently unable to implement Reproxy correctly. So far I have both Reproxy and Wordpress containers (one each). This is what I'm trying to achieve. When connecting to localhost, Reproxy should redirect/connect to the Wordpress container. I want to add a Mailcow installation later, so the Wordpress container should be the default when connecting to the domain. So when I enter http://localhost I should see my website and/or Wordpress Dashboard.

Unfortunately this doesn't work for me yet and I cannot tell why...

This is my compose file for Reproxy:

services:
  reproxy:
    image: umputun/reproxy:master
    container_name: reproxy
    hostname: reproxy
    ports:
      - "80:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./web:/web
    environment:
      - TZ=Europe/Amsterdam
      - LISTEN=0.0.0.0:8080
      - DOCKER_ENABLED=true
      - DOCKER_AUTO=false
      - DEBUG=true
      - SSL_TYPE=none

This is the compose settings in the file for Wordpress:

wordpress:
    depends_on:
      - db
    image: wordpress:latest
    volumes:
      - wordpress_data:/var/www/html
    restart: always
    hostname: wordpress
    container_name: wordpress
    environment:
      WORDPRESS_DB_HOST: db
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: wordpress
      WORDPRESS_DB_NAME: wordpress
    labels:
      - reproxy.enabled= true
      - reproxy.server= localhost
      - reproxy.port=80

When I try to access http://localhost, I only see Server error... I feel like I am doing something wrong, but I tried everything and don't know how to fix this. Thank you!

[Currrupted]

Also, this is the container output (through sudo docker-compose up):

reproxy    | 2022/02/13 19:25:54.846 [DEBUG] {provider/docker.go:302 provider.(*Docker).listContainers} container reproxy excluded
reproxy    | 2022/02/13 19:25:54.846 [DEBUG] {provider/docker.go:336 provider.(*Docker).listContainers} completed list
reproxy    | 2022/02/13 19:25:54.847 [INFO]  {discovery/discovery.go:140 discovery.(*Service).Run} proxy  docker: localhost ^/wordpress/(.*) -> http://172.19.0.4:80/$1
reproxy    | 2022/02/13 19:26:07.561 [WARN]  {proxy/proxy.go:239 proxy.(*Http).proxyHandler.func2} no match for  /

[umputun]

the log shows the exact issue - the route you asked reproxy to handle is /wordpress, and such requests will be properly routed to your wordpress containers, i.e. http://localhost/wordpress should reach your site.

In order to change the default routing, you should set it implicitly, by adding reproxy.route label, i.e. --reproxy.route: '^/(.*)'

I think the source of confusion is outdated documentation. Back in days, the default route was ^/(.*), however, this was troublesome in case multiple containers were involved and we have changed it to ^/<container-name>/(.*) which you see now in the logs. I'll correct the documentation but your fix is to add reproxy.route as described above

[umputun]

moved to discussions

[Currrupted]

@umputun Thank you for the time and support! I changed the label and also added the -HEADER options to the Reproxy service file. I don't get the error anymore, however it doesn't seem to be working correctly yet.

When I access localhost, my Browser tries to connect for several minutes (blank screen), before eventually saying that there was a problem loading the page. Do you know what could be the cause? Again, thank you for your work

[Currrupted]

I suspect that it might have something to do with Wordpress, however I don't see any error messages there. I tried it out with whoami and it does work... Really strange!

[umputun]

as long as you see smth like proxy docker: localhost ^/(.*) -> http://172.19.0.4:80/$1 in your logs repoxy will try to forward to this container if you hit http://localhost. I'm not sure if the WordPress container really serves anything on port 80, but you can try it by discovering ip:port (docker inspect) and accessing it directly

[Currrupted]

as long as you see smth like proxy docker: localhost ^/(.*) -> http://172.19.0.4:80/$1 in your logs repoxy will try to forward to this container if you hit http://localhost. I'm not sure if the WordPress container really serves anything on port 80, but you can try it by discovering ip:port (docker inspect) and accessing it directly

Ok, got it! According to the logs, the connection does work correctly. So it must have something to do with Wordpress. I did some research and apparently WP requires a correct value for the X-Forward-Proto header. If the SSL admin isn't set correctly, WP will stay in a redirect loop. So the issue doesn't lie with Reproxy. Thanks!

https://wordpress.org/support/article/administration-over-ssl/#using-a-reverse-proxy