Zero Trust VaultWarden issue tunneling.

When trying reach my domain achllys.net I get error 502. What might I be doing wrong? Clouldflare

version: '2.3'

services:
  cloudflared:
    image: cloudflare/cloudflared:latest
    container_name: ach
    command: tunnel run --token "hidden for reasons"
    networks:
      - ach

networks:
  ach:
    external: true

version: '2.3'

services:
  cloudflared:
    image: cloudflare/cloudflared:latest
    container_name: ach
    command: tunnel run --token "hidden for reasons"
    networks:
      - ach

networks:
  ach:
    external: true

VaultWarden

version: '3.7'

services:
    server:
        container_name: vaultwarden
        volumes:
            - '/docker/vaultwarden:/data/'
        environment:
            - SIGNUPS_ALLOWED=true
            - ADMIN_TOKEN=
        ports:
            - '8090:80'
        image: 'vaultwarden/server:latest'
        networks:
            - ach

networks:
    ach:
        driver: bridge

version: '3.7'

services:
    server:
        container_name: vaultwarden
        volumes:
            - '/docker/vaultwarden:/data/'
        environment:
            - SIGNUPS_ALLOWED=true
            - ADMIN_TOKEN=
        ports:
            - '8090:80'
        image: 'vaultwarden/server:latest'
        networks:
            - ach

networks:
    ach:
        driver: bridge

8 Replies

Chaika•5mo ago

502 is from the tunnel being unable to connect to your service. Those issues can all be troubleshooted the same way: - Check cloudflared logs and see what error it's failing with - If you can't figure it out from the error/it's generic conn failed, try the exact same fetch via curl from the same cloudflared host (in this case container) and debug from there That screenshot you showed with the public hostname doesn't make sense, you can't just have a port with no ip. Since the traffic is going over the local docker network I think you'd want vaultwarden:80