Caddy as reverse proxy #139

New Issue

OVERLORD · 2026-02-04T17:28:47+03:00

OVERLORD commented

2026-02-04 17:28:47 +03:00

Originally created by @ykktrcb7 on GitHub (Oct 30, 2021).

Works fine with IP address, but with reverse proxy get infinite loading screen.

Similar to other Traefik issues mentioned here, but cannot get it to work with Caddy server as reverse proxy.

Originally created by @ykktrcb7 on GitHub (Oct 30, 2021). Works fine with IP address, but with reverse proxy get infinite loading screen. Similar to other Traefik issues mentioned here, but cannot get it to work with Caddy server as reverse proxy.

OVERLORD closed this issue

2026-02-04 17:28:54 +03:00

OVERLORD commented

2026-02-04 17:28:59 +03:00

@kabukimandelux commented on GitHub (Nov 10, 2021):

Cannot help directly as I'm using Nginx reverse proxy manager. Had to activate web socket and it worked, might help you

@kabukimandelux commented on GitHub (Nov 10, 2021): Cannot help directly as I'm using Nginx reverse proxy manager. Had to activate web socket and it worked, might help you

OVERLORD commented

2026-02-04 17:29:07 +03:00

@xsteadfastx commented on GitHub (Nov 12, 2021):

im using caddy here. and this here works for me

planka.foo.tld {
        reverse_proxy planka:1337
}

planka is just the container name in the same docker network. nothing else to do for me.

@xsteadfastx commented on GitHub (Nov 12, 2021): im using caddy here. and this here works for me ``` planka.foo.tld { reverse_proxy planka:1337 } ``` planka is just the container name in the same docker network. nothing else to do for me.

OVERLORD commented

2026-02-04 17:29:09 +03:00

@arvigeus commented on GitHub (Nov 18, 2021):

I didn't had any problems with it, check my repo - caddy, docker.compose.yml. The only unorthodox thing I am doing is to use a single database across multiple containers. Ignore the tls option in my Caddyfile, it's for my cloud provider.

@arvigeus commented on GitHub (Nov 18, 2021): I didn't had any problems with it, check my [repo](https://github.com/arvigeus/arvigeus.one) - [caddy](https://github.com/arvigeus/arvigeus.one/blob/master/config/caddy/Caddyfile), [docker.compose.yml](https://github.com/arvigeus/arvigeus.one/blob/master/docker-compose.yml). The only unorthodox thing I am doing is to use a single database across multiple containers. Ignore the `tls` option in my Caddyfile, it's for my cloud provider.

OVERLORD commented

2026-02-04 17:29:18 +03:00

@REVENTOR-EU commented on GitHub (Jan 17, 2022):

Cannot help directly as I'm using Nginx reverse proxy manager. Had to activate web socket and it worked, might help you

how did you set up everything? activating websocket still gives me an endless loading circle. console still tells me websocket connection failed.

@REVENTOR-EU commented on GitHub (Jan 17, 2022): > Cannot help directly as I'm using Nginx reverse proxy manager. Had to activate web socket and it worked, might help you how did you set up everything? activating websocket still gives me an endless loading circle. console still tells me websocket connection failed.

OVERLORD commented

2026-02-04 17:29:24 +03:00

@MatejLach commented on GitHub (Mar 10, 2024):

Old issue but in case it's useful, this works for me:

http://planka:port {
    reverse_proxy :3000 {
        header_up X-Real-IP {remote_host}
    }


    @websockets {
        header Connection *Upgrade*
        header Upgrade websocket
    }
    reverse_proxy @websockets localhost:3000
}

@MatejLach commented on GitHub (Mar 10, 2024): Old issue but in case it's useful, this works for me: ``` http://planka:port { reverse_proxy :3000 { header_up X-Real-IP {remote_host} } @websockets { header Connection *Upgrade* header Upgrade websocket } reverse_proxy @websockets localhost:3000 } ```

OVERLORD referenced this issue

2026-02-04 17:45:59 +03:00

[Unable to migrate] Migration not found #189

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#139