Skip to content
English
Manage and Create Tickets
  • There are no suggestions because the search field is empty.

FileCloud Portals Inaccessible After Upgrade Due to Apache 000-default.conf Configuration Reset

Original Question or Issue:

 After upgrading the FileCloud environment and rebooting the server, both the Admin and User Portals became inaccessible. The customer reported browser errors and Apache log entries showing an APR version mismatch with ModSecurity. Further investigation revealed that the live Apache 000-default.conf configuration had changed during the upgrade and was missing the required HTTPS (*:443) VirtualHost configuration. 

Environment:

  • Product - FileCloud Server
  • Version - 23.262
  • Platform - Linux

Steps to Reproduce:

  • Upgrade the FileCloud environment.
  • Reboot the server.
  • Attempt to access the Admin or User Portal.
  • Both portals fail to load.
  • Review /etc/apache2/sites-enabled/000-default.conf.
  • Compare the current configuration with the pre-upgrade backup.

Error or Log Message:

Apache was listening on port 443, but apachectl -S did not show an HTTPS VirtualHost. The customer also observed:

ModSecurity: APR compiled version="1.7.0"; loaded version="1.7.2"

The HTTPS connection returned:

SSL routines::wrong version number

Defect or Enhancement Number:

 

Cause:

 The upgrade replaced/modified the Apache 000-default.conf configuration. The current configuration no longer contained the customer's custom *:443 VirtualHost, including the SSLEngine On and SSL certificate/key configuration. As a result, Apache was not serving the HTTPS configuration required by the FileCloud portals. 

Resolution or Workaround:

Instructed to rename the new 000-default.conf and restore the pre-upgrade configuration as 000-default.conf, then restart Apache using:

systemctl restart apache2

After restoring the previous configuration and restarting Apache, both the Admin and User Portals became accessible.

Notes: