Update proof configurations

My CWP install is behind a gateway device so all logged IP's are 192.168.1.1. Because of a CWP bug (don't know if it was ever fixed), I am using Nginx & Varnish & Apache.

Before updating (which update I do not know), I had my CWP set up to log the client IP's. It was using mod_rpaf with x-forward but it seems an update has removed the mod_rpaf option from the control panel.

What is the proper way to setup client IP logging so that the custom config does not get blown away by a future update?

I understand that CWP now has a vhost template editor/switcher but I don't see that same type of functionality being offered for server config files such as Apache's 'httpd.conf' file.

So, for example, if I want to enable an Apache module (that is not enabled by default) such as 'mod_remoteip.so', do I have to manually edit the 'httpd.conf' file every time I rebuild Apache or is there a better way?

OK... The cloud has lifted. I now understand the changes to the way templates and configs are handled in CWP.

In order to edit the main server config, you simply create a new config file and add your edits to it. That file will be included, automatically.

I did encounter a small bug. I get the following error when creating a new config file in CWP->WebServer Settings->WebServers Conf Editor->Apache->conf.d

Code: [Select]

Notice: Undefined variable: file_size in /usr/local/cwpsrv/htdocs/resources/admin/modules/file_editor.php on line 0Although the file was successfully created.