starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Infinite loading wheel when opening restored attachment #1644

New Issue
Closed
opened 2026-02-05 01:24:11 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-05 01:24:11 +03:00
Owner
Copy Link

Originally created by @louisfgr on GitHub (Jul 17, 2023).

Subject of the issue

I restored my SQLite DB and my attachments folder into a new Vaultwarden instance. This worked fine for the DB but now my attachments won't load.

Deployment environment

  • vaultwarden version:

  • Install method:

  • Clients used:

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @louisfgr on GitHub (Jul 17, 2023). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> I restored my SQLite DB and my attachments folder into a new Vaultwarden instance. This worked fine for the DB but now my attachments won't load. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
OVERLORD commented 2026-02-05 01:24:18 +03:00
Author
Owner
Copy Link

@louisfgr commented on GitHub (Jul 17, 2023):

Sorry accidentally pressed enter to early :)
Pls ignore.

ps. feel free to delete. Seems like I don't have the rights for that.

@louisfgr commented on GitHub (Jul 17, 2023): Sorry accidentally pressed enter to early :) Pls ignore. ps. feel free to delete. Seems like I don't have the rights for that.
OVERLORD commented 2026-02-05 01:24:20 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jul 17, 2023):

Pressed enter to early on the sense, you fixed it? Because ot probably is your Domain setting 😉

@BlackDex commented on GitHub (Jul 17, 2023): Pressed enter to early on the sense, you fixed it? Because ot probably is your Domain setting 😉
OVERLORD commented 2026-02-05 01:24:23 +03:00
Author
Owner
Copy Link

@louisfgr commented on GitHub (Jul 17, 2023):

I decided to do some more testing before opening an issue. I have tested your hint about the domain settings, but that could not fix my problem. I will do some more testing and open a new issue or discussion with all the information I could get. Thanks ;)

@louisfgr commented on GitHub (Jul 17, 2023): I decided to do some more testing before opening an issue. I have tested your hint about the domain settings, but that could not fix my problem. I will do some more testing and open a new issue or discussion with all the information I could get. Thanks ;)
OVERLORD commented 2026-02-05 01:24:25 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jul 17, 2023):

I suggest to check /admin/diagnostics and see if there are any issues there.

@BlackDex commented on GitHub (Jul 17, 2023): I suggest to check `/admin/diagnostics` and see if there are any issues there.
OVERLORD commented 2026-02-05 01:24:30 +03:00
Author
Owner
Copy Link

@louisfgr commented on GitHub (Jul 17, 2023):

I think I fixed it. Here is what I did:

Exported DB and attachments of bitwarden.xxx.tld
Restored to bitwardentest.xxx.tld -> can't open attachments
Set Domain URL of test environment to bitwarden.xxx.tld -> can't open attachments
Docker restart -> can't open attachments
Set Domain URL of test environment back to bitwardentest.xxx.tld -> suddenly can open attachments
Docker restart -> still can open attachments

Seems like changing the Domain URL to the on where the backup originates from and then again back to the actual one changes something internaly.

Again thanks for your hint. Wouldn't have found it out with out that :)

@louisfgr commented on GitHub (Jul 17, 2023): I think I fixed it. Here is what I did: Exported DB and attachments of bitwarden.xxx.tld Restored to bitwardentest.xxx.tld -> can't open attachments Set Domain URL of test environment to bitwarden.xxx.tld -> can't open attachments Docker restart -> can't open attachments Set Domain URL of test environment back to bitwardentest.xxx.tld -> suddenly can open attachments Docker restart -> still can open attachments Seems like changing the Domain URL to the on where the backup originates from and then again back to the actual one changes something internaly. Again thanks for your hint. Wouldn't have found it out with out that :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1644
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?