Jump to content

Smarty Error: unable to read resource


WorldWideWebDev

Recommended Posts

The last two clients ive had join up have done so with questionable names and contact information. when i check the logs the reveal this :-

 

17/10/2013 20:18

Smarty Error: unable to read resource: "/var/www/vhosts/worldwidewebs.com.au/httpdocs/billing/templates/RackHost/clientareasecurity.tpl"

Client 119.18.155.82

 

 

The other client was :-

 

11/10/2013 05:13

Smarty Error: unable to read resource: "/var/www/vhosts/worldwidewebs.com.au/httpdocs/billing/templates/RackHost/clientareasecurity.tpl"

Client 41.107.107.69

11/10/2013 05:13

Smarty Error: unable to read resource: "/var/www/vhosts/worldwidewebs.com.au/httpdocs/billing/templates/RackHost/clientareasecurity.tpl"

Client 41.107.107.69

11/10/2013 05:03

Smarty Error: unable to read resource: "/var/www/vhosts/worldwidewebs.com.au/httpdocs/billing/templates/RackHost/clientareasecurity.tpl"

Client 178.32.244.27

 

What are they doing to come up with this error and does anyone know if its an issue??

Link to comment
Share on other sites

"/var/www/vhosts/worldwidewebs.com.au/httpdocs/billing/templates/RackHost/clientareasecurity.tpl"

It looks like they might be trying to read your templates, by guessing at folder names and locations. If you haven't already, you should be able to prevent reading of your tpl files with .htaccess.

 

Put this in an .htaccess file in any directory that covers WHMCS in your install (if your server allows htaccess and so on):

<Files "*.tpl">
Order Allow,Deny
Deny from All
</Files>

Link to comment
Share on other sites

It's a great idea to use that code to block access to these files but I don't think it's caused by visiting the files directly as I've seen the error on my WHMCS installs for years and have this code installed to stop the ability to visit .tpl files directly.

 

It's also a good idea to add a index.php file to every directory of your WHMCS template. This stops the ability to view a list of containing files in a directory if not already disabled by the server.

Link to comment
Share on other sites

It's also a good idea to add a index.php file to every directory of your WHMCS template. This stops the ability to view a list of containing files in a directory if not already disabled by the server.

Simple enough to add a line to your root .htaccess for your site with this:

Options -Indexes

 

No need for index files. ;)

Link to comment
Share on other sites

Hi Zomex, it doesnt appear to cause any issue other than show up in logs, but im a bit paranoid of late...

Index.php in every folder. Simple and effective..

I cant view any tpl files through internet explorer, it just shows a blank. Thats why i thought it may be some sort of hack from within WHMCS..

 

I had a look in the directory , the .tpl file in this template did not exist.

I looked at the original custom template which i purchased to see, but this template never had a clientareasecurity.tpl.

I looked at the default template to see if this had its own clientareasecurity.tpl and it did , so i have copied the tpl file and placed it in my custom RackHost template folder. (And hope to a higher power it doesn't cause more problems and the log error disappears. )

 

 

Bear, i have to look into this .htaccess file a bit more. I have not set one up but it seems its the way to go.

 

Thanks for the tip guys, i have plenty to do...

Cheers

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated