github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 06:08:33 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #34] Error: Invalid configuration file: Validation error: Required at "gerbil.site_block_size" #18351

New Issue
Closed
opened 2026-05-21 17:24:01 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-05-21 17:24:01 -05:00
Owner
Copy Link

Originally created by @M3t4Data on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/34

Hello,
I encountered an issue when trying to start the Pangolin container after following the Quick Install guide. I followed the instructions exactly as described, without making any special configuration changes. However, the pangolin container fails to start with the following error:

Starting migrations from version 1.0.0-beta.3
All migrations completed successfully
/app/server/lib/config.ts:158
            throw new Error(`Invalid configuration file: ${errors}`);
                  ^


Error: Invalid configuration file: Validation error: Required at "gerbil.site_block_size"
    at Config.loadConfig (/app/server/lib/config.ts:158:19)
    at new Config (/app/server/lib/config.ts:91:14)
    at <anonymous> (/app/server/lib/config.ts:202:23)

Node.js v20.18.1

To troubleshoot, I modified the docker-compose.yml file to use the 1.0.0-beta.2 version of the Pangolin image instead of 1.0.0-beta.3. With this version, the container starts correctly without any issues.

Thank you for this tool and your work!

Originally created by @M3t4Data on GitHub (Jan 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/34 Hello, I encountered an issue when trying to start the Pangolin container after following the [Quick Install guide](https://docs.fossorial.io/Getting%20Started/quick-install). I followed the instructions exactly as described, without making any special configuration changes. However, the pangolin container fails to start with the following error: ``` Starting migrations from version 1.0.0-beta.3 All migrations completed successfully /app/server/lib/config.ts:158 throw new Error(`Invalid configuration file: ${errors}`); ^ Error: Invalid configuration file: Validation error: Required at "gerbil.site_block_size" at Config.loadConfig (/app/server/lib/config.ts:158:19) at new Config (/app/server/lib/config.ts:91:14) at <anonymous> (/app/server/lib/config.ts:202:23) Node.js v20.18.1 ``` To troubleshoot, I modified the docker-compose.yml file to use the 1.0.0-beta.2 version of the Pangolin image instead of 1.0.0-beta.3. With this version, the container starts correctly without any issues. Thank you for this tool and your work!
GiteaMirror commented 2026-05-21 17:24:04 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jan 12, 2025):

Try to put site_block_size: 29 manually into the gerbil section of the config and try again. The beta.3 migration is supposed to do that for you but it seems like maybe it is not? We are looking into it...

https://docs.fossorial.io/Pangolin/Configuration/config#gerbil

<!-- gh-comment-id:2585533075 --> @oschwartz10612 commented on GitHub (Jan 12, 2025): Try to put `site_block_size: 29` manually into the gerbil section of the config and try again. The beta.3 migration is supposed to do that for you but it seems like maybe it is not? We are looking into it... https://docs.fossorial.io/Pangolin/Configuration/config#gerbil
GiteaMirror commented 2026-05-21 17:24:05 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jan 12, 2025):

Actually if you have the subnet_group: 100.89.137.0/20 then use site_block_size: 30

Did you install manually or with the installer?

<!-- gh-comment-id:2585533340 --> @oschwartz10612 commented on GitHub (Jan 12, 2025): Actually if you have the `subnet_group: 100.89.137.0/20` then use `site_block_size: 30` Did you install manually or with the installer?
GiteaMirror commented 2026-05-21 17:24:06 -05:00
Author
Owner
Copy Link

@M3t4Data commented on GitHub (Jan 12, 2025):

I installed Pangolin using the provided binary "installer". The configuration that was generated for the gerbil section is as follows:

gerbil:  
    start_port: 51820  
    base_endpoint: (redacted)  
    use_subdomain: false  
    block_size: 16  
    subnet_group: 10.0.0.0/8

I tried reinstalling Pangolin on another VM, and this time the configuration for the gerbil section was different. It looked like this during my test:

gerbil:  
    start_port: 51820  
    base_endpoint: (redacted)  
    use_subdomain: false  
    block_size: 24  
    site_block_size: 30  
    subnet_group: 100.89.137.0/20

It seems like the site_block_size was correctly generated this time and the container run perfectly. Maybe I missed something during the first installation without realizing it ...

<!-- gh-comment-id:2585537901 --> @M3t4Data commented on GitHub (Jan 12, 2025): I installed Pangolin using the provided binary "installer". The configuration that was generated for the gerbil section is as follows: ```yaml gerbil: start_port: 51820 base_endpoint: (redacted) use_subdomain: false block_size: 16 subnet_group: 10.0.0.0/8 ``` I tried reinstalling Pangolin on another VM, and this time the configuration for the gerbil section was different. It looked like this during my test: ```yaml gerbil: start_port: 51820 base_endpoint: (redacted) use_subdomain: false block_size: 24 site_block_size: 30 subnet_group: 100.89.137.0/20 ``` It seems like the site_block_size was correctly generated this time and the container run perfectly. Maybe I missed something during the first installation without realizing it ...
GiteaMirror commented 2026-05-21 17:24:06 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jan 12, 2025):

Okay this is great info thanks!

I think what could have happened is you grabbed the installer for beta.2 (maybe from an old page from the docs or by accident) and because we have :latest as the tag in the docker file it pulled beta.3 and we have this odd issue. Does that sound like it could have been it?

I think we are going to go back to explicitly tagging the docker-compose file and it should fix this.

<!-- gh-comment-id:2585539402 --> @oschwartz10612 commented on GitHub (Jan 12, 2025): Okay this is great info thanks! I think what could have happened is you grabbed the installer for beta.2 (maybe from an old page from the docs or by accident) and because we have :latest as the tag in the docker file it pulled beta.3 and we have this odd issue. Does that sound like it could have been it? I think we are going to go back to explicitly tagging the docker-compose file and it should fix this.
GiteaMirror commented 2026-05-21 17:24:07 -05:00
Author
Owner
Copy Link

@M3t4Data commented on GitHub (Jan 12, 2025):

That might be it, especially since the latest release is so recent. I’ve added an explicit tag to the containers just to be safe, and everything is working fine now.

Thanks for your help, and for the quick response !

<!-- gh-comment-id:2585540383 --> @M3t4Data commented on GitHub (Jan 12, 2025): That might be it, especially since the latest release is so recent. I’ve added an explicit tag to the containers just to be safe, and everything is working fine now. Thanks for your help, and for the quick response !
GiteaMirror commented 2026-05-21 17:24:08 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jan 12, 2025):

No worries! Thanks!

<!-- gh-comment-id:2585540700 --> @oschwartz10612 commented on GitHub (Jan 12, 2025): No worries! 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#18351
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?