♻️ Add support for NEXTAUTH_URL_INTERNAL` option #750
Closed
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.
packages/dashboard/src/env/schema.mjs
NEXTAUTH_URL_INTERNAL
to the.env
This update will allow people to load the dashboard from the public IP and the internal IP. This way if they are hosting on their own machines they can have access it without having to use a different system on a different network.
With this there are two connection IPs. There is the public one accessible by others and the Internal IP only accessible from the host machine.
Both work perfectly with this update. Naturally though with this method if you want to access it form a seperate machine on the same network you will need to change the
NEXTAUTH_URL_INTERNAL="http://0.0.0.0:3000"
toNEXTAUTH_URL_INTERNAL="http://<private_ip>:3000"
aslocalhost
would not work for that.For instance if your private IP was
192.168.0.29
theNEXTAUTH_URL_INTERNAL
flag would need to be set toNEXTAUTH_URL_INTERNAL="http://192.168.0.29:3000"
Naturally you can see a description of this in the issue linked below: