H-at-H-docker icon indicating copy to clipboard operation
H-at-H-docker copied to clipboard

it can not work, always show the error ip?

Open acer1204 opened this issue 4 years ago • 3 comments

It show

2020-06-29T08:57:48Z [info] The client has failed the external connection test.
2020-06-29T08:57:48Z [info] The server failed to verify that this client is online and available from the Internet.
2020-06-29T08:57:48Z [info] If you are behind a firewall, please check that port 33445 is forwarded to this computer.
2020-06-29T08:57:48Z [info] You might also want to check that ::ffff:203.69.229.94 is your actual public IP address.
2020-06-29T08:57:48Z [info] If you need assistance with forwarding a port to this client, locate a guide for your particular router at http: //portforward.com/
2020-06-29T08:57:48Z [info] The client will remain running so you can run port connection tests.
2020-06-29T08:57:48Z [info] Use Program -> Exit in windowed mode or hit Ctrl+C in console mode to exit the program.
2020-06-29T08:57:48Z [info] ****************************************************************************************************************


2020-06-29T08:57:48Z [info]
2020-06-29T08:57:48Z [info] Startup notification failed.

but my qnap's public ip is 140.130.xx.xx and i setup the container network as host, why it always get 203.69.229.xxx? how to slove the problem?

acer1204 avatar Jun 29 '20 09:06 acer1204

Looks like your device is behind some firewall?

Disappear9 avatar Jun 29 '20 11:06 Disappear9

I've got the same issue with it failing startup even though I have the appropriate port forwarded. I get this error whether I'm using the port or -net host in the docker run command. Mine reports the correct IP though.

i-am-at0m avatar Jul 17 '23 01:07 i-am-at0m

I've got the same issue with it failing startup even though I have the appropriate port forwarded. I get this error whether I'm using the port or -net host in the docker run command. Mine reports the correct IP though.

I am using Synology, and I also encountered a similar problem. After troubleshooting, I allowed the corresponding port request in Synology's firewall, and the network returned to normal after restarting the container.


我用的是群晖,也遇到了跟你类似的问题,我排查后在群晖的防火墙放行了对应的端口请求,重启容器后网络恢复正常。

Small-tailqwq avatar Oct 28 '23 03:10 Small-tailqwq