Custom VirtualHost Directive Syntax

[jayronc]

It appears as though the syntax is YAML. Nowhere in the documentation does it say this, and nowhere does it say how to format your directives for this system. I had a server just switched from apache 1.3 to apache 2.2 and i now have about 15 sites down because this new system absolutely refuses to recognize either of these directives. YES i used the distil command and YES i used the rebuild command. ALL of my other changes get saved, but these do not, meaning every time the smallest edit is made by whm or cpanel ALL of my proxied sites lose their proxy settings.


ProxyPass / http://127.0.0.1:3000
ProxyPassReverse / http://127.0.0.1:3000

HOW do i get around this?

If there is documentation for this syntax please point me in the direction. I find it incredibly disturbing that YAML would be used, without any documentation about how it should be formatted.

[cpanelkenneth]

YAML is only used as the storage format in /var/cpanel/userdata. Add your needed directives in an Include file for the VirtualHosts that need such changes. More information is found here: http://www.cpanel.net/support/docs/e...irectives.html

[jayronc]

Ok after the initial "oh crappppp all my sites are broked!!!" feeling wore off, im finally starting to "GET" the easy apache 3.

i have 3 additional questions.

1. looks like if i know im going to be using ProxyPass and ProxyPassReverse alot on my virtualhosts that i can add them to the /var/cpanel/templates/apache1/vhost.default file and then i can specify these in the userdata/*sitename*.com files. Is there documentation for doing this? I really dont want to add the whole file structure and directories to 30-some sites just for 2 lines each for these directives.

2. I have several SSL hosts hosts that were deleted in the upgrade from WHM 10 to WHM 11. can i add a new files directly to the /var/cpanel/userdata/accountname/sitehost.com_SSL to bring it back?

3. is there a way to generate the httpd.conf somewhere else other than the default location (and overwriting my temporary "band-aid" conf file just for testing purposes while im trying to work this out? Restarting all the sites on a production server every time i generate a new test file is kind of hard on my clients.

Thanks!

[jayronc]

everything works with the exception of one domain that has a wildcard SSL certificate.

it refuses to allow me to add custom directives.

the certificate of the domain is *.jobfinderusa.com

but the easyapache3 include system doesnt allow for a subdomain named *. as shown by this error i got when trying to compile the conf file.

when i add a customdirective to:
/usr/local/apache/userdata/ssl/1/jobfinde/*. jobfinderusa.com/rails.conf

i get this error when compiling:

httpd: wildcard patterns not allowed in Include /usr/local/apache/conf/userdata/ssl/1/jobfinde/*. jobfinderusa.com/*.conf