Admin Page unable to read the changed value in config.json #831

New Issue

Closed

opened 2026-02-04 22:55:24 +03:00 by OVERLORD · 2 comments

OVERLORD commented 2026-02-04 22:55:24 +03:00

Owner

Copy Link

Originally created by @wcjxixi on GitHub (Oct 13, 2020).

I change the value of setting in Admin Page, it can write to config.json, but when I change value of setting in config.json directly, Admin Page unable to read the changed value in config.json.

I have tried to clear the browser's cooke and cache, but still the same.

I think the permissions of the config.json file are correct.

My Environment

• Server Installed: 1.17.0
• Web Installed: 2.16.1

Originally created by @wcjxixi on GitHub (Oct 13, 2020). I change the value of setting in Admin Page, it can write to config.json, but when I change value of setting in config.json directly, Admin Page unable to read the changed value in config.json. I have tried to clear the browser's cooke and cache, but still the same. I think the permissions of the config.json file are correct.  ### My Environment - Server Installed: 1.17.0 - Web Installed: 2.16.1

OVERLORD added the better for forum label 2026-02-04 22:55:24 +03:00

OVERLORD closed this issue 2026-02-04 22:55:30 +03:00

OVERLORD commented 2026-02-04 22:55:43 +03:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Oct 13, 2020):

Did you also restarted bitwarden? Because it only reads that file during start.

@BlackDex commented on GitHub (Oct 13, 2020): Did you also restarted bitwarden? Because it only reads that file during start.

OVERLORD commented 2026-02-04 22:55:48 +03:00

Author

Owner

Copy Link

@wcjxixi commented on GitHub (Oct 14, 2020):

Did you also restarted bitwarden? Because it only reads that file during start.

Thank you, it has been resolved, as you said, bitwarden needs to be restarted

@wcjxixi commented on GitHub (Oct 14, 2020): > Did you also restarted bitwarden? Because it only reads that file during start. Thank you, it has been resolved, as you said, bitwarden needs to be restarted

OVERLORD referenced this issue 2026-02-05 04:56:50 +03:00

[PR #831] [MERGED] SIGNUPS_ALLOWED with no whitelist [fixes #830] #2780

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

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

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 better for forum

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#831