Support

 I got a notice from Watchfuli that my .htaccess file had been changed.

When I did a file compare it looked like the following lines had been added in several places

RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$

I changed it back to how it was the day before & notified my hosting company Rochen & asked them if they had altered the htaccess file.

They said this

"Thank you for contacting Rochen. This file was modified automatically by cPanel as a part of the new "AutoSSL" feature which was introduced in a recent release. The system automatically tried to perform domain control validation on your domain parkcherchase.com, but this ultimately failed as your site issued a redirect instead of directly serving the new file that was created (83A8EC9F95DD9448D5BD2F3153E6E57C.txt). "

I am attaching the 2 versions of the htaccess file (Nov 13 version created by Admin Tools, Nov 15 version changed by cpanel)

I don't understand why it was changed by cpanel or if I need to add those 2 lines in the htaccess maker text box so the code doesn't get removed if I run teh Admin Tools htaccess maker again.

I also found this https://features.cpanel.net/topic/ability-to-prevent-autossl-editing-htaccess-fles

But I'm afraid I don't understand all of it & what I need to do to htaccess Maker to make sure my website works correctly.

Thank you for any advice you can provide.

Hi Davide,

The contents of the 83A8EC9F95DD9448D5BD2F3153E6E57C.txt file are

c23d70278dc07db45c3439ea7d57aae0b6e827a8
comodoca.com

Does this mean I should add the 83A8EC9F95DD9448D5BD2F3153E6E57C.txt file to Admin Tools htaccess Maker Exceptions>Allow direct access to these files ? Then create a new htaccess file using htaccess Maker?

If so should I just add "83A8EC9F95DD9448D5BD2F3153E6E57C.txt" (without quotes) to teh Exceptions>Allow direct access to these files without a leading forward slash?

Thank you for your help with this.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.