IRCConnectEnabled is unexpectedly set to yes in znc.conf #52

New Issue

2026-10-05T03:56:22+02:00

adam commented

2026-10-05 03:56:22 +02:00

znc sets IRCConnectEnabled to true in znc.conf under several circumstances.

SetIRCConnectEnabled(true or false); is called when

you execute "/znc jump, connect, or disconnect" (ClientCommand.cpp deals with it)
you issue "/msg *admin reconnect or disconnect"
CBlockUser::Block() is called
CIRCNetwork::CIRCNetwork() is called

And IRCConnectEnabled is written to znc.conf when WriteConfig is called.
WriteConfig is called when

you execute "/znc shutdown, restart, or saveconfig"
znc receives SIGUSR1
you save settings in webadmin.

Since I use webadmin frequently, this is a problem.

When znc is started, znc automatically connects to networks with IRCConnectEnabled set to yes.
But I don't want znc to automatically connect to any network when znc is started.
So I don't want znc to set IRCConnectEnabled to true in any circumstance.
But CIRCNetwork::Connect() refuses to connect if m_bIRCConnectEnabled is false.

How can I prevent znc from automatically connecting to networks?
I want to obtain manual control over whether and when znc connects to a network.

znc sets IRCConnectEnabled to true in znc.conf under several circumstances. SetIRCConnectEnabled(true or false); is called when 1) you execute "/znc jump, connect, or disconnect" (ClientCommand.cpp deals with it) 2) you issue "/msg *admin reconnect or disconnect" 3) CBlockUser::Block() is called 4) CIRCNetwork::CIRCNetwork() is called And IRCConnectEnabled is written to znc.conf when WriteConfig is called. WriteConfig is called when 1) you execute "/znc shutdown, restart, or saveconfig" 2) znc receives SIGUSR1 3) you save settings in webadmin. Since I use webadmin frequently, this is a problem. When znc is started, znc automatically connects to networks with IRCConnectEnabled set to yes. But I don't want znc to automatically connect to any network when znc is started. So I don't want znc to set IRCConnectEnabled to true in any circumstance. But CIRCNetwork::Connect() refuses to connect if m_bIRCConnectEnabled is false. How can I prevent znc from automatically connecting to networks? I want to obtain manual control over whether and when znc connects to a network.

adam closed this issue

2026-10-05 03:56:22 +02:00

adam commented

2026-10-05 03:56:23 +02:00

Please can you tell me which commit you are having issues with because I recently rewrote the IRCConnectEnabled to fix some bugs.

Please can you tell me which commit you are having issues with because I recently rewrote the IRCConnectEnabled to fix some bugs.

adam commented

2026-10-05 03:56:24 +02:00

I compiled the latest revision, and it doesn't seem to have this behavior.
I think I can close it now.

I compiled the latest revision, and it doesn't seem to have this behavior. I think I can close it now.

adam commented

2026-10-05 03:56:24 +02:00

I'm reopening this issue since I found the exact cause of this issue.
The detail explanation is in the main article.

I'm reopening this issue since I found the exact cause of this issue. The detail explanation is in the main article.

adam commented

2026-10-05 03:56:25 +02:00

Write a global module, which would prevent any connection between OnLoad and OnBoot, and which would set IRCConnectEnabled to false for every user in OnBoot.

It's not a bug at all, and therefore it won't be "fixed" in ZNC.

Write a global module, which would prevent any connection between OnLoad and OnBoot, and which would set IRCConnectEnabled to false for every user in OnBoot. It's not a bug at all, and therefore it won't be "fixed" in ZNC.

adam commented

2026-10-05 03:56:26 +02:00

What znc assumes is that when you tell a user to "connect" is that you want to have it stay connected. That's why it's getting saved to the config file. One could argue that "connect" should only establish a temporary connection that would have to be reconnected manually in case it drops, but that's not the design we chose.

What znc assumes is that when you tell a user to "connect" is that you want to have it stay connected. That's why it's getting saved to the config file. One could argue that "connect" should only establish a temporary connection that would have to be reconnected manually in case it drops, but that's not the design we chose.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#52