WindmillWWindmill
Powered by
Zottelchen🍭Z
Windmill•2y ago•
6 replies
Zottelchen🍭

Unable to use Assistants - (WARNING:tornado.access:404)

I seem to be unable to use the assistants. When I click the reload button nothing happens in the frontend and in the docker logs it shows this:
lsp-1                     | WARNING:tornado.access:404 GET /pyright (172.19.0.5) 1.48ms
lsp-1                     | WARNING:tornado.access:404 GET /ruff (172.19.0.5) 0.45ms
lsp-1                     | WARNING:tornado.access:404 GET /diagnostic (172.19.0.5) 0.45ms
lsp-1                     | WARNING:tornado.access:404 GET /pyright (172.19.0.5) 1.48ms
lsp-1                     | WARNING:tornado.access:404 GET /ruff (172.19.0.5) 0.45ms
lsp-1                     | WARNING:tornado.access:404 GET /diagnostic (172.19.0.5) 0.45ms

I am using caddy, but through https://github.com/lucaslorentz/caddy-docker-proxy. The labels are:
windmill_server:
    ...
    labels:
      caddy: "windmill.example.org"
      caddy.tls.dns: "cloudflare <snip>"
      caddy.tls.resolvers: 1.1.1.1
      caddy.handle_path: /*
      caddy.handle_path.0_reverse_proxy: "{{upstreams 8000}}"

lsp:
    ...
    labels:
      caddy: "windmill.example.org"
      caddy.tls.dns: "cloudflare <snip>"
      caddy.tls.resolvers: 1.1.1.1
      caddy.handle_path: /ws/*
      caddy.handle_path.0_reverse_proxy: "{{upstreams 3001}}"
windmill_server:
    ...
    labels:
      caddy: "windmill.example.org"
      caddy.tls.dns: "cloudflare <snip>"
      caddy.tls.resolvers: 1.1.1.1
      caddy.handle_path: /*
      caddy.handle_path.0_reverse_proxy: "{{upstreams 8000}}"

lsp:
    ...
    labels:
      caddy: "windmill.example.org"
      caddy.tls.dns: "cloudflare <snip>"
      caddy.tls.resolvers: 1.1.1.1
      caddy.handle_path: /ws/*
      caddy.handle_path.0_reverse_proxy: "{{upstreams 3001}}"


which result in the Caddyfile:
windmill.example.org {
    handle_path /* {
        reverse_proxy 172.19.0.13:8000
    }
    handle_path /ws/* {
        reverse_proxy 172.19.0.12:3001
    }
    tls {
        dns cloudflare <snip>
        resolvers 1.1.1.1
    }
}
windmill.example.org {
    handle_path /* {
        reverse_proxy 172.19.0.13:8000
    }
    handle_path /ws/* {
        reverse_proxy 172.19.0.12:3001
    }
    tls {
        dns cloudflare <snip>
        resolvers 1.1.1.1
    }
}


So to my knowledge this should work fine. What am I missing?
WindmillJoin
3,362Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements
Recent Announcements
henri-c

Weekly kenote to tell you about our latest updates https://discord.com/channels/930051556043276338/1278977038430240813 https://youtube.com/live/2dGd9TdT8xs?feature=share

henri-c · 4d ago

Pyra

### HTTP tracing (EE) Capture HTTP requests made by job scripts as observability spans Features: - View HTTP request traces (method, URL, status, timing) in the job details UI - Auto-instrumentation for Native TypeScript, MITM proxy for other languages - Integrates with external OpenTelemetry collectors changelog: https://www.windmill.dev/changelog/http-tracing docs: https://www.windmill.dev/docs/advanced/instance_settings#http-tracing Additionally jobs memory metrics are now fully OSS!

Pyra · 2w ago

henri-c

First keynote of the year here https://discord.com/channels/930051556043276338/1278977038430240813 🙂

henri-c · 4w ago

Similar Threads

Unable to access results value
TreyTTrey / help
5mo ago
unable to use DynSelect in scheduler
TreyTTrey / help
3mo ago
Unable to use new Spotify OAuth provider
minchyMminchy / help
16mo ago
404 resource not found
KeloraKKelora / help
2y ago