Error 500 caused by Filesafe plugin by seyDesign


(Marcia Kwarsick) #1

Google has informed me of some error 500’s. I see in my Google Search Console they are being caused by the filesafe plugin. I no longer use filesafe on my site, so I’m not sure why I’m getting this error. I went into my Control panel and found the FileSafeDownload.log and sdFileSafeDownload.php still in the folder. Can I delete these files to keep from getting the errors? Is there anything else I should do? Thanks for the help.


(Rob D) #2

I am pretty sure that if you don’t use FileSafe, you can delete both items. To be absolutely sure, I would get in touch with @willwood, who is the current developer of FileSafe. He may be able to give you some additional insight on the topic.


(Will Woodgate) #3

FileSafe is not developed by me. Tom Bristol is the developer.


(Doug Bennett) #4

I don’t have Filesafe but I’m not sure why having any files on the server that aren’t used would cause an internal server error (500).

Do you actually get a 500 error on the website yourself or is it just something on a google report?

If you actually get the error yourself then you could simply backup the files to your Mac and delete them off the server and test to see if the problem goes away. I would also suggest you test everything out to make sure deleting the files didn’t break something else.

You said Google Search Console is indicating the 500’s are being caused by the filesafe plugin, what does the console report say? perhaps a screenshot of the console report would help us out.


(Rob D) #5

Sorry for that…


(Marcia Kwarsick) #6

When I go to the webpage I don’t get any errors. When I click the links that are on the google console I do get the error. I’ve linked one here. Attached are screenshots. I’ve gone several years without an error. I don’t know why these 4 showed up. I deleted Filesafe from this page 4 months ago. I’ve been doing some reading and I’m thinking I may need to install a redirect to my https. (Which I don’t really know how to do.) FYI, I’m not a web developer, I built my site in 2014 with RW6 which I’m still using. My host is Chillidog. Thanks for the help. (PS. I’ve not deleted anything.)


(Doug Bennett) #7

OK, I’m assuming that you no longer have any old links on your site to these old URL’s

The simplest way to “get rid” of the old references that are somehow hanging around would be to do the redirects.
An htaccess rule would do the trick:

RewriteEngine On
RewriteRule ^ringtones/index_files/sdFileSafeDownload.php.*$ http://www.einsteinparrot.com/ringtones/? [R=410,L]

This Rule should “redirect” any links to these 4 URL’s to the home page, more critical I set them up as a return code 410 (Gone) that tells search engines to stop looking for these pages. It might take some time for them to be Dropped by google console.

RW8 has an htaccess editor built in, but you said you are using RW6. You can create a .htaccess File with any Plain Text editor. The name of the file must start with a .. That makes it tricky because any file that begins with a . will be invisible by default.
The file must be named .htaccess , must be Plain Text and must be placed in the root directory of the server.


(Marcia Kwarsick) #8

Thanks! for that!

I have an .htaccess file already in my root directory where I have placed some 301 redirects. Do I just place the one you sent at the top of the page?

Also, do you think I should include a redirect to https? As I’m getting a “Not secure” URL message on my http. (On Chrome) From the reading I’ve done it should look like this???

RewriteEngine On
RewriteCond %{HTTP_HOST} ^einsteinparrot.com [NC]
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]


(Doug Bennett) #9

Not knowing exactly what you have in the htaccess file already it’s hard to say for sure.

The following should work for both if you added it to the bottom of the current htaccess file:

RewriteEngine on
RewriteRule ^ringtones/index_files/sdFileSafeDownload.php.*$ http://www.einsteinparrot.com/ringtones/? [R=410,L]
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

If the current file has a RewriteEngine on directive already than you can remvoe it(you only need one).


(Marcia Kwarsick) #10

Thank you so much! I’ll give it a try.


(Marcia Kwarsick) #11

Redirect to https worked great! Thanks you so much! Will monitor for errors.


(system) #12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.