Disable IPv6 for sharelatex container #229
Open
Conversation
This file contains 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
|
This change should not be needed anymore - the problem seems to have been fixed in the new versions of the toolkit. |
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
For me, there was an issue where sharelatex/nginx were trying to use 127.0.0.1 to access the proxied services, but some were only listening on ::1, and one seemed to be listening on ::1 but redirect to 127.0.0.1. To make things consistent, I disabled IPv6 in that container to ensure they all use 127.0.0.1. An alternative solution would be to make all config references consistent (127.0.0.1 vs "localhost", which may resolve to ::1), but this seems simpler and IPv6 is unlikely to be needed for the internal Docker network in this case.
Related issues / Pull Requests
None
Contributor Agreement