docs: add network hosting and reverse proxy troubleshooting (@isma-021)#7970
Merged
Merged
Conversation
Added instructions for hosting over HTTPS and troubleshooting frontend connection issues.
Member
|
Thanks! |
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 noticed that when trying to host Monkeytype over a local network or the internet instead of
localhost, the frontend crashes with anUncaught TypeError: crypto.randomUUID is not a functionerror. This happens because modern browsers restrict this API to secure contexts (HTTPS).When putting a reverse proxy in front to handle HTTPS, it's very easy to run into Mixed Content blocks or 404 errors due to incorrect
.envconfigurations (like adding a trailing slash toMONKEYTYPE_FRONTENDURLor forgetting to completely recreate the containers).This PR updates
SELF_HOSTING.mdto:.envfile to avoid API 404 errors (the trailing slash issue).docker compose up -d --force-recreateand clearing the browser cache, since environment variables are baked into the SPA static files at startup.Checks