Unexpected changes made to httpd-custom.conf

Support
1

Description

Some time ago I added a couple custom VirtualHost blocks to /etc/httpd/conf/httpd-custom.conf, with the expectation that this was an appropriate place to add custom Apache configuration (as suggested by docs). I woke up this morning to find that every ServerName directive in the file had been rewritten with the server’s main hostname.

Am I misunderstanding how to customize Apache, or should this file remain untouched?

Steps to Reproduce

Please provide detailed steps to reproduce the bug. Include any necessary code snippets, commands, or configuration files.

  • Add a custom VirtualHost block to /etc/httpd/conf/httpd-custom.conf with various ServerName directives.
  • Wait for ApisCP update or monthly check (not sure).

Expected Behavior

I would expect no change to httpd-custom.conf.

Actual Behavior

ServerName directives were rewritten.

Environment

ApisCP version: cpcmd misc:cp-version

revision: efe49da72b896985bcedb83bee3bfcae6a383c4b
timestamp: 1741108131
ver_maj: 3
ver_min: 2
ver_patch: 46
ver_pre: ''
dirty: false
debug: false

Operating System: uname -r
4.18.0-553.44.1.el8_10.x86_64

2

To avoid rewriting the ServerName, locate these VirtualHost blocks in /etc/httpd/conf/apnscp-amendments.conf or /etc/httpd/conf.d/X.conf; all files that end in .conf are sourced within that directory.