Caddy and other issues when deploying with source code #5252
Comments
|
If you're using normal caddy you should remove the layer4 part. Apart from that it should work correctly. |
Thank you for your answer, but when I delete the layer4 part and execute directly, I still get an error. and I get the following error: |
I tried again, deleted the layer4 part in the caddyfile file, started it, and then visited http://localhost/ in the browser, and the error was as follows: |
|
As you're not using the docker compose, the caddyfile does not proxy to the correct endpoints. |
Thank you, I made the changes according to your suggestion, the content of caddyfile is as follows, and there is no problem in executing sudo caddy run --config Caddyfile, but when I visit http://localhost, I still get an error: |
|
you need to build the frontend with NODE_OPTIONS="--max-old-space-size=8192" npm run build |
|
|
now run cargo run and make sure to have the right feature flags (including static_frontend) and it should work |
This is the log of my cargo execution in the backend directory. It looks fine, but when I visit http://localhost, I get a 404 error. |
|
This is always the error. |
What does 'right feature flags' refer to |
cargo run --features embedding,parquet,openidconnect,jemalloc,deno_core,license,http_trigger,zip,oauth2,dind,php,mysql,mssql,bigquery,oracledb,postgres_trigger,websocket,python,smtp,csharp,static_frontend,rust |
Thank you very much, with your help I successfully started windmill, but when I wanted to create an account to override the default super administrator account, a problem occurred. The following is the log of cargo. I don't know what the permissions here refer to.
|
I carefully checked the cargo run log and found three errors. I did not see any information about uv in the readme document. I installed uv according to the prompts, but the error still exists. |
When I log in with the default account, I cannot create a new account in the instance. It prompts me that this is not a feature of the open source version. I remember that I can create one when I use docker deployment. |
|
@HugoCasa I really need your help, do you have time? |
I tried to deploy again, and the error became as follows： |
|
windmill depends on multiple runtimes that must be installed on the system, e.g. deno, uv, bun, etc.. and you need to specify the appropriate paths in env |
OK, thank you. But I am confused why when I first logged in, I created an account to overwrite the default account, but the backend log indicated that the account already existed? And, after I logged in with the default account, I could not create a new account in the instance, and it prompted me that this was a non-open source version feature. |
I have solved the runtime problems such as uv, but I can't create a user |
|
because this part of the code is closed source |
I just want to know how to set the number of workers after the source code is deployed, just like modifying windmill_worker in the docker-compose file when using docker deployment |
Does this mean I can't create new accounts in the instance unless I become an ee user? |
|
Thank you, but if I deploy using source code, do I need to be an EE to create a user in the instance? |
Is there a problem with caddyfile when using source code self-hosting deployment? I modified it to the following to execute "sudo caddy run --config Caddyfile" normally. My caddy version is 2.9
{$BASE_URL}:80 {
#listen {$ADDRESS}
reverse_proxy /ws/* http://lsp:3001
# reverse_proxy /ws_mp/* http://multiplayer:3002
# reverse_proxy /api/srch/* http://windmill_indexer:8001
reverse_proxy /* http://windmill_server:8000
# tls /certs/cert.pem /certs/key.pem
}
After all preparations are ready, I visited http://localhost/ in the browser and there was no response, and an error was reported in the terminal。
2025-02-10T07:29:04.253180Z ERROR request: windmill-api/src/tracing_init.rs:37: response latency=0 status=404 method=GET uri=/ traceId="b934ff26-0c5b-4b83-9860-4da8a6b45b03"
The text was updated successfully, but these errors were encountered: