You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you set NEXT_PUBLIC_WEBAPP_URL= to your devices IP address e.g. 192.168.1.x or whatever, it will say it is listening on 0.0.0.0:3000 which is accurate.
However, within the .env config NEXT_PUBLIC_WEBAPP_URL= needs to be set to your TLD example.com etc.
When you do this, it says it is listening on localhost:3000 however that isn't true as you can still connect to it via the routeable LAN IP so it is listening on 0.0.0.0:3000 still and not only localhost otherwise it would only respond to localhost and nothing else. Similarly if it was listening to 127.0.0.1 it wouldn't respond if you connected to 192.168.1.x
So anyway it works how it is, but it says the information wrong.
You can see I am correct with the command ss -antlp as well
The text was updated successfully, but these errors were encountered:
When you set
NEXT_PUBLIC_WEBAPP_URL=
to your devices IP address e.g. 192.168.1.x or whatever, it will say it is listening on 0.0.0.0:3000 which is accurate.However, within the .env config
NEXT_PUBLIC_WEBAPP_URL=
needs to be set to your TLDexample.com
etc.When you do this, it says it is listening on
localhost:3000
however that isn't true as you can still connect to it via the routeable LAN IP so it is listening on0.0.0.0:3000
still and not only localhost otherwise it would only respond to localhost and nothing else. Similarly if it was listening to 127.0.0.1 it wouldn't respond if you connected to 192.168.1.xSo anyway it works how it is, but it says the information wrong.
You can see I am correct with the command
ss -antlp
as wellThe text was updated successfully, but these errors were encountered: