Update docs for maintenance: add the description about providers blocking the federation port #4229
Conversation
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
…king the federation port Signed-off-by: Suguru Hirahara <[email protected]>
luixxiul
force-pushed
the
matrix-federation-port
branch
from
0d2bb0b to
8cedd22
Compare
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.
This PR intends to update the migration guide based on my own experience. During migration I've scratched my head for the federation API port not being available, and it turned out the server provider blocked ports other than basic ones (for SSH, HTTPS, etc.)
This kind of stuff can sometimes be difficult to realize, and I think it deserves to be noted for the sake of troubleshooting.