Docker compose: Gitea+Woodpecker+WPAgent

[timteka]

Hi, can't solve the authorization problem. Here's my compose file:

networks:
  gitea:
    external: false

volumes:
  gitea:
    driver: local

services:
  gitea:
    image: gitea/gitea:latest
    container_name: gitea
    environment:
      - USER = git
      - USER_UID = 121
      - USER_GID = 121
      - HTTP_ADDR = 0.0.0.0
    restart: always
    networks:
      - gitea
    volumes:
      - /var/lib/gitea-compose/data:/data
      - /home/git/.ssh/:/data/git/.ssh
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - "3000:3000"
      - "2222:22"
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    container_name: woodpecker-server
    restart: always
    ports:
      - 8000:8000
      - 9000:9000
    networks:
      - gitea
    volumes:
      - /var/lib/gitea-compose/woodpecker:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=http://10.10.2.31
      - WOODPECKER_SERVER_ADDR=:8000
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=http://10.10.2.31:3000
      - WOODPECKER_GITEA_CLIENT=a7e08042-f03b-4f15-9793-6bf2bedf1c42
      - WOODPECKER_GITEA_SECRET=gto_qncojzjvdc53rwyixzqr3ruu3oab5ekbcxpwj2mphyldrsoy7brq
      - WOODPECKER_AGENT_SECRET=c5704bc389f1e3d47f1c4751d1295c86
      - WOODPECKER_GITEA_SKIP_VERIFY=true
      - WOODPECKER_GRPC_ADDR=:9000

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest
    container_name: woodpecker-agent
    command: agent
    depends_on:
      woodpecker-server:
        condition: service_healthy
    networks:
      - gitea
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/lib/gitea-compose/woodpecker-agent:/etc/woodpecker
    environment:
      - WOODPECKER_SERVER=10.10.2.31:9000
      - WOODPECKER_AGENT_SECRET=c5704bc389f1e3d47f1c4751d1295c86
      - WOODPECKER_BACKEND_DOCKER_NETWORK=gitea 

[timteka]

Clicking on Login button in Woodpecker init page produces:

Authorization failed
Unregistered Redirect URI

[timteka]

The settings of the Application in Gitea:

[timteka]

What was my previous version )) And that's why i've decided to explicitely set port via:

WOODPECKER_SERVER_ADDR=:8000

[zc-devs]

They might be different settings.
Try

WOODPECKER_HOST=http://10.10.2.31:8000
WOODPECKER_SERVER_ADDR=:8000

[timteka]

Still no success:

Nothing happens after authorization attempt.
And then timeout with:
2024/04/26 18:10:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /login/oauth/authorize?client_id=a7e08042-f03b-4f15-9793-6bf2bedf1c42&redirect_uri=http%3A%2F%2F10.10.2.31%3A8000%2Fauthorize&response_type=code&state=woodpecker for 10.10.2.12:53194, 303 See Other in 8.7ms @ auth/oauth.go:362(auth.AuthorizeOAuth)

[timteka]

Docker inspect reveals correct WOODPECKER_GITEA_CLIENT and WOODPECKER_GITEA_SECRET.
Strangeness in exposed ports:

"ExposedPorts": {
                "443/tcp": {},
                "80/tcp": {},
                "8000/tcp": {},
                "9000/tcp": {}
            }

[zc-devs]

vpn

timeout

requests stuck in the middle / truncated responses / SSL errors

=> check the MTU

[zc-devs]

networks:
  gitea:
    external: false

I wonder, how do you access Gitea and Woodpecker? What do you type in the browser?
Where did you get 10.10.2.31? Is it your Docker host's IP?

---

Cannot reproduce using Docker host IP.
Tried Gitea site-wide OAuth2 application and user-wide: both work.
docker-compose.yaml.txt
Gitea 1.21.11, Woodpecker 2.4.1, Docker 4.27.2, Windows 10.

[timteka]

Thanks for your help.... We use vpn server in our environment, so each VM is connected to it and getting that 10.10.2.x address.
As for your test docker-compose..... i run linux, so only the docker/docker compose are older (e.g. Docker Compose version v2.26.1) and Docker version 25.0.4.

[timteka]

I've tried to setup the same config in VirtualBox. Just Gitea and WP-server. Still the same login failure (with 303 See Other).

[qwerty287]

Is the config above still correct? Because as @zc-devs pointed out, the WOODPECKER_HOST must be the full user-facing URL, including port etc. And 303 is the correct code after the authorization.

[timteka]

Yep. Still the output in Chrome is:

[qwerty287]

Well, this and the next request actually seem correct, but then, an error occurred.
Is there something in the logs? Can you give me the request details for the login?error=oauth_error?

[timteka]

I'll do it later if you don't mind. Some urgent stuff to do.

[timteka]

@qwerty287 please import the chrome .har.
127.0.0.1.har.zip

[timteka]

My local config in Virtualbox on Win11:

networks:
  gitea:
    external: false

volumes:
  gitea:
    driver: local

services:
  gitea:
    image: gitea/gitea:latest
    container_name: gitea
    environment:
      - USER = git
      - USER_UID = 122
      - USER_GID = 122
      - HTTP_ADDR = 0.0.0.0
    restart: always
    networks:
      - gitea
    volumes:
      - /var/lib/gitea-compose/data:/data
      - /home/git/.ssh/:/data/git/.ssh
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 3000:3000
      - 2222:22
      
 woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    container_name: woodpecker-server
    restart: always
    ports:
      - 8000:8000
      - 9000:9000
    networks:
      - gitea
    volumes:
      - /var/lib/gitea-compose/woodpecker:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=http://127.0.0.1:8000
      - WOODPECKER_SERVER_ADDR=:8000
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=http://127.0.0.1:3000
      - WOODPECKER_GITEA_CLIENT=32922d21-012d-4407-9361-fc55323d757e
      - WOODPECKER_GITEA_SECRET=gto_vemy3dfho7y5kq7w6twse6xov7cb7lsfqbistvdd6wsrcjh7gjnq
      - WOODPECKER_GITEA_SKIP_VERIFY=true

Below are my network settings:

[zc-devs]

WOODPECKER_GITEA_URL=http://127.0.0.1:3000

Note, that each host have 127.0.0.1. And 127.0.0.1 from Woodpecker container is Woodpecker itself, not Docker host, nor Gitea.

BTW, do you really want to access the services by IP?

[timteka]

Maybe that's the problem. But I'm novice "docker", not sure if we can refer to container nics by name from 'environment' sections (. Moreover you 've succeed with my config on your PC.
Probably smth wrong with my Gentoo VM. I'll try to experiment with Ubuntu tomorrow.

[pat-s]

I'm novice "docker",

Gentoo VM

Virtualbox on Win11:

vpn server

Maybe you're playing with too many balls here? Especially if you're new to docker this sounds like a bit of an "advanced" playground to start with.

Why not start with a simpler setup and take it step by step, then you see on which point you encounter errors. You can always rent a VM in the cloud for a few pennies per hour to play around in a much better vanilla setup. Should be worth it if you can save hours of your lifetime (and from others) ;)

[timteka]

Absolutely identical result on 'brand new' Ubuntu server. I've only installed the dockers and run my compose file.
Still 'bad request' and
127.0.0.1 ubuntu.har.zip
'Authorization failed Unregistered Redirect URI'