github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-22 01:22:50 -05:00
Code Issues 959 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #640] 1.3.0 - server:secret config option not populated on fresh install #14430

New Issue
Closed
opened 2026-05-16 02:16:25 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-16 02:16:25 -05:00
Owner
Copy Link

Originally created by @rfrank on GitHub (May 2, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/640

On fresh install, the server's secret config option does not get populated. I did several fresh installs to confirm the bug persisted. I ended up generating a 52-char alphanumeric string to get things up and going but wanted to submit an issue in case it's not just me and a fix needs to be issued.

Originally created by @rfrank on GitHub (May 2, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/640 On fresh install, the server's secret config option does not get populated. I did several fresh installs to confirm the bug persisted. I ended up generating a 52-char alphanumeric string to get things up and going but wanted to submit an issue in case it's not just me and a fix needs to be issued.
GiteaMirror commented 2026-05-16 02:16:27 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (May 2, 2025):

I think I fixed this. Could re download the installer and confirm?

<!-- gh-comment-id:2848193378 --> @oschwartz10612 commented on GitHub (May 2, 2025): I think I fixed this. Could re download the installer and confirm?
GiteaMirror commented 2026-05-16 02:16:27 -05:00
Author
Owner
Copy Link

@xd003 commented on GitHub (May 3, 2025):

I can confirm this issue, after i upgraded my pangolin docker to 1.3.0, the config.yml file didn't had the secret config option added

<!-- gh-comment-id:2848462216 --> @xd003 commented on GitHub (May 3, 2025): I can confirm this issue, after i upgraded my pangolin docker to 1.3.0, the config.yml file didn't had the secret config option added
GiteaMirror commented 2026-05-16 02:16:28 -05:00
Author
Owner
Copy Link

@Cratermn commented on GitHub (May 4, 2025):

This is still occurring on 1.3.1

<!-- gh-comment-id:2848865746 --> @Cratermn commented on GitHub (May 4, 2025): This is still occurring on 1.3.1
GiteaMirror commented 2026-05-16 02:16:28 -05:00
Author
Owner
Copy Link

@GRAUPS commented on GitHub (May 4, 2025):

I'm also encountering this issue on 1.3.1. In my case the secret option is there, but it is not populated (null). This causes Pangolin to fail to start.

Here is the error in the log

pangolin | Starting migrations from version 1.3.1
pangolin | Migrations to run:
pangolin | All migrations completed successfully
pangolin | /app/server/lib/config.ts:224
pangolin | throw new Error(Invalid configuration file: ${errors});
pangolin | ^
pangolin |
pangolin |
pangolin | Error: Invalid configuration file: Validation error: Expected string, received null at "server.secret"
pangolin | at Pa.loadConfig (/app/server/lib/config.ts:224:19)
pangolin | at new Pa (/app/server/lib/config.ts:182:14)
pangolin | at (/app/server/lib/config.ts:380:23)
pangolin |
pangolin | Node.js v20.19.1
pangolin exited with code 1

<!-- gh-comment-id:2848890206 --> @GRAUPS commented on GitHub (May 4, 2025): I'm also encountering this issue on 1.3.1. In my case the secret option is there, but it is not populated (null). This causes Pangolin to fail to start. Here is the error in the log pangolin | Starting migrations from version 1.3.1 pangolin | Migrations to run: pangolin | All migrations completed successfully pangolin | /app/server/lib/config.ts:224 pangolin | throw new Error(`Invalid configuration file: ${errors}`); pangolin | ^ pangolin | pangolin | pangolin | Error: Invalid configuration file: Validation error: Expected string, received null at "server.secret" pangolin | at Pa.loadConfig (/app/server/lib/config.ts:224:19) pangolin | at new Pa (/app/server/lib/config.ts:182:14) pangolin | at <anonymous> (/app/server/lib/config.ts:380:23) pangolin | pangolin | Node.js v20.19.1 pangolin exited with code 1
GiteaMirror commented 2026-05-16 02:16:29 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (May 4, 2025):

Will look into this

<!-- gh-comment-id:2848890520 --> @miloschwartz commented on GitHub (May 4, 2025): Will look into this
GiteaMirror commented 2026-05-16 02:16:29 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (May 4, 2025):

Fix was not properly merged into dev. Just pushed the commit and rebuilt. Please try again now.

<!-- gh-comment-id:2848908872 --> @oschwartz10612 commented on GitHub (May 4, 2025): Fix was not properly merged into dev. Just pushed the commit and rebuilt. Please try again now.
GiteaMirror commented 2026-05-16 02:16:30 -05:00
Author
Owner
Copy Link

@GRAUPS commented on GitHub (May 7, 2025):

I can confirm this is fixed now, thanks!

<!-- gh-comment-id:2857059625 --> @GRAUPS commented on GitHub (May 7, 2025): I can confirm this is fixed now, thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#14430
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?