I have a huge issue with my ZNC installation, and it's doing it on fresh installations of ZNC as well. It seems that ZNC will not connect more than six users to a given IRC network. The issue is deeper than network settings as we have an exception set on the target server. When the user attempts to /msg *status connect they are not getting any errors, not even a "Connection timed out". This is rather confusing for me because it was just working fine the the other day until some random disconnect happened. I have attempted this on two different machines with fresh installs and it's the same results.
I have a huge issue with my ZNC installation, and it's doing it on fresh installations of ZNC as well. It seems that ZNC will not connect more than six users to a given IRC network. The issue is deeper than network settings as we have an exception set on the target server. When the user attempts to `/msg *status connect` they are not getting any errors, not even a "Connection timed out". This is rather confusing for me because it was just working fine the the other day until some random disconnect happened. I have attempted this on two different machines with fresh installs and it's the same results.
<!-- github-sync-id:45735428 -->
Do you see anything in znc -D? You might also want to read Debugging at ZNC wiki and include information on your ZNC version and OS.
Do you see anything in `znc -D`? You might also want to read [Debugging at ZNC wiki](http://wiki.znc.in/Debugging) and include information on your ZNC version and OS.
<!-- github-comment-id:59020985 -->
May you describe what was the issue with BindHosts?
2014-10-14 12:14 GMT+01:00 Richard Banks notifications@github.com:
> Closed #707 https://github.com/znc/znc/issues/707.
>
> —
> Reply to this email directly or view it on GitHub
> https://github.com/znc/znc/issues/707#event-178151571.
<!-- github-comment-id:59029059 -->
@DarthGandalf The users had BindHosts set that were no longer valid due to a newly invalid domain. The process was hanging up trying to connect those users instead of moving on to connect users who didn't have a BindHost set. Unfortunately there was no way to disable BindHosts globally so I had to go through and disable them through the ControlPanel module individually and then reconnect them. BindHosts was showing blank in the WebAdmin interface as well, for each of the users so there was no way to do so there either.
@DarthGandalf The users had BindHosts set that were no longer valid due to a newly invalid domain. The process was hanging up trying to connect those users instead of moving on to connect users who didn't have a BindHost set. Unfortunately there was no way to disable BindHosts globally so I had to go through and disable them through the ControlPanel module individually and then reconnect them. BindHosts was showing blank in the WebAdmin interface as well, for each of the users so there was no way to do so there either.
<!-- github-comment-id:59158252 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have a huge issue with my ZNC installation, and it's doing it on fresh installations of ZNC as well. It seems that ZNC will not connect more than six users to a given IRC network. The issue is deeper than network settings as we have an exception set on the target server. When the user attempts to
/msg *status connectthey are not getting any errors, not even a "Connection timed out". This is rather confusing for me because it was just working fine the the other day until some random disconnect happened. I have attempted this on two different machines with fresh installs and it's the same results.Do you see anything in
znc -D? You might also want to read Debugging at ZNC wiki and include information on your ZNC version and OS.ZNC 1.4 Ubuntu 14.04
Some of the accounts seem to be running into a BindHost issue. How do I fix that globally?
This issue is fixed. The issue was BindHosts.
May you describe what was the issue with BindHosts?
2014-10-14 12:14 GMT+01:00 Richard Banks notifications@github.com:
@DarthGandalf The users had BindHosts set that were no longer valid due to a newly invalid domain. The process was hanging up trying to connect those users instead of moving on to connect users who didn't have a BindHost set. Unfortunately there was no way to disable BindHosts globally so I had to go through and disable them through the ControlPanel module individually and then reconnect them. BindHosts was showing blank in the WebAdmin interface as well, for each of the users so there was no way to do so there either.