Zottelchen🍭 Posts - Answer Overflow

Zottelchen🍭

Explore posts from servers

•Created by Zottelchen🍭 on 9/16/2024 in #🛟bazzite-help

Secure Boot does not work

I am trying to install Bazzite on a Lenovo ThinkPad L380. I did the following: 0. Secure Boot is initially on. 1. I installed Bazzite from Ventoy. Automatic Storage, but encrypted using the whole disk. 2. Bazzite did not boot - deactived Secure Boot. 3. Bazzite boots, initial setup & following Method B of https://docs.bazzite.gg/General/Installation_Guide/secure_boot/ 4. Reboot & active Secure Boot. 5. Bazzite does not start anymore. 6. Reboot & disable Secure Boot. 7. Bazzite does still not start. The error:

Failed to open \EFI\BOOT\mmx64.efi - Not found
Failed to load image : Not Found
Failed to start MokManager : Not Found
Something has gone serioujjsly wrong: import_mok_state() failed: Not found

Failed to open \EFI\BOOT\mmx64.efi - Not found
Failed to load image : Not Found
Failed to start MokManager : Not Found
Something has gone serioujjsly wrong: import_mok_state() failed: Not found

What went wrong and how do I fix that?

3 replies

WWindmill

•Created by Zottelchen🍭 on 3/11/2024 in #help

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?

7 replies

Gaming

Programming