unable to connect to znc when using 4096 bit key signed cert, only 2048 bit #573

Closed
opened 2026-10-05 04:30:48 +02:00 by adam · 6 comments
Owner

title says it all. znc webadmin or bnc wont load when using a signed 4096 cert. it works with a signed 2048 cert only

title says it all. znc webadmin or bnc wont load when using a signed 4096 cert. it works with a signed 2048 cert only <!-- github-sync-id:106132107 -->
adam closed this issue 2026-10-05 04:30:48 +02:00
Author
Owner

And you have followed http://wiki.znc.in/Signed_SSL_certificate ?

@kerio92 you are more familiar with ZNC & SSL than me.

And you have followed http://wiki.znc.in/Signed_SSL_certificate ? @kerio92 you are more familiar with ZNC & SSL than me. <!-- github-comment-id:139733175 -->
Author
Owner

yep. did the same thing for both certs. 2048 works. 4096 doesnt

yep. did the same thing for both certs. 2048 works. 4096 doesnt <!-- github-comment-id:139733418 -->
Author
Owner

And you are sure that the issue is with ZNC and not your client?

Could you also add the information that was asked when you opened this issue?

The information I think is needed this time is:

  • /znc version.
  • your OS/distribution version.
  • what znc -D says when you connect to ZNC with the bigger certificate?
And you are sure that the issue is with ZNC and not your client? Could you also add the information that was asked when you opened this issue? - https://github.com/znc/znc/blob/master/CONTRIBUTING.md#reporting-bugs The information I think is needed this time is: - `/znc version`. - your OS/distribution version. - what `znc -D` says when you connect to ZNC with the bigger certificate? <!-- github-comment-id:139737039 -->
Author
Owner

yes because i tried the webadmin with my browser too. webadmin on 4096 didnt work but it did on 2048. znc just seemed completely inaccessible with 4096.

<_status> ZNC 1.6.1 - http://znc.in
<_status> IPv6: yes, SSL: yes, DNS: threads, charset: no

Centos 6

ill try znc -D soon

yes because i tried the webadmin with my browser too. webadmin on 4096 didnt work but it did on 2048. znc just seemed completely inaccessible with 4096. <_status> ZNC 1.6.1 - http://znc.in <_status> IPv6: yes, SSL: yes, DNS: threads, charset: no Centos 6 ill try znc -D soon <!-- github-comment-id:139737370 -->
Author
Owner

ok i feel really stupid now
[2015-09-13 01:01:04.890403] src/Csocket.cpp:1680 Error with PEM file [/home/brr/.znc/znc.pem]
[2015-09-13 01:01:04.890449] src/Csocket.cpp:602 at src/Csocket.cpp:1681
[2015-09-13 01:01:04.890476] src/Csocket.cpp:607 error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch

i tried some other certs and its working now. so i mustve made a mistake when creating the pem file for my domain which i just cat'd into znc.pem or something. signed 4096 certs for other domains are working with znc so it was just an issue with one of them. :|

ok i feel really stupid now [2015-09-13 01:01:04.890403] src/Csocket.cpp:1680 Error with PEM file [/home/brr/.znc/znc.pem] [2015-09-13 01:01:04.890449] src/Csocket.cpp:602 at src/Csocket.cpp:1681 [2015-09-13 01:01:04.890476] src/Csocket.cpp:607 error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch i tried some other certs and its working now. so i mustve made a mistake when creating the pem file for my domain which i just cat'd into znc.pem or something. signed 4096 certs for other domains are working with znc so it was just an issue with one of them. :| <!-- github-comment-id:139783271 -->
Author
Owner

At least it wasn't a bug or nothing serious and thank you for pointing to making #1082 :)

At least it wasn't a bug or nothing serious and thank you for pointing to making #1082 :) <!-- github-comment-id:139819509 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#573