mirror of
https://github.com/pelican-dev/panel.git
synced 2026-03-01 11:21:31 +03:00
Settings are no longer saving on the Panel #522
Reference in New Issue
Block a user
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?
Originally created by @felinusfish on GitHub (Dec 20, 2025).
Current Behavior
Currently, on canary (Commit
1d5ace3) using a Docker installation, there appears to be a regression when trying to save the settings, as it does not save your settings after you have changed them. I am not 100% sure if this is an issue with Beta 30 or potentially an issue with Docker installations, But I'm sure somebody will chime in sooner or later on whether or not the issue exists for them outside of my specifications.Expected Behavior
The settings should be saving, but they are not.
Steps to Reproduce
Panel Version
canary (
1d5ace3)Wings Version
N/A
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
@coderabbitai[bot] commented on GitHub (Dec 20, 2025):
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
Examples
🔗 Similar Issues
Possible Duplicates
Related Issues
👤 Suggested Assignees
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord or schedule a call!
@notAreYouScared commented on GitHub (Dec 20, 2025):
No error logs whatsoever? What settings? Profile? Server? Panel? There's alot of settings... no notifications??
@parkervcp commented on GitHub (Dec 20, 2025):
Which settings are you changing?
@felinusfish commented on GitHub (Dec 20, 2025):
Any. All of them are not saving in "Settings"! There were no errors in the logs.
@notAreYouScared commented on GitHub (Dec 20, 2025):
So youre editing the options in the "Settings" tab... so panel settings... when you click save what happens? Does the page refresh? Does it popup in the top corner that it failed?
@felinusfish commented on GitHub (Dec 20, 2025):
The page either refreshes afterwards when it says "Settings saved!" without changing the settings, or it doesn't refresh and says "Settings saved!" and manually refreshing shows the original settings, not the modified settings.
@notAreYouScared commented on GitHub (Dec 20, 2025):
Verify the .env has correct permissions, as all those settings live in it, and if it cant write to it... then yes it would still show old values.
@felinusfish commented on GitHub (Dec 20, 2025):
What would have changed about the .env permissions between now and two days ago?
@notAreYouScared commented on GitHub (Dec 20, 2025):
I dont have access to your system, nor setup. So I cannot answer that.
Did you check the permissions? Did you run the permission commands in the install guide to make sure they're correct? Then try again?
@parkervcp commented on GitHub (Dec 20, 2025):
I tested this on my a copy of the panel and while the UI refreshed after I changed the name the env file updated.
@PalmarHealer commented on GitHub (Dec 21, 2025):
Having the issue aswell. I have beta30 in docker
@PalmarHealer commented on GitHub (Dec 22, 2025):
For me this only occurs only when updating from an older version. Fresh installs work fine.
@notAreYouScared commented on GitHub (Dec 22, 2025):
In panel settings go to Misc, and check to see if automatic allocation creation is on. If it is, are the two port sections empty?
@PalmarHealer commented on GitHub (Dec 22, 2025):
That is not the problem. But I fixed it
I don't know what is causing this issue but I was able to fix it.
That did the trick for me.
Note: If you're using a oauth provider make sure its enabled, mine disabled but I just had to click next because the values where pre-filled from env
@rmartinoscar commented on GitHub (Dec 24, 2025):
Probably means you had a .env that wasn't symlinked to your docker volume or config is somehow cached which is incompatible with our design.
@parkervcp commented on GitHub (Dec 26, 2025):
I know about the issue and have a fix. I am not able to test and make the change right now.