feat: added instructions to enable IPv6 networking on application servers #617
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
nimish-ks
changed the title
|
Thank you for the addition, though the information was a bit misplaced, I've fixed the placement so the information is added to the private networking specific documentation. Let me know if you have any suggestions to my additions. |
|
LGTM! |
|
Thanks again! |
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.
I struggled to reach my services over Railway private networking and ended up solving the problem by enabling IPv6 on my application servers. phasehq/console#395
Thought this might save some folks a headache.
I'm putting this together in a hurry. Please feel free to rewrite the language / put this else ware if it makes better sense to do so.