Magento: 500 Internal server error in admin - magento

I keep getting the 500 internal server error. I getting 500 internal server error when I am importing customer records by csv file from magento admin side. I can't found any solution. I have given the 755 permission to all the required files and folders of magento. How i can resolve this error, any one have idea for this solution.

.htaccess by default in Magento has this options disabled that are specific to 1and1 hosting, I would try enabling them:
#AddType x-mapp-php5 .php
#AddHandler x-mapp-php5 .php
You may also want to read over:
http://www.magentocommerce.com/boards/viewthread/2019/
http://www.magentocommerce.com/boards/viewthread/199907/

You should find the server "var/log" but not inside the magento's "var/log"
because this is the server error - 500 internal server
For my experience, it seems the php process is out of memory during importing/exporting data.
Also there are few other reasons about the settings,
e.g. max. post variables are out of limit, upload file size exceed limit , you may check the server log to know what is the exact problem.

Try enable the logging
System - Configuration - Developer - Log Setting

Related

Internal Server Error: Laravel CentOs 7

I have uploaded my Laravel Project on the Server which CentOs 7.
But after migrating the project i got the Error as shown in following screenshot:
I have Clear the Cache, also allow the permission to storage folder and update the composer and i have tried Many Stuff in order to solve but unfortunately none of them work form me.
Your Effort will be appreciated.
Thanks,
The HyperText Transfer Protocol (HTTP) 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
This error response is a generic "catch-all" response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.
You can have problem in your code that server can not parse it.
You should enable .htaccess by adding this to your vhost:
Directory /var/www/html/yourfoldername
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
Then disable SELinux permanently:
https://www.tecmint.com/disable-selinux-temporarily-permanently-in-centos-rhel-fedora/
Try to Fix 500 Internal Server Error: - change FollowSymLinks to SymLinksIfOwnerMatch in .htaccess files.

Error 500 after login to admin

I have my url set to www.YourDomain.com/store and log in via www.YourDomain.com/store/index.php/admin or www.YourDomain.com/store/admin in to the dashboard but whe I log in the first time I always get a internal server error . Once I refresh I have no issues till I would say the next session
Any one has a suggestions how to fix this ? I don't have the issue on my Local
TX
C
Increase the memory limit from .htaccess file. Thats the main issue may be. check for this variable in .htaccess in magento root php_value memory_limit

500 internal server error on virtual hosting magento

I am running magento sites on virtual host.All are working properly except one where on product saving it shows me 500 error.I search and did alot of techniques but couldn't succeed.Can anyone tell me that either this is my side issue or server side.I check magento logs but no error or exception.Only on product save it show me the error.Thanks I also enable rewrites from htaccess.
While watching var/reports i found two types of errors in all files:
SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction
SQLSTATE[42000] [1044] Access denied for user 'magento'#'%' to database

An unrecoverable error occurred. The uploaded file likely exceeded the maximum file size (2 MB) that this server supports

Ok I got Drupal 7.19, mySQL 5.1.66-cll PHP 5.3.21
Now I searched for he above error and found various answers of various age, however it doesn't address, my problem.
I get the error for any file bigger than 100k
went through php.ini settings.php as well as account settings, which is now 5000k.
and max post and max file are way higher.
The site has only 2 image fields, the original as well as one other. It doesn't matter which one is used in a content, the field settings for the original one were never changed and the themed installation came with images larger than 500k.
While for the time I can live with resizing images before uploading, it nevertheless is a pain in the .... and I really would appreciate any help.
I had a similar problem which i resolved via the php.ini file as well as the apache mod_security user.conf file.
My httpd is apache2, which has mod_security enabled, which also did not allow me to upload over 100k image file in Drupal. Apparently this is a common problem for the web-hosting provider (liquid web) because it took no more than 3 minutes to resolve.
First the php.ini file was altered (on CentOS it is in /usr/local/lib/) with lines:
;upload_tmp_dir = /tmp (yes it has a semi-colon at the start)
and also the line:
session.save_path = "/tmp"
Second file that was altered is the modsec2.user.conf file located on (CentOS) at /usr/local/apache/conf/
(appended at the bottom of the file in the last 2 lines):
SecUploadDir /tmp
SecTmpDir /tmp
Then /etc/init.d/httpd restart (or reload) apache and you should be able to bypass this limit for file uploads by mod_apache if it is enabled. Best of luck and please know that this is my first answer on stack so please be considerate.
just you can request your hosting provider
to added into the sites whitelist.conf file :
<IfModule mod_security2.c>
<LocationMatch .*>
SecRuleRemoveById 340147
</LocationMatch>
</IfModule>

Magento install stops creating database

I've tried win xp and 7
Apache 2.2.19
php-5.3.6 (tried php 5.1.x)
Mysql 5.1.44
The install process runs ok until the database creation screen.
After 1 minute, the process stops at:
http://127.0.0.1/magento/index.php/install/wizard/installDb/
with a BLANK page
The database has only 199 tables (sometimes stops with less tables)
If i refresh the webpage, sometimes more tables are created, but then i get a database error.
Tried to IMPORT the database manually and start the install, but i get an error at the same step!
Also retried the install (deleting the cached data in the Magento folder).
What am i doing wrong?
thanks.
I used to get the same behavior. Other observation is you do not get the blank screen if you are running installation wizard while magento sample data imported to the database.
I did some googling and find the following poge which resolved my issue.
http://www.magentocommerce.com/boards/viewthread/76240/
that is modify apache httpd.conf and add following lines:
Options FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
I would suggest trying to install via the Command Line Interface:
http://www.magentocommerce.com/wiki/groups/227/command_line_installation_wizard
Open the index.php file (at the root) and write the following line at the top
<?php
set_time_limit(0);
?>
Empty the tables in your database and try again. The white page appears because the script times out and when you refresh that same page Magento gives you an error page where it says the table already exists. The SQL script which creates the tables in the database does not check whether the table exists in the database or not.
A blank screen in PHP is a strong sign of running out of memory. Check the memory limit according to the requirements and then maybe add a bit more too.
Change the name localhost file
with any www.example123.com in
c:\Windows\System32\drivers\etc\hosts
and add
127.0.0.1 www.example123.com
after wards follow these steps through this torrent link.
http://tinyurl.com/3r6dpop
After installing some images may not upload so even uploaded the books.
I got blank screen too, and the following error:
[09-Feb-2012 15:27:43] PHP Fatal error: Maximum execution time of 30
seconds exceeded in D:\creation\software
developer\projects\magento\document root\lib\Zend\Db\Statement\Pdo.php
on line 228
I'm pretty sure, that you have execution timeout too...
You have to setup your php.ini, and increase the max_execution_timeout, and in the iis manager you have to increase the fastcgi request and activity timeouts too.

Resources