CUPS broken in current testing build 170

The error_log shows:

Unable to encrypt connection: Unable to create server credentials.

I tested this issue on 4 different systems with the exact same error.

Using the cups web interface only works without encryption.

Hi Thomas - Welcome to the IPFire Community!

I just installed CUPS via Pakfire on IPFire 2.27 (x86_64) - Core-Update 170 Development Build: master/ef7d41ef and all works OK.

I looked in the /var/log/httpd/error_log and did not see anything. So I am guessing you see this after you’ve installed CUPS and you tried to use it.

Where did you see this error?

Can you post a screenshot or a picture of what you see?

(I am going on a tangent AND I am thinking out loud)

I wonder if this has anything to do with messagebus not running (and can not be started)?

https://bugzilla.ipfire.org/show_bug.cgi?id=12916

The error occurs as soon as you open the admin part of the webinterface, so using cups without an encrypted connection does not reproduce this issue here.

The messagebus error does not interfere here, since cups still works on the latest stable build even with this error.

please send a screenshot of what you see.

And please send a screenshot of the error_log

Browser:

error_log:

E [01/Sep/2022:00:08:42 +0200] [Client 606] Unable to encrypt connection: Unable to create server credentials.
E [01/Sep/2022:00:08:44 +0200] [Client 608] Unable to encrypt connection: Unable to create server credentials.
E [01/Sep/2022:00:08:45 +0200] [Client 609] Unable to encrypt connection: Unable to create server credentials.
[…]

There were recent changes to CUPS.

I opened a bug report:
https://bugzilla.ipfire.org/show_bug.cgi?id=12924

3 Likes

Just for the record: a downgrade on version 2.4.1 works :+1:

I am curious - How did you downgrade?

Just use pakfire in IPFire’s webfrontend and switch back to the stable repo first, uninstall cups, hit the refresh button and install it again. You now have a working 2.4.1 release installed again :slight_smile:

1 Like

Ahh! got it!

I noticed an update for cups today with encryption deactivated, but it is still broken since the necessary encrypted connections to the printer cannot be established. So turning off encryption is not a working workaround.