TOS 7 Upgrade: Vaultwarden (Docker 1.37.2) fails to start on F8 SSD / UI Log pagination issue/b]
Hello,
I have recently updated my NAS to TOS 7.0.1169, and right after the update, my Vaultwarden container completely broke and refuses to start.
Device details:
* NAS Model: TerraMaster F8 SSD
* Current TOS Version: 7.0.1169
* App Version: Vaultwarden 1.37.2 (Docker / Container Manager)
The Issues:
1. Container crash loop: The container fails to launch and completely drops the web interface connection. It seems the network ports are also completely unreachable.
2. Terrible UI Log Pagination: I initially thought there were no logs because the TOS 7 Container Manager displays them in a highly counter-intuitive way. Instead of showing the newest entries first, it appends them to the very end. I had to manually click through to page 850+ just to find the actual current errors.
Here are the latest log lines from the very last page of the container log viewer:
Before the TOS 7 update, everything worked flawlessly with the exact same volumes and network configurations.
Could you please advise on how to fix this startup failure? Also, please pass feedback to the UI team to fix the log sorting in the Container Manager, as forcing users to scroll through hundreds of pages to see fresh logs is unacceptable.
Thank you.
It is highly likely that the issue is related to the Caddy reverse proxy service, which I previously configured to handle the HTTPS connections and SSL certificates for Vaultwarden.
Hello,
I have recently updated my NAS to TOS 7.0.1169, and right after the update, my Vaultwarden container completely broke and refuses to start.
Device details:
* NAS Model: TerraMaster F8 SSD
* Current TOS Version: 7.0.1169
* App Version: Vaultwarden 1.37.2 (Docker / Container Manager)
The Issues:
1. Container crash loop: The container fails to launch and completely drops the web interface connection. It seems the network ports are also completely unreachable.
2. Terrible UI Log Pagination: I initially thought there were no logs because the TOS 7 Container Manager displays them in a highly counter-intuitive way. Instead of showing the newest entries first, it appends them to the very end. I had to manually click through to page 850+ just to find the actual current errors.
Here are the latest log lines from the very last page of the container log viewer:
Before the TOS 7 update, everything worked flawlessly with the exact same volumes and network configurations.
Could you please advise on how to fix this startup failure? Also, please pass feedback to the UI team to fix the log sorting in the Container Manager, as forcing users to scroll through hundreds of pages to see fresh logs is unacceptable.
Thank you.
I wanted to share my experience and the final solution for restoring a Vaultwarden (Docker) deployment after migrating to TOS 7 (7.0.1169) on a TerraMaster F8 SSD.
## Why it broke during the TOS 7 upgrade:
1. Port Collisions: The new TOS 7 system architecture highjacks previously popular custom container ports at the host network level (e.g., ports like 5443 or 6443 are now locked by internal system services via tcp6), forcing existing containers into an immediate Address already in use crash loop.
2. Strict TLS Engine Update: The updated container engine inside TOS 7 Container Manager no longer accepts an individual unified .pem file acting as both a certificate and a private key simultaneously via the ROCKET_TLS environment string. It silently drops connections with an ERR_INVALID_HTTP_RESPONSE error.
3. Case Sensitivity Shifts: The storage mount paths handler became completely unforgiving regarding Linux case sensitivity (e.g., passing /volume2/ instead of /Volume2/), resulting in Docker spinning up pristine empty directory nodes instead of reading the actual existing database.
------------------------------
## How we successfully fixed it:
If your Vaultwarden instance is stuck constantly restarting, use the TOS built-in Terminal app and execute the following sequential deployment patch:
Step 1: Extract separate certificate assets from the unified key
Navigate into your storage directory and split the certificate layer to satisfy the new engine constraints:
Step 3: Redeploy on a clean custom port with explicit Case-Sensitive volumes
Deploy using an unassigned host port (like 7443) and pass the newly separated TLS parameters to safely pull your existing database weights (e.g., db.sqlite3):
Step 4: Update TOS Firewall Rules
Go to Control Panel -> Security -> Firewall, add a custom inbound rule allowing TCP port 7443, and apply changes.
After completing these steps, the Vaultwarden vault becomes fully operational via https://[NAS_IP]:7443 without any data loss. Hopefully, the dev team will fix the default port overlapping and counter-intuitive log pagination in upcoming updates.
Please fix the german translation in Virtual Machine Manager. When uploading an image the german word for image is still image not Bild, because Bild is picture and not a iso image. Please fix, thank you
