[GH-ISSUE #1818] Attachment size limit displayed to user does not match the limit imposed in the Vaultwarden admin panel #34021

New Issue

Closed

opened 2026-07-13 18:41:16 -05:00 by GiteaMirror · 2 comments

GiteaMirror commented 2026-07-13 18:41:16 -05:00

Owner

Copy Link

Copy Source

Originally created by @ghost on GitHub (Jul 2, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1818

This upload will fail and will return the shown error due to the size restriction set by the admin using the admin panel. It is set to 50MB in this example.

Originally created by @ghost on GitHub (Jul 2, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1818  This upload will fail and will return the shown error due to the size restriction set by the admin using the admin panel. It is set to 50MB in this example.

GiteaMirror added the enhancementlow priority labels 2026-07-13 18:41:19 -05:00

GiteaMirror closed this issue 2026-07-13 18:41:20 -05:00

GiteaMirror commented 2026-07-13 18:41:21 -05:00

Author

Owner

Copy Link

Copy Source

@BlackDex commented on GitHub (Jul 2, 2021):

Those are hard-coded limits in the web-vault, and not something we can change on-the-fly, per server.
What we can do is change the error message to indicate what the limit is so that it will be more clear.

<!-- gh-comment-id:873005109 --> @BlackDex commented on GitHub (Jul 2, 2021): Those are hard-coded limits in the web-vault, and not something we can change on-the-fly, per server. What we can do is change the error message to indicate what the limit is so that it will be more clear.

GiteaMirror commented 2026-07-13 18:41:21 -05:00

Author

Owner

Copy Link

Copy Source

@BlackDex commented on GitHub (Jul 5, 2021):

I have checked the code a bit better, and the size limit you can configure isn't per attachment, but as a total amount of storage. The wording is a bit off, so i think we should change that.

<!-- gh-comment-id:874257281 --> @BlackDex commented on GitHub (Jul 5, 2021): I have checked the code a bit better, and the size limit you can configure isn't per attachment, but as a total amount of storage. The wording is a bit off, so i think we should change that.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

v2-registration

revert-7033-patch-1

cached-config-operations

test_dylint

1.37.2

1.37.1

1.37.0

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No labels enhancement low priority

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#34021