Skip to main content

mod_rewrite (not .htaccess) conf not loading

Comments

10 comments

  • 4pples
    Seems that the correct directory is /std/ not /ssl/.
    0
  • 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.
    0
  • 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.
    0
  • cPRex Jurassic Moderator
    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.
    0
  • 4pples
    hi @cPRex. What kind of info can I provide?
    0
  • cPRex Jurassic Moderator
    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.
    0
  • 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?
    0
  • cPRex Jurassic Moderator
    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.
    0
  • 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?
    0
  • cPRex Jurassic Moderator
    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.
    0

Please sign in to leave a comment.