I'm running Magento 1.7.0.0 multistore and a few times a day I get the famous "Internal Server Error 500" in my browser.
When navigating to Magento backend or a different Magento Storeview, the backend and the Storeview are still available and show no Internal Server Error.
Visiting the homepage or any category page, product page or cms page doesn't make a difference.
After flushing /var/sessions, the frontend is available again.
So, what I've done already:
I think it's not related to permissions, as these are set properly. I ran Magento-Cleanup.php a few times, and that's not changing or helping.
I checked settings in htaccess. These seem to be good.
SID is off. With or without SID doesn't make a difference
Logs show no issues that could cause this.
Help!
Can you change your PHP setting to use Apache rather than fastCGI? I've seen this error before with FastCGI on some servers
Related
I'm getting this issue with categories in Magento 1.9, Issues basically to do with Categories page and product > categories.
My site is not new and it has suddenly happened, the only recent events are style changes and few template changes to product gallery (media.phtml).
Im stuck on categories loading... I even left it over night.
image screenshot
It's a nightmare.
I have no console errors except for GET https://www.SITENAME.com/skin/adminhtml/base/default/fonts/fontawesome/font-awesome.css net::ERR_ABORTED which being fontawesome I feel is not related to this.
Has anyone else had this and found a solution?
One suggestion I found was to change mod security in cpanel. I can't change mod security as my cpanel/whm doesn't have that option, possibly as this issues was 4 years ago.
Please save me!?
Below are some fixes that help you to resolve the issue:
Try a different browser.
Disable mod_security and add whitelist: Check your mod_security audit log and if you see entries from the admin backend, have your host investigate and temporarily disable the module. If your issues goes away, ask your host to whitelist your admin backend.
Check your www vs. no www redirects: Make sure you’re only using one form of redirection, either in cPanel, Magento, or .htaccess.
A Magento website is down in IE and in Firefox. Magento provides the following message: "There has been an error processing your request. Exception printing is disabled by default for security reasons."
However using Ctrl+F5 makes the site work.
The site works in Chrome and in Opera.
It also works if any page is requested other than the home page.
The error in the magento file in var/report lists:
a:4:{i:0;s:108:"SQLSTATE[HY000] [1203] User XXXXXXX already has more than 'max_user_connections' active
However it still works in chrome.
You have a problem with your database; Basically your database is hitting the limit for the amount of connections for that user. Check what your max_user_connections setting is at and increase it.
Be careful, as the higher that number, the more resources it will use. You have to find an even balance.
It was not a problem with Magento or the database. The web host was incorrectly caching the site. We found out when a file I uploaded still appeared in cPanel yet the file had been deleted several minutes before.
The web host flushed their cache of the site. The website immediately loaded without any error.
We have been unable to log in to our magento admin panel for a few months now, but this isn't a standard 404 issue.
After logging in with correct username/password, we get redirected to a 404 page. The strange thing is, it only happens from office WIFI, not over 4G or at our developers office. This occurs on our dev server, not live (live logs in just fine)
Our developers have tried creating a new development environment on a new server but the issue is still occurring.
I have tried disabling all firewalls and cannot see anything in router settings which would cause this, anyone had a similar issue or can suggest a solution?
Check your .xml files. You might been redirected to another module url showing the 404 error and check if module is currently actived. This would explain why you still have the same issue even when you're changing server, house, country etc etc.
I know that that similar issues and topics exist, however my issue differs slightly and none of the proposed fixes have worked.
I was accessing the Magento backend as normal. Approximately 10 minutes after that I could no longer access the Magento backend.
What I mean is that when I go to the admin url login page, I get a 404. However the 404 isn't generated by my host, it's generated by my webstore.
Everything about my webstore works as normal.
I've seen a number of fixes, mainly this one...
http://www.magentocommerce.com/boards/viewthread/207981/#t274443
I have a few main issues.
Admin Custom URL had been set (but not by me). It was set over a year ago when Magento was installed. It worked entirely fine until today.
I do not even have "admin/url/custom" and "admin/url/use_custom" in my "core_config_data" PHP table. It simply does not exist so I cannot change it. I looked manually for it and did a search for it. Nothing.
I tried updating the local.xml file and clearing "var/caches" and "var/sessions" but that did not work either.
I've been working this for hours and it's beyond frustrating. It's imperative that this be fixed ASAP because we are a fairly sizeable company.
Thanks ahead for helping. Anything at all would be appreciated.
First Check your Apache configurations
I know that you said you were only in the Magento admin but I would first check that apache was configured correctly. This is the first point of contact and you need to ensure that it's working right.
You need to locate a default Magento htaccess file that you can upload to your server. There's additional configurations that you need to make if you're in a subdirectory and also check to make sure that your mod_rewrite is working properly. There's an extensive tutorial on these things here, magento htaccess.
Make sure that you have the right magento admin url
I have to assume that you know what your magento admin url is, but of course I would double check that you're getting it right. There is an option in the admin area to change the admin url, you could have adjusted that on accident.
You say that you don't have "admin/url/custom" and "admin/url/use_custom" in your core_config_data table. This actually means that you didn't set the magento admin url from the admin area. However there is a third place that you can look for your admin url. This is in app/etc/local.xml but you couldn't have changed this from the administration area.
Did you turn off search engine friendly urls?
If you had been accessing your administrative area using /admin and then accidentally turned off SEF urls, then your admin area could have just simply moved to /index.php/admin. Of course you mentioned that you have a custom admin url, but I don't know what that is, so I'm giving examples with the default.
I can't really give you any more suggestions without more information. I hope that this helps!
Found this and thought I would post here since it shows up in google.
http://sourcelibrary.org/2011/05/19/magento-404-page-not-found-error-for-admin-panel-access/#comment-8444
I have a magento install on a staging environment, everything is working except the catalog backend page and the frontend layered navigation. Look at the image below. There is a backend within the backend. When visiting the page it refreshes to infinity. See this identical problem
My first guess is there is a bug in the template file but an identical template file on my local machine does not cause any issues. Additionally the database between my local and staging site are identical minus the core_config_url. The only difference is local I am running Apache and on staging I am running nginx.
The second issue which I imagine is related is that the filters on the frontend catalog page dont work. They are visible but clicking on them reloads the page without changing the products.
Any help would be appreciated. Thanks
UPDATE: After switching from NGINX to Apache the issue disappeared. I still would like to figure out what is causing the problem
I take for granted that you had already tried different browsers/clearing your browser cache and Magento cache (empty the cache directory), etc.
Are you sure you put the correct value in the cookie_domain setting? Many users that had your same problem seem to have setted up an incorrect value in that setting.
Take a look here and let me know.
I have found that usually this is caused by a server-side error on the ajax request. If there is any kind of error response returned, it will just continue to spin. Either check your Chrome console for a 500 response, or look in your server's error logs.