ZottelchenšŸ­
ZottelchenšŸ­
WWindmill
Created by ZottelchenšŸ­ on 3/11/2024 in #help
Unable to use Assistants - (WARNING:tornado.access:404)
I very much overthunk it. The working labels are:
windmill_server:
...
labels:
caddy: "windmill.example.org"
caddy.tls.dns: "cloudflare <snip>"
caddy.tls.resolvers: 1.1.1.1
caddy.reverse_proxy: "{{upstreams http 8000}}"

lsp:
...
labels:
caddy: "windmill.example.org"
caddy.tls.dns: "cloudflare <snip>"
caddy.tls.resolvers: 1.1.1.1
caddy.@ws.0_header: Connection *Upgrade*
caddy.@ws.1_header: Upgrade websocket
caddy.0_reverse_proxy: "@ws {{upstreams 3001}}"
caddy.1_reverse_proxy: /ws/*
windmill_server:
...
labels:
caddy: "windmill.example.org"
caddy.tls.dns: "cloudflare <snip>"
caddy.tls.resolvers: 1.1.1.1
caddy.reverse_proxy: "{{upstreams http 8000}}"

lsp:
...
labels:
caddy: "windmill.example.org"
caddy.tls.dns: "cloudflare <snip>"
caddy.tls.resolvers: 1.1.1.1
caddy.@ws.0_header: Connection *Upgrade*
caddy.@ws.1_header: Upgrade websocket
caddy.0_reverse_proxy: "@ws {{upstreams 3001}}"
caddy.1_reverse_proxy: /ws/*
7 replies
WWindmill
Created by ZottelchenšŸ­ on 3/11/2024 in #help
Unable to use Assistants - (WARNING:tornado.access:404)
Oh no, wait a second, that can't be. If that was the case, I would not get the logs above as the requests would not reach the lsp container.
7 replies
WWindmill
Created by ZottelchenšŸ­ on 3/11/2024 in #help
Unable to use Assistants - (WARNING:tornado.access:404)
The way I did test that was opening a local windmill with the default values. Production (https://windmill.example.org/ws/) returns OK -> this does not work Testing (http://localhost/ws/) returns 404: Not Found -> this works Maybe instead of returning OK consider to return a page "Hey, it seems you've configured this wrong"?
7 replies
WWindmill
Created by ZottelchenšŸ­ on 3/11/2024 in #help
Unable to use Assistants - (WARNING:tornado.access:404)
Ah, seems like you are right, that seems to be the case. Will have to read up on how to fix thatšŸ˜…
7 replies