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

Changed localhost to 0.0.0.0 #4

Closed
wants to merge 1 commit into from
Closed

Conversation

Cerkoryn
Copy link

@Cerkoryn Cerkoryn commented Dec 7, 2023

Running a Watcher in a container. Ran into issue that 127.0.0.1 was not reachable from network. Is there a reason for it to be localhost only? If not, 0.0.0.0 would give fewer headaches to new Watchers.

Running a Watcher in a container.  Ran into issue that 127.0.0.1 was not reachable from network.  Is there a reason for it to be localhost only?  If not, 0.0.0.0 would give fewer headaches to new Watchers.
@QCPOLstakepool
Copy link
Contributor

Check #3 😉

@zargarzadehm
Copy link
Member

If you use 0.0.0.0, the watcher interface will be made public on all your interfaces, potentially creating a vulnerability by allowing outside access to your watcher web UI. Therefore, using 0.0.0.0 isn't a good solution. We recommend employing other methods, such as SSH port-forwarding, to access your watcher web UI.

@Cerkoryn
Copy link
Author

I like @QCPOLstakepool's solution in #3, I think that provides the best of both worlds.

@Cerkoryn Cerkoryn closed this Dec 10, 2023
@ccgarant ccgarant mentioned this pull request Dec 18, 2023
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

Successfully merging this pull request may close these issues.

3 participants