Skip to content

2024-12-15T06:48:36Z [WARN] Rejecting connection request from 172.17.0.1 during startup. #6

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

Closed
wants to merge 1 commit into from

Conversation

UjuiUjuMandan
Copy link

@UjuiUjuMandan UjuiUjuMandan commented Dec 15, 2024

Hi, H@H added --disable-ip-origin-check to solve this in October 2019.

@UjuiUjuMandan
Copy link
Author

You said Or if bridge mode doesn't work on your Docker host for some reason... in readme, but how would it ever work at all without --disable-ip-origin-check I wonder?

@UjuiUjuMandan
Copy link
Author

@frosty5689 Check this please.

@frosty5689
Copy link
Owner

Sorry for the delay in response...

I'm using bridge mode with a port exposed and it works fine detecting my public IP.

This likely works because H@H doesn't use the IP allocated within the Docker subnet, and instead send request to the server backend to determine the public IP.

From the description of this option, looks like this disables the check that checks to see if the request to the H@H client is from a known server IP address, so this is to fix NAT issues common in Countries where IPv4 is scarce.

I will add an "EXTRA_ARGS" env var that gets added at the end of the command so users can add any arguments they want.

@frosty5689
Copy link
Owner

See #9

@frosty5689 frosty5689 closed this Feb 27, 2025
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.

2 participants