# Rocket.rs dev seems broken, vaultwarden fails to launch

**URL:** <https://vaultwarden.discourse.group/t/rocket-rs-dev-seems-broken-vaultwarden-fails-to-launch/1192>\
**Category:** Help\
**Created:** [October 13, 2021, 8:37am UTC](https://vaultwarden.discourse.group/t/rocket-rs-dev-seems-broken-vaultwarden-fails-to-launch/1192 "2021-10-13T08:37:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jens](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@jens](https://vaultwarden.discourse.group/u/jens)\
**Post date:** [October 13, 2021, 8:37am UTC](https://vaultwarden.discourse.group/t/rocket-rs-dev-seems-broken-vaultwarden-fails-to-launch/1192/1 "2021-10-13T08:37:46Z")

</div>

yesterday I built vaultwarden from source and got this error:

[2021-10-13 08:26:50.348][panic][ERROR] thread ‘main’ panicked at ‘Error: expected token ‘/’ but found ‘b’ at index 0’: /opt/bitwarden\_rs/.cargo/git/checkouts/rocket-8bf16d9ca7e90bdc/263e39b/core/lib/src/rocket.rs:528  
0: vaultwarden::init\_logging::{{closure}}  
1: std::panicking::rust\_panic\_with\_hook  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:626:17  
2: std::panicking::begin\_panic\_handler::{{closure}}  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:519:13  
3: std::sys\_common::backtrace::\_\_rust\_end\_short\_backtrace  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/sys\_common/backtrace.rs:141:18  
4: rust\_begin\_unwind  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:515:5  
5: std::panicking::begin\_panic\_fmt  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:457:5  
6: rocket:🚀🚀:mount::{{closure}}  
7: rocket:🚀🚀:mount  
8: vaultwarden::main  
9: std::sys\_common::backtrace::\_\_rust\_begin\_short\_backtrace  
10: std::rt::lang\_start::{{closure}}  
11: core::ops::function::impls::\<impl core::ops::function::FnOnce for &F\>::call\_once  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/core/src/ops/function.rs:259:13  
std::panicking::try::do\_call  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:401:40  
std::panicking::try  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:365:19  
std::panic::catch\_unwind  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panic.rs:434:14  
std::rt::lang\_start\_internal::{{closure}}  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/rt.rs:45:48  
std::panicking::try::do\_call  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:401:40  
std::panicking::try  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panicking.rs:365:19  
std::panic::catch\_unwind  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/panic.rs:434:14  
std::rt::lang\_start\_internal  
at /rustc/5a7834050f3a0ebcd117b4ddf0bc1e8459594309/library/std/src/rt.rs:45:20  
12: main  
13: \_\_libc\_start\_main  
14: \_start

 

I believe this is because rocket.rs=0.5.0-dev is broken, would it not make more sense to specify =0.5.0-rc1 in the **Cargo.toml** file to make sure builds are working?

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [October 13, 2021, 8:56pm UTC](https://vaultwarden.discourse.group/t/rocket-rs-dev-seems-broken-vaultwarden-fails-to-launch/1192/2 "2021-10-13T20:56:00Z")

</div>

We use a very specific git commit checksum, so it can’t be broken because of that. At least, not because of code changes regarding Rocket.

If you use the master branch of Vaultwarden as-is it compiles fine for me. It could be some external libraries, but not sure.

---

<div class="post-metadata">

**Author:** ![jens](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@jens](https://vaultwarden.discourse.group/u/jens)\
**Post date:** [October 14, 2021, 7:48am UTC](https://vaultwarden.discourse.group/t/rocket-rs-dev-seems-broken-vaultwarden-fails-to-launch/1192/3 "2021-10-14T07:48:21Z")

</div>

Hi,

Yes, I just noticed lower in the Cargo.toml file there is a patch that pins the commit of rocket,  
This was indeed a configuration issue, a bit sad to see a simple forgotten ‘/’ in a configuration file result in a full on panic, but things worked after fixing my configuration.