Added relevant requirement to readme-vars.yml#27
Merged
thelamer merged 1 commit intolinuxserver:masterfrom Mar 1, 2026
Merged
Conversation
Updated app setup block with additional information regarding container requirements. I had been struggling with the Sealskin connection until I found the issue linuxserver#6 . I wish I had read clearly that before as I have everything else (40) from LinuxServer running behind Caddy. I added to the container requirements paragraph the @thelamer words: "The entire stack is not designed to run behind a reverse proxy it is meant to be directly exposed to the internet."
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
Contributor
|
I am a bot, here are the test results for this PR:
|
thelamer
approved these changes
Mar 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
I added to the container requirements paragraph the @thelamer words: "The entire stack is not designed to run behind a reverse proxy it is meant to be directly exposed to the internet." to readme-vars.yml
Benefits of this PR and context:
That information is important because this container is a exceptional a exceptional case compared to other LinuxServer ones.
I have every single other LinuxServer containeir running behind Caddy without any setbacks. I had been struggling with the Sealskin connection until I found the issue #6 . I wish I had read clearly that before.
How Has This Been Tested?
Once I removed SealSkin from Caddy and exposed it directly, everything is running smoothly.
Source / References:
@thelamer mentioned it on #6