We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi there,
I am new here and I am just trying to get started. I followed the instructions to self-host the project in docker, with only 2 changes:
The setup looks good until you try to set the new password. Then the frontend hangs while the backend logs this:
[windmill_server] | 2025-01-09T08:32:57.370817Z INFO request: windmill-api/src/tracing_init.rs:35: response latency=4 status=200 method=GET uri=/api/w/admins/apps/get/lite/g/all/setup_app traceId="9ea3cd2c-8fdc-485b-b135-87378395c09f" username="[email protected]" email="[email protected]" workspace_id="admins" [windmill_server] | 2025-01-09T08:32:57.371210Z INFO request: windmill-api/src/tracing_init.rs:35: response latency=5 status=200 method=GET uri=/api/w/admins/flows/list?starred_only=true traceId="a10124ee-0add-4343-a384-9b6683bfc2c7" username="[email protected]" email="[email protected]" workspace_id="admins" [windmill_server] | 2025-01-09T08:32:57.410472Z INFO request: windmill-api/src/tracing_init.rs:35: response latency=1 status=200 method=GET uri=/api/w/admins/apps_u/public_resource/f/app_themes/theme_0 traceId="d2c51f69-2c01-420e-beed-179c0f087e33" username="[email protected]" email="[email protected]" workspace_id="admins" [windmill_server] | 2025-01-09T08:32:57.421793Z INFO request: windmill-api/src/tracing_init.rs:35: response latency=4 status=200 method=GET uri=/api/w/admins/apps/list?starred_only=true traceId="6a44b257-4f1b-4960-a403-bbed939235b5" username="[email protected]" email="[email protected]" workspace_id="admins" [windmill_server] | 2025-01-09T08:32:57.692608Z INFO request: windmill-api/src/tracing_init.rs:35: response latency=3 status=200 method=GET uri=/api/w/admins/raw_apps/list?starred_only=true traceId="e2b02557-5ed5-40d5-9f24-c423bdd68feb" username="[email protected]" email="[email protected]" workspace_id="admins" [windmill_server] | 2025-01-09T08:32:57.716905Z INFO src/main.rs:668: received killpill for monitor job [windmill_server] | 2025-01-09T08:32:57.716922Z INFO windmill-common/src/lib.rs:140: shutdown monitor received killpill [windmill_server] | 2025-01-09T08:32:57.716924Z INFO windmill-api/src/lib.rs:497: Graceful shutdown of server [windmill_server] | 2025-01-09T08:32:57.716944Z INFO windmill-common/src/lib.rs:152: signal received, starting graceful shutdown [windmill_server] | 2025-01-09T08:32:57.716953Z INFO src/main.rs:649: Starting phase 2 of shutdown [windmill_server] | 2025-01-09T08:32:57.716963Z INFO src/main.rs:651: Phase 2 of shutdown completed [windmill_server] | 2025-01-09T08:32:57.716972Z INFO src/main.rs:875: Monitor exited [windmill_server] | 2025-01-09T08:32:57.718402Z INFO src/monitor.rs:504: Sending current log file to object store [windmill_server] | 2025-01-09T08:32:57.764650Z INFO src/main.rs:909: Exiting connection pool [windmill_server] | 2025-01-09T08:32:57.772707Z INFO src/main.rs:912: Database connection pool closed
Run the instructions to self-host the project in docker using Podman until you set the new admin password.
No errors.
No response
Related to #4311.
The text was updated successfully, but these errors were encountered:
rubenfiszel
No branches or pull requests
Describe the bug
Hi there,
I am new here and I am just trying to get started. I followed the instructions to self-host the project in docker, with only 2 changes:
The setup looks good until you try to set the new password.
Then the frontend hangs while the backend logs this:
To reproduce
Run the instructions to self-host the project in docker using Podman until you set the new admin password.
Expected behavior
No errors.
Screenshots
No response
Browser information
No response
Application version
No response
Additional Context
Related to #4311.
The text was updated successfully, but these errors were encountered: