Piping MYSQL error when restoring Vaultwarden backup

[humptydumpty]

I saw this thread and I increased the VW app RAM to 8GB and the MySQL service to 15GB and it didn't help. Suggestions?

An error occurred during the import operation: Addons Error: Error piping file /home/yellowtent/appsdata/xxxxxxxx-xxxx-xxxxxxxxxxxxxxx-xxxxxxxxxxxxx/mysqldump to request http://172.18.30.1:3000/databases/xxxxxxxxxxxxxxx/restore?access_token=60xxxxxxxxxx.... (redacted)

MySQL log:

2024-07-12T19:57:31.000Z Waiting for MySQL to come up
2024-07-12T19:57:31.000Z Waiting with password
2024-07-12T19:57:32.000Z mysqladmin: [Warning] Using a password on the command line interface can be insecure.
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,966 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,966 INFO Included extra file "/etc/supervisor/conf.d/mysql-service.conf" during parsing
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,966 INFO Included extra file "/etc/supervisor/conf.d/mysql.conf" during parsing
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,970 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,970 INFO RPC interface 'supervisor' initialized
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,971 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,971 INFO RPC interface 'supervisor' initialized
2024-07-12T19:57:33.000Z 2024-07-12 19:57:33,971 INFO supervisord started with pid 1
2024-07-12T19:57:33.000Z Starting supervisor
2024-07-12T19:57:34.000Z 2024-07-12 19:57:34,975 INFO spawned: 'mysql' with pid 65
2024-07-12T19:57:34.000Z 2024-07-12 19:57:34,978 INFO reaped unknown pid 12 (exit status 0)
2024-07-12T19:57:34.000Z 2024-07-12 19:57:34,978 INFO spawned: 'mysql-service' with pid 66
2024-07-12T19:57:35.000Z MySQL service endpoint listening on http://:::3000
2024-07-12T19:57:36.000Z 2024-07-12 19:57:36,130 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-12T19:57:36.000Z 2024-07-12 19:57:36,130 INFO success: mysql-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-12T19:57:37.000Z [GET] /healthcheck
2024-07-12T19:58:05.000Z [POST] /databases
2024-07-12T19:58:05.000Z add: adding database 4bda4510e043716f

[humptydumpty]

Yep, as usual. It's user error. I was using the box config backup. I just had to adjust the backup path to point to the app. I figured out the correct path by logging into my Backblaze dashboard, browsed through the bucket (by date) and the file "name" is your path. Copy/paste into the import box along with the box settings and voila!

[humptydumpty]

Oh wait. I think I'm uploading the server backup file instead of the app configuration. BRB!

[humptydumpty]

Yep, as usual. It's user error. I was using the box config backup. I just had to adjust the backup path to point to the app. I figured out the correct path by logging into my Backblaze dashboard, browsed through the bucket (by date) and the file "name" is your path. Copy/paste into the import box along with the box settings and voila!