I attempted to upgrad to 2.12.4 on Windows 10 using a portable install. The error in the server log is 'No ping reply for XX seconds, disconnecting'. The time is anywhere between 40 and 70 seconds each time. This happens after I connect to a single server and autojoin my channels. I have tried turning off away tracking. This is still an issue for me. I'll be installing 2.12.1 until I hear back.
meganleighwoulffe
All 13 comments
I've been experiencing this problem for a while now as well.
There was a previous bug opened for this but was closed out. #1866
I've been sitting on 2.12.1 and have tested .2, .3, and .4 on Windows 10 Pro
This appears to be happening only on the larger networks that I connect to (over 40 channels each), but the fact it's still present after being "resolved" is not ideal.
I've also turned off away tracking and both of the network meters in the view menu.
jwshields
on 1 Mar 2017
Update, I cleared out my configs and recreated all my networks. Still finding ping problems on 2.12.4 even on smaller ones (like 1-4 channels joined) as well as the larger ones. This is with the lag meters turned off as well
jwshields
on 9 Mar 2017
Any non-default system settings?
(e.g. firewall, anti-virus etc?)
If you ping the network manually, does it respond?
learn-more
on 5 Apr 2017
Nothing "out of the ordinary" for me.
I am able to connect normally using 2.12.1, I have connections open to my ZNC host outside of ZNC itself and the connection never drops.
Using 2.12.1, didn't run into issues, and since then, like the issue I mentioned in my previous comment. Ping timeouts galore.
Edit: nothing has changed overall.
I've wiped hexchat from my system, reinstalled with no configs, rebuilt all my configs, messed with all the UI settings mentioned, as well as a system reinstall for a separate problem I was experiencing;.
jwshields
on 5 Apr 2017
this occurs for me whether I run portable or default installation. 2.12.1 runs and connect with no issue whatsoever. I know the server is running fine. I do have all ports opened for the ports I use for IRC and my AV and firewall on my system are both allowing hexchat
meganleighwoulffe
on 5 Apr 2017
and if you run 2.12.1 as portable app, it does work?
learn-more
on 6 Apr 2017
2.12.1 as portable or default installation both work without a single issue.
meganleighwoulffe
on 6 Apr 2017
i have this problem as well using 2.12.4 on win7, downgrading to 2.12.1, however, does not fix it for me.
watceedee
on 20 Apr 2017
i have the same error 2.12.4 : No ping reply for 89 seconds, disconnecting.
But i think that this is important notice, hexchat works fine with freenode but ircnet (irc.cs.tut.fi) dosnt.
survivor303
on 21 Apr 2017
If this is a reoccuring issue for anybody please just disable it for now: /set net_ping_timeout 0
TingPing
on 21 Apr 2017
What are the repercussions of doing this? What side effects may occur?
meganleighwoulffe
on 21 Apr 2017
If your connection is actually lost you won't realize it for a bit. Note that this was the default for like 15 years until this recent release, thus the recent complaints.
TingPing
on 21 Apr 2017
i was using 2.12.4 for a while without problems. i connect via znc bouncer. originally was talking to a private irc server but have since moved to the slack irc gateway. a couple months ago i suddenly started having fairly constant disconnects. my gut says that it was due to how many channels you end up being connected to in slack multi-dm "channels" etc. moving back to 2.12.2 seemed to stop it.
using the workaround disabling ping_timeout lets me use 2.12.4 again.
dahainsworth
on 6 Oct 2017
Related issues
Atario
·
13Comments
philicious
·
10Comments
invidian
·
14Comments
Havvy
·
10Comments
ghost
·
13Comments
Most helpful comment
If this is a reoccuring issue for anybody please just disable it for now:
/set net_ping_timeout 0