adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-11-03 02:42:21 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

ZNC starts in a bad state when unable to load SSL Cert #283

New Issue
Closed
opened 2026-10-05 04:09:51 +02:00 by adam · 3 comments
adam commented 2026-10-05 04:09:51 +02:00
Owner
Copy link
Copy source

Hi, not sure if this is intended or not, but I had ZNC start in a dirty state during a server migration.

I had migrated my configuration file from an older version of ZNC to ZNC 1.2 which was on the new server. The path of the SSL Certificate did not exist.

ZNC prompted me that the SSL Certificate was not able to be read (didn't exist) asked me to create one in the same location. Creating the new .pem file succeeded but it failed to save.

ZNC would continue to start and was accessible on the defined port, however no connection could be completed.

Workaround: Updated the path in the configuration file, which ZNC then proceeded to create a new .pem file, and was able to load it successfully.

Hi, not sure if this is intended or not, but I had ZNC start in a dirty state during a server migration. I had migrated my configuration file from an older version of ZNC to ZNC 1.2 which was on the new server. The path of the SSL Certificate did not exist. ZNC prompted me that the SSL Certificate was not able to be read (didn't exist) asked me to create one in the same location. Creating the new .pem file succeeded but it failed to save. ZNC would continue to start and was accessible on the defined port, however no connection could be completed. Workaround: Updated the path in the configuration file, which ZNC then proceeded to create a new .pem file, and was able to load it successfully. <!-- github-sync-id:25060880 -->
adam closed this issue 2026-10-05 04:09:52 +02:00
adam commented 2026-10-05 04:09:53 +02:00
Author
Owner
Copy link
Copy source

It's run now with different $HOME than before? Fix znc.conf file, it probably contains old path
Also check permissions on files

It's run now with different $HOME than before? Fix znc.conf file, it probably contains old path Also check permissions on files <!-- github-comment-id:31591848 -->
adam commented 2026-10-05 04:09:53 +02:00
Author
Owner
Copy link
Copy source

I did fix the file and it resolved the issue as I stated before. The "issue" if you will is that ZNC will continue to go through the startup process after it fails to save/load the key, and still binding to the selected port without a .pem file to reference.

I did fix the file and it resolved the issue as I stated before. The "issue" if you will is that ZNC will continue to go through the startup process after it fails to save/load the key, and still binding to the selected port without a .pem file to reference. <!-- github-comment-id:31597304 -->
adam commented 2026-10-05 04:09:54 +02:00
Author
Owner
Copy link
Copy source

Did you check permissions? Do you have write access on ~/.znc/ ? How exactly it fails to save? Logs please

Did you check permissions? Do you have write access on ~/.znc/ ? How exactly it fails to save? Logs please <!-- github-comment-id:31599715 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#283