Vaultwarden (Legacy) running but health check fails after StartOS update

General
1

I am running Vaultwarden (Legacy) 1.36.0-1 on StartOS. I recently updated StartOS.

Vaultwarden shows “Running,” but the Web UI health check repeatedly reports:

Error while fetching URL: http://vaultwarden.embassy:80/alive

The logs repeatedly show:

Error: TypeError: fetch failed

Bitwarden clients can display my existing vault, but when I try to save a new password I get “Error in fetching” or a timeout.

Clicking Vaultwarden → Open UI in StartOS also fails. Firefox gives:

PR_END_OF_FILE_ERROR

I have already:

  • Restarted Vaultwarden

  • Rebuilt the Vaultwarden service

  • Confirmed the problem persists afterward

I have not uninstalled Vaultwarden, reset the configuration, or changed the Admin Token because I don’t want to risk losing my vault data.

What is the safest way to repair the service while preserving my existing Vaultwarden database?

2

You’re already taking risks by ignoring the guide and going your own way. Why are you trying to start up Legacy services on StartOS v040?

3

I understand now. The StartOS 0.4 update was completed before I realized the Legacy services needed to be updated on 0.3.5.1 first. I have stopped the Legacy services and have not uninstalled or replaced anything.

My important data includes a Core Lightning node with existing channels and my Vaultwarden database. What is the safest supported recovery path from here: can these Legacy services be migrated in place on 0.4, or should I roll back to 0.3.5.1, update all services there, and then repeat the 0.4 migration?

I do have Bitcoin Knots Legacy #knots:29.3.1:0; the 0.4 marketplace offers Bitcoin Knots (pre-RDTS) #knotspredrts:29.3:17. I have not installed it. Please advise before I modify anything.

4

Following the update guide is highly recommended:

But in your specific case, look at your 040 server UI and see if there are any updates available for your sevices. All of them should of been updated before starting them anyways.

5

I checked the 0.4 UI. Most services have now migrated and no longer say Legacy, but Bitcoin Knots and BTCPay Server still do. My installed Bitcoin Knots is #knots:29.3.1:0. When I search the 0.4 Marketplace, the only Knots offered is Bitcoin Knots (pre-RDTS) #knotspredrts:29.3:17. There is no update button on the Legacy Knots service page.

Should I install/switch to Bitcoin Knots (pre-RDTS) from the Marketplace to migrate the existing Legacy Knots service/data, or is there another update path I should use?

6

Knots is a special case, it’s on the failed (as yet) BIP-110 chain rather on the chain most of the world is following. So you should switch to pre-RDTS yes.

BTCPay Server simply needs to be updated… but… I can see why that would be a problem, caused by the recent rush to release a fix for the bug. If you’re actually using it, then hand tight until we make an update available. If not, then you can uninstall it and install it again later.

7

thank you for your help. All the best.

8

You can update BTCPay now.