FirstHonourF
Convex Community5mo ago
13 replies
FirstHonour

self host getting stuck

Hello
i am self hosting convex using docker. it was working perfectly for months. then suddenly one day after restarting my pc (windows 11) running the backend no longer works.

the commands:

$env:PATH += ";C:\Program Files\Git\bin"
$env:AWS_LC_SYS_PREBUILT_NASM = "1"
just run-local-backend


the log

cargo run -p local_backend --bin convex-local-backend -- "$@"
warning: unused variable: `hash`
  --> crates\fivetran_common\build.rs:36:9
warning: unused variable: `hash`
  --> crates\fivetran_common\build.rs:36:9
   |
36 |     let hash = hasher.finish();
36 |     let hash = hasher.finish();
   |         ^^^^ help: if this is intentional, prefix it with an underscore: `_hash`
   |
   = note: `#[warn(unused_variables)]` on by default

warning: constant `FILE_HASH` is never used
  --> crates\fivetran_common\build.rs:22:7
   |
22 | const FILE_HASH: u64 = 1411440539;
   |       ^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: `convex_fivetran_common` (build script) generated 2 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.61s
     Running `target\debug\convex-local-backend.exe`
2025-09-10T06:07:54.645978Z  INFO convex_local_backend: Starting a Convex backend
2025-09-10T06:07:54.646342Z  INFO convex_local_backend: The self-host Convex backend will periodically communicate with a remote beacon server. This is to help Convex understand and improve the product. You can disable this telemetry by setting the --disable-beacon flag or the DISABLE_BEACON environment variable if you are self-hosting using the Docker image.
2025-09-10T06:07:54.646650Z  INFO convex_local_backend: Sentry is not enabled.
2025-09-10T06:07:54.650565Z  INFO db_connection: Connected to SQLite at convex_local_backend.sqlite3
2025-09-10T06:07:54.651242Z  INFO search::searcher::searcher: Searchlight starting, local_storage_path: C:\Users\nopel\AppData\Local\Temp\.tmpjbbhsY max_size: 500.0 MiB
Was this page helpful?