WOODPECKER_GITEA_URL doesn't work

[FarisZR]

Component

server, web-ui

Describe the bug

It seems like the WOODPECKER_GITEA_URL Environment variable doesn't work. no matter what i do, it still uses try.gitea.io and doesn't use codeberg.org

System Info

**all of the tokens are edited and revoked**

version: '3.3'
services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    ports:
      - 127.0.0.1:9002:8000
    volumes:
      - ./woodpecker:/var/lib/woodpecker/
    environment:
      - 'WOODPECKER_OPEN=true'
      - 'WOODPECKER_HOST=https://cd.website.com'
      - 'WOODPECKER_GITEA=true'
      - 'WOODPECKER_GITEA_URL=https://codeberg.org'
      - 'WOODPECKER_GITEA_CLIENT=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx'
      - 'WOODPECKER_GITEA_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
      - 'WOODPECKER_AGENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest
    command: agent
    restart: always
    depends_on:
      - woodpecker-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000 
      - 'WOODPECKER_AGENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
      - WOODPECKER_BACKEND=docker

Additional context

this is an error that shows up for the agent, however i'm not sure if it has anything to do with this problem

woodpecker-agent_1   | {"level":"error","error":"rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \"error reading from server: EOF\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \"too_many_pings\"","time":"2021-11-26T22:08:15Z","message":"grpc error: done(): code: Unavailable: rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \"error reading from server: EOF\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \"too_many_pings\""}

Validations

• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

[FarisZR]

ah, classic chromium cache.