tauri: WSL Unable to init server
yarn tauri dev fails when trying to start.
To Reproduce
- Follow steps for Linux setup and install Tauri node package globally
- Also enable Windows loopback (I did this just in case because I’m on WSL 2)
- Create a new project (I’m using Svelte) and add node package locally
- Edit
tauri.conf.json
"build": {
"distDir": "../public",
"devPath": "http://127.0.0.1:5000"
},
- Run
yarn devto start up Svelte dev server - Run
yarn tauri devin a different terminal tab
Expected behavior I expect the Tauri dev environment to start up.
Platform and Versions:
OS: Linux(4.19.84-microsoft-standard) - linux/x64 Node: 13.6.0 NPM: 6.13.4 Yarn: 1.21.1 Rustc: 1.42.0-nightly
Additional context Note that this is my first time trying out Tauri, but as a JS/Rust user I’m very excited!
Stack Trace
➜ tauri-counter RUST_BACKTRACE=1 yarn tauri dev
yarn run v1.21.1
warning package.json: No license field
$ /home/googlemac/Code/rust/tauri-counter/node_modules/.bin/tauri dev
[tauri]: running dev
app:spawn Running "cargo run --features dev-server" +0ms
warning: unused manifest key: package.author
Compiling app v0.1.0 (/home/googlemac/Code/rust/tauri-counter/src-tauri)
Compiling tauri v0.3.2
Finished dev [unoptimized + debuginfo] target(s) in 2.30s
Running `target/debug/app`
Unable to init server: Could not connect: Connection refused
thread 'main' panicked at 'Failed to build webview: Initialization', /home/googlemac/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-0.3.2/src/app.rs:14:5
stack backtrace:
0: backtrace::backtrace::libunwind::trace
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
1: backtrace::backtrace::trace_unsynchronized
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
2: std::sys_common::backtrace::_print_fmt
at src/libstd/sys_common/backtrace.rs:77
3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
at src/libstd/sys_common/backtrace.rs:59
4: core::fmt::write
at src/libcore/fmt/mod.rs:1052
5: std::io::Write::write_fmt
at src/libstd/io/mod.rs:1428
6: std::sys_common::backtrace::_print
at src/libstd/sys_common/backtrace.rs:62
7: std::sys_common::backtrace::print
at src/libstd/sys_common/backtrace.rs:49
8: std::panicking::default_hook::{{closure}}
at src/libstd/panicking.rs:204
9: std::panicking::default_hook
at src/libstd/panicking.rs:224
10: std::panicking::rust_panic_with_hook
at src/libstd/panicking.rs:470
11: rust_begin_unwind
at src/libstd/panicking.rs:378
12: core::panicking::panic_fmt
at src/libcore/panicking.rs:85
13: core::option::expect_none_failed
at src/libcore/option.rs:1199
14: core::result::Result<T,E>::expect
at /rustc/8417d68de5e063426ab6bb7f383df6117d1beeed/src/libcore/result.rs:991
15: tauri::app::App::run
at /home/googlemac/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-0.3.2/src/app.rs:14
16: app::main
at src/main.rs:13
17: std::rt::lang_start::{{closure}}
at /rustc/8417d68de5e063426ab6bb7f383df6117d1beeed/src/libstd/rt.rs:67
18: std::rt::lang_start_internal::{{closure}}
at src/libstd/rt.rs:52
19: std::panicking::try::do_call
at src/libstd/panicking.rs:303
20: __rust_maybe_catch_panic
at src/libpanic_unwind/lib.rs:86
21: std::panicking::try
at src/libstd/panicking.rs:281
22: std::panic::catch_unwind
at src/libstd/panic.rs:394
23: std::rt::lang_start_internal
at src/libstd/rt.rs:51
24: std::rt::lang_start
at /rustc/8417d68de5e063426ab6bb7f383df6117d1beeed/src/libstd/rt.rs:67
25: main
26: __libc_start_main
27: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
app:spawn Command "cargo" failed with exit code: 101 +0ms
app:tauri (template) ⚠️ [FAIL] Cargo CLI has failed +0ms
app:tauri Shutting down tauri process... +1ms
error Command failed with exit code 1.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (10 by maintainers)
@nothingismagick The line above should be used in the docs instead (the current one is expecting awk to be a filename). I just got everything working great today!
@tensor-programming Thanks for the concise yet good details. I think the WSL2 command should be
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0instead.@Laegel - good tips above from Tensor for the DOCS