This question already has an answer here:

I sometime get Store Debug Information saying some attempted access to install.php. Is is better to delete/rename install.php?

URL: http://mywebsite.com/install.php
IP Address: 

#0 /app/code/core/Mage/Core/Model/App.php(861): Mage_Core_Model_App->throwStoreException()
#1 /app/code/core/Mage/Core/Model/App.php(502): Mage_Core_Model_App->getStore()
#2 /app/code/core/Mage/Core/Model/App.php(285): Mage_Core_Model_App->_initCurrentStore('default', 'store')
#3 /app/Mage.php(616): Mage_Core_Model_App->init('default', 'store', Array)
#4 /install.php(129): Mage::app('default')
#5 {main}

marked as duplicate by Anna Völkl, Fabian Schmengler, Community Aug 5 '16 at 11:49

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Yes, you can remove install.php from your production server. – Anna Völkl Aug 5 '16 at 11:13

You can block install.php access by adding following line to .htaccess on magento's root directory

<Files install.php>
    order allow,deny
    deny from all
  • Can be removed, see here: magento.stackexchange.com/questions/82042/… – Anna Völkl Aug 5 '16 at 12:02
  • Yes you can remove, but why remove if we have option to make this unavailable for everyone. All magento files will remain same and there will be no issue while applying patch if any patch released for install.php – Gulshan Maurya Aug 5 '16 at 12:10
  • I see what you're talking about. Actually I am speaking of leaving the file in the development system but do not deploy it to production. – Anna Völkl Aug 5 '16 at 12:53

Not the answer you're looking for? Browse other questions tagged or ask your own question.