Error Generating Certificate and Configuring Apache During Smart Connect Server 7.5.9 Installation on Docker

Hi All,

I am encountering an issue during the installation of Smart Connect Server 7.5.9 in a Docker environment. The error occurs when starting the frontend service, specifically during the SSL certificate generation process, which prevents Apache from running properly. Below are the log details:

/usr/local/bin/generate-certificate: generating new certificate  
ecparam: Can't open "/usr/local/apache2/conf/server.key" for writing, Is a directory  
Could not read private key from /usr/local/apache2/conf/server.key  
chmod: changing permissions of '/usr/local/apache2/conf/server.key': Operation not permitted  
chmod: changing permissions of '/usr/local/apache2/conf/server.crt': Operation not permitted  
/usr/local/bin/generate-certificate: generated /usr/local/apache2/conf/server.key and /usr/local/apache2/conf/server.crt  
AH00526: Syntax error on line 44 of /usr/local/apache2/conf/extra/httpd-vhosts.conf:  
SSLCertificateFile: file '/usr/local/apache2/conf/server.crt' does not exist or is empty

Key Observations:

  1. Permissions: The system returns permission errors when attempting to create or modify the server.key and server.crt files.
  2. Directory Structure: The path /usr/local/apache2/conf/server.key is being interpreted as a directory, which might indicate a misconfiguration in the Docker volume or the certificate generation script.
  3. Apache Configuration: Line 44 of the httpd-vhosts.conf file points to a certificate that does not exist or is empty, causing Apache to fail on startup.

I would appreciate any guidance or recommended adjustments to resolve this issue during the installation of Smart Connect Server 7.5.9 on Docker.

Thank you for your support.

Best regards,

Hermenegildo.

I had the same problem and solved it change permission to certificate.
In ubuntu I use this command:
sudo chmod 777 -R path/to/certificates (./7.5.9/apache2)

Hi Daniel,

Thanks for your suggestion! I’ll try changing the certificate permissions as you mentioned and see if it resolves the issue. I appreciate your help.

Kind regards,

Hermenegildo.