Web server issue on Raspberry Pi 4

[avanty42]

Problem Description

I’ve recently bought a Raspberry Pi 4 and installed sympl. Initially, the web server worked, but now it’s stopped working.

Any Error Messages

[Fri Nov 03 10:50:07.766634 2023] [ssl:emerg] [pid 144368] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/zz-mass-hosting.error.log for more information
AH00016: Configuration Failed
[Fri Nov 03 10:52:04.875001 2023] [ssl:emerg] [pid 144477] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/zz-mass-hosting.error.log for more information
AH00016: Configuration Failed
[Fri Nov 03 10:52:07.165145 2023] [ssl:emerg] [pid 144504] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/zz-mass-hosting.error.log for more information
AH00016: Configuration Failed

[Fri Nov 03 10:50:07.766447 2023] [ssl:emerg] [pid 144368] AH01958: SSLStapling: no stapling cache available
[Fri Nov 03 10:52:04.874799 2023] [ssl:emerg] [pid 144477] AH01958: SSLStapling: no stapling cache available
[Fri Nov 03 10:52:07.164925 2023] [ssl:emerg] [pid 144504] AH01958: SSLStapling: no stapling cache available

Environment

• Sympl Version: 12.2
• Sympl Testing Version? No
• Debian Version: 12.2
• Hardware Type? Pi 4

[techwilk]

Looks like this is the same issue from these other two threads.

Solution:

Seems a little broken

I’m reasonably certain I’ve found the problem, and im working on pushing a new package out with a fix now. In the mean time, after installing sympl normally, manually this to enable the missing part of the configuration: sudo a2enconf sympl-web sudo service apache2 stop sudo service apache2 start It’ll take a while for the potential fixes to come down the pipeline with new packages, and I will also need to re-replicate the issue to confirm before they’re pushed to stable, but this should deal…

The fix:

Seems a little broken

I’ve fast-tracked the fix for this now, along with some other small fixes which were pending. This bug will only have affected new installs, and meant that the relevant part of the config which sets up SSL Stapling wasn’t enabled properly, but old/upgraded installs would have been fine. This wasn’t picked up because the testing didn’t automatically pick up a new LE cert and force applying it, because the VMs used for testing don’t persist, and we could quickly hit Let’s Encrypt rate limits. I…

See also:

Problem with zz-mass-hosting.ssl.conf

(Just to mention, I’ve split this into it’s own topic under support, and contacted @tricky for some more info to see if I can identify the issue, although I don’t think it’s related to the other recent issue with new installs.)

[avanty42]

I did try to search for existing threads about the issue, but missed those.

Updating appears to have fixed the issue