[GH-ISSUE #2211] Vault export and re-import not working #1190

New issue

Closed

opened 2026-03-03 02:07:02 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:07:02 +03:00

Owner

Originally created by @A30BL on GitHub (Jan 7, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2211

Subject of the issue

Hello,
I am currently using vaultwarden version 2.25.0 on two different machines. The first installation was intended as a test version, but was then used for a longer time. Now the vault of the first installation should be transferred to a newer computer, which also runs version 2.25.0 with an empty vault.
So I tried to export the vault from computer 1 in csv format and also in json format. The export completed without any errors.
Then I tried to import the data on computer 2 as "Bitwarden (json)" and "Bitwarden (csv)" and got the error message in each case:

Import Error
There was a problem with the data you tried to import. Please resolve the errors listed below in your source file and try again.
HTML code content:

        <html lang="en">
        <head>
            <meta charset="utf-8">
            <title>400 Bad Request</title>
        </head>
        <body align="center">
            <div role="main" align="center">
                <h1>400: Bad Request</h1>
                <p>The request could not be understood by the server due
            to malformed syntax.</p>
                <hr />
            </div>
            <div role="contentinfo" align="center">
                <small>Rocket</small>
            </div>
        </body>
        </html>

Deployment environment

vaultwarden version: 2.25.0

Install method: Vaultwarden software package that comes with Dietpi
Clients used: web vault
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:

Steps to reproduce

Dietpi installation with software package "183 vaultwarden"

Expected behaviour

Vaultwarden imports vault data

Actual behaviour

Vaultwarden does not import own vault data

Troubleshooting data

Originally created by @A30BL on GitHub (Jan 7, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2211   ### Subject of the issue Hello, I am currently using vaultwarden version 2.25.0 on two different machines. The first installation was intended as a test version, but was then used for a longer time. Now the vault of the first installation should be transferred to a newer computer, which also runs version 2.25.0 with an empty vault. So I tried to export the vault from computer 1 in csv format and also in json format. The export completed without any errors. Then I tried to import the data on computer 2 as "Bitwarden (json)" and "Bitwarden (csv)" and got the error message in each case: Import Error There was a problem with the data you tried to import. Please resolve the errors listed below in your source file and try again. HTML code content: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>400 Bad Request</title> </head> <body align="center"> <div role="main" align="center"> <h1>400: Bad Request</h1> <p>The request could not be understood by the server due to malformed syntax.</p> <hr /> </div> <div role="contentinfo" align="center"> <small>Rocket</small> </div> </body> </html> ### Deployment environment     * vaultwarden version: 2.25.0  * Install method: Vaultwarden software package that comes with Dietpi * Clients used: web vault * Reverse proxy and version:  * MySQL/MariaDB or PostgreSQL version:  * Other relevant details: ### Steps to reproduce Dietpi installation with software package "183 vaultwarden" ### Expected behaviour Vaultwarden imports vault data ### Actual behaviour Vaultwarden does not import own vault data ### Troubleshooting data

kerem closed this issue

2026-03-03 02:07:03 +03:00

kerem commented

2026-03-03 02:07:03 +03:00

Author

Owner

@BlackDex commented on GitHub (Jan 7, 2022):

Could you please post the /admin/diagnostics Support String?
Because looking at the DietPi install script it is still using web-vault v2.21.1, also v2.25.0 is not the version number of Vaultwarden it self, that is the web-vault version.

@BlackDex commented on GitHub (Jan 7, 2022): Could you please post the /admin/diagnostics `Support String`? Because looking at the DietPi install script it is still using web-vault v2.21.1, also v2.25.0 is not the version number of Vaultwarden it self, that is the web-vault version.

kerem commented

2026-03-03 02:07:03 +03:00

Author

Owner

@BlackDex commented on GitHub (Jan 7, 2022):

Also, if all is empty, and you have no other users besides your self, you could also just transfer the database it self.

@BlackDex commented on GitHub (Jan 7, 2022): Also, if all is empty, and you have no other users besides your self, you could also just transfer the database it self.

kerem commented

2026-03-03 02:07:03 +03:00

Author

Owner

@BlackDex commented on GitHub (Jan 12, 2022):

I am not able to reproduce this at all. It could also be that the reverse proxy you are using limits the body size and then pushes a partial body to Vaultwarden which then of course is invalid.

I would suggest to checkout your reverse proxy logs and check the Developer Tools (F12) within the browser to see if you see something strange there.

If you still find this is a Vaultwarden issue, and you can provide more useful information please feel free to re-open this ticket, i will close it for now.

@BlackDex commented on GitHub (Jan 12, 2022): I am not able to reproduce this at all. It could also be that the reverse proxy you are using limits the body size and then pushes a partial body to Vaultwarden which then of course is invalid. I would suggest to checkout your reverse proxy logs and check the Developer Tools (F12) within the browser to see if you see something strange there. If you still find this is a Vaultwarden issue, and you can provide more useful information please feel free to re-open this ticket, i will close it for now.