-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
国内机无法检测IPV4 #124
Comments
你的 server 是只有 ipv6 的 ip ?
|
日志已经写了, |
搞不明白 这个不会要指定端口的吧 比如80 443什么的 这机器除了不备案没有80和443之类的端口和其它机器没区别 |
好像因为这个也无法看实时流量了 之前用的ServerStatus-Hotaru 实时流量是可以检测到的 |
这个是用http 协议上报的,他们用的是 tcp 协议,可以查查你的环境有没开http代理,检测一下http 相关 |
用grpc上报也不行? 没用代理 不懂怎么检测 不折腾了 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
服务端只显示IPV6 机器是双栈的 IPV4正常可用
Dec 16 15:38:53 coal-w768p1ep stat_client[2568814]: enable feature native
Dec 16 15:38:56 coal-w768p1ep stat_client[2568814]: get_network (ipv4, ipv6) => (false, false)
Dec 16 15:38:56 coal-w768p1ep stat_client[2568814]: ERROR stat_client > refresh_ip_info error => error sending request for url (http://ip-api.com/json?fields=status,message,continent,continentCode,country,countryCode,region,regionName,city,district,zip,lat,lon,t>
Dec 16 15:38:56 coal-w768p1ep stat_client[2568814]: Caused by:
Dec 16 15:38:56 coal-w768p1ep stat_client[2568814]: 0: connection error: Connection reset by peer (os error 104)
Dec 16 15:38:56 coal-w768p1ep stat_client[2568814]: 1: Connection reset by peer (os error 104)
Dec 16 15:38:59 coal-w768p1ep stat_client[2568814]: ERROR stat_client > refresh_ip_info error => error sending request for url (http://ip-api.com/json?fields=status,message,continent,continentCode,country,countryCode,region,regionName,city,district,zip,lat,lon,t>
Dec 16 15:38:59 coal-w768p1ep stat_client[2568814]: Caused by:
Dec 16 15:38:59 coal-w768p1ep stat_client[2568814]: 0: connection error: Connection reset by peer (os error 104)
Dec 16 15:38:59 coal-w768p1ep stat_client[2568814]: 1: Connection reset by peer (os error 104)
The text was updated successfully, but these errors were encountered: