[GH-ISSUE #4787] Cannot generate the QR Code in the web page's security settings with the Authenticator app provider #1982

New issue

Closed

opened 2026-03-03 02:14:04 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:14:04 +03:00

Owner

Originally created by @syneart on GitHub (Jul 27, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4787

Subject of the issue

In the web page's security settings, the Provider settings for the Authenticator app in the Two-step login cannot generate a QR Code.

Deployment environment

vaultwarden version: v1.31.0

Install method: Docker - vaultwarden/server:latest

MySQL/MariaDB or PostgreSQL version: MariaDB

Other relevant details:

There is an error when generating the QR code.
Screenshot 2024-07-27 at 22 35 36

Expected behaviour

A QR code needs to be generated.

Originally created by @syneart on GitHub (Jul 27, 2024). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4787 ## Subject of the issue ## In the web page's security settings, the Provider settings for the Authenticator app in the Two-step login cannot generate a QR Code. ## Deployment environment ## vaultwarden version: v1.31.0 Install method: Docker - vaultwarden/server:latest MySQL/MariaDB or PostgreSQL version: MariaDB ## Other relevant details: ## There is an error when generating the QR code. <img width="1469" alt="Screenshot 2024-07-27 at 22 35 36" src="https://github.com/user-attachments/assets/67d732d3-49ec-4369-91be-5b519f755d7d"> ## Expected behaviour ## A QR code needs to be generated.

kerem closed this issue

2026-03-03 02:14:05 +03:00

kerem commented

2026-03-03 02:14:05 +03:00

Author

Owner

@BlackDex commented on GitHub (Jul 27, 2024):

Re-open that panel, it is a known issue which has been solved with a newer web-vault already if I'm correct. Only we need some extra checks to be done for the newer web-vault to work correctly.

It's not a issue of Vaultwarden it self.

@BlackDex commented on GitHub (Jul 27, 2024): Re-open that panel, it is a known issue which has been solved with a newer web-vault already if I'm correct. Only we need some extra checks to be done for the newer web-vault to work correctly. It's not a issue of Vaultwarden it self.