Today I ran into an odd error on my foreman server. I had enabled auto-updates on Rocky Linux, and overnight httpd got updated. Today I found my foreman unresponsive, or rather: refusing to connect.
Well in fact the foreman was fine, but the httpd service (Apache2) did not start giving out that line above. Typical error when there are multiple ssl configurations pointing to that port.
The solution was to run the foreman installer again without any arguments:
$ <strong>foreman-installer</strong>This uses puppet in the background to recreate the required configurations, and indeed the service worked afterwards again. Turns out that the ssl.conf was added by the upgrade, but is actually in the way.
-rw-r--r--. 1 root root 3353 Feb 27 16:02 05-foreman.conf<br>drwxr-xr-x. 2 root root 4096 Feb 27 16:02 05-foreman.d<br>-rw-r--r--. 1 root root 4028 Jun 5 15:42 05-foreman-ssl.conf<br>drwxr-xr-x. 2 root root 4096 Feb 27 16:02 05-foreman-ssl.dAll sorted, back to business.
Happy coding!
Author Profile
Latest entries
blog23.01.2026Puppet with Foreman – Installation- blog20.01.2026ConfDroid Puppet Modules – Pilot
blog19.01.2026ConfDroid Forge – Pilot- blog16.01.2026Puppet with Foreman – Infrastructure
Categories:
