mod_rewrite (not .htaccess) conf not loading

[4pples]

Hi,

Using cpanel v92.0.10, CENTOS 7.9.

I’m having issues getting mod_rewrite to load my .conf. Can anyone please help me figure out how to debug this further to see where the issue is?

rewrite is enabled on apache2. The Include related to loading .conf (/etc/apache2/conf.d/userdata/ssl/2_4/domain/domain.com/.conf) is uncommented. There is a file at that location. I did a rebuild + restart. Still nothing.

I’ve also added LogLevel alert rewrite:trace8 to the /userdata conf and have a tail -f running on /var/log/apache2/error_log, reload the page in question and nothing appears in tail.

I've checked /usr/local/apache/domlogs, no luck.

Any ideas where one might look please?

Thank you

 

[4pples]

Seems that the correct directory is /std/ not /ssl/.

 

[RoseHosting]

Seems that the correct directory is /std/ not /ssl/.

If you navigate your site in HTTP mode, then you need to edit the file under /std/, and in /ssl/ if you want it to work when navigating the site in HTTPS.

 

[4pples]

If you navigate your site in HTTP mode, then you need to edit the file under /std/, and in /ssl/ if you want it to work when navigating the site in HTTPS.

So one would think! But it turned out to not be the case.

 

[cPRex]

Can you explain more about the std vs ssl? Those definitely correspond to insecure/secure vhosts so I'd be happy to do more testing on my end if you let me know what you're seeing.

 

[4pples]

hi @cPRex. What kind of info can I provide?

 

[cPRex]

Earlier you mentioned the std and ssl include files didn't seem to correspond to the secure and insecure access in the browser. If you had some details on how I could reproduce that I can do some testing on my end, and file a case with our developers if necessary.

 

[4pples]

I'm running a pretty standard / new DigitalOcean droplet with the following:

cPanel & WHM® 82.0.15 on CentOS 7.6

cPanel has been upgraded to v92.0.11) and CENTOS to 7.9kvm

Doubt it makes a difference, but this is in SFO.

Let me know if I can provide any other details?

 

[cPRex]

Mostly I'd be interested in what you're placing in the include files and how you're testing those. If that isn't information you can post publicly you can open a ticket with our team and we can do more testing on that for you.

 

[4pples]

In the end, it wasn't the include file at issue. It was apache (httpd.conf?) looking in the wrong place.

Meaning, for the vhost conf for the SSL version of my site, it was completely ignoring my Include directive (which was pointing to /ssl). And for the standard :80 vhost conf in the same file, THAT include directory _was_ working, both for http and https.

Does that make sense?

 

[cPRex]

Interesting - I can't say I've seen that behavior in the past. If you'd like to open a ticket with our team we're always interested in checking things like that.