Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

localhost:3000 is misleading #335

Open
asdf4w3t5 opened this issue Feb 27, 2024 · 2 comments
Open

localhost:3000 is misleading #335

asdf4w3t5 opened this issue Feb 27, 2024 · 2 comments

Comments

@asdf4w3t5
Copy link

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
image

@voska
Copy link

voska commented Feb 29, 2024

This is a docker issue: https://docs.docker.com/network/packet-filtering-firewalls/

@asdf4w3t5
Copy link
Author

Docker influences the STDOUT text output by the software?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants