SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

FileBrowser Quantum resets password to default #1839

New Issue
Closed
opened 2025-11-20 05:18:17 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:18:17 -05:00
Owner
Copy Link

Originally created by @guyman70718 on GitHub (Sep 3, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

FileBrowser Quantum

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/filebrowser-quantum.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.4.5/57892e8e686cb35b (running kernel: 6.8.12-13-pve)

📝 Provide a clear and concise description of the issue.

The installed copy of filebrowser resets the admin password to the one specified in the config without notification.

🔄 Steps to reproduce the issue.

  1. Install FileBrowser Quantum
  2. Change password via the WebUI
  3. Reboot
  4. Password has been changed back to helper-scripts.com

❌ Paste the full error output (if available).

na

🖼️ Additional context (optional).

This can be resolved by editing /usr/local/community-scripts/fq-config.yaml, however I believe this isn't made clear enough during setup that you MUST change the password via this file and NOT via the webui. I didn't realize, and I had my instance exposed to the open internet with the default password for some period.

Originally created by @guyman70718 on GitHub (Sep 3, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? FileBrowser Quantum ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/filebrowser-quantum.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.4.5/57892e8e686cb35b (running kernel: 6.8.12-13-pve) ### 📝 Provide a clear and concise description of the issue. The installed copy of filebrowser resets the admin password to the one specified in the config without notification. ### 🔄 Steps to reproduce the issue. 1. Install FileBrowser Quantum 2. Change password via the WebUI 3. Reboot 4. Password has been changed back to helper-scripts.com ### ❌ Paste the full error output (if available). na ### 🖼️ Additional context (optional). This can be resolved by editing /usr/local/community-scripts/fq-config.yaml, however I believe this isn't made clear enough during setup that you MUST change the password via this file and NOT via the webui. I didn't realize, and I had my instance exposed to the open internet with the default password for some period.
saavagebueno added the bug label 2025-11-20 05:18:17 -05:00
saavagebueno commented 2025-11-20 05:18:17 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 4, 2025):

  1. Then, in my opinion, it's a software error. The frontend should overwrite the yaml. => Report it to their repo

  2. The config file is visible on the website; it's not a script error per se, but at most a configuration adjustment, but we assume that every tool that has a config and a database changes this independently.

@MickLesk commented on GitHub (Sep 4, 2025): 1. Then, in my opinion, it's a software error. The frontend should overwrite the yaml. => Report it to their repo 2. The config file is visible on the website; it's not a script error per se, but at most a configuration adjustment, but we assume that every tool that has a config and a database changes this independently.
saavagebueno commented 2025-11-20 05:18:18 -05:00
Author
Owner
Copy Link

@WildEchoWanderer commented on GitHub (Nov 6, 2025):

I have the same problem. @guyman70718 did you report it in their repo?

@WildEchoWanderer commented on GitHub (Nov 6, 2025): I have the same problem. @guyman70718 did you report it in their repo?
saavagebueno commented 2025-11-20 05:18:18 -05:00
Author
Owner
Copy Link

@guyman70718 commented on GitHub (Nov 6, 2025):

I have the same problem. @guyman70718 did you report it in their repo?

No

@guyman70718 commented on GitHub (Nov 6, 2025): > I have the same problem. [@guyman70718](https://github.com/guyman70718) did you report it in their repo? No
saavagebueno commented 2025-11-20 05:18:18 -05:00
Author
Owner
Copy Link

@Vaskyy commented on GitHub (Nov 17, 2025):

I got the same behaviour.
Whats their repo to post this issue?

@Vaskyy commented on GitHub (Nov 17, 2025): I got the same behaviour. Whats their repo to post this issue?
saavagebueno commented 2025-11-20 05:18:18 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 17, 2025):

https://github.com/gtsteffaniak/filebrowser/

@MickLesk commented on GitHub (Nov 17, 2025): https://github.com/gtsteffaniak/filebrowser/
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1839
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?