I have upgraded Magento to 1.9.3.1 from 1.9.1.1 from magento connect manager and after successful up-gradation I got this error:
Exception during cache and session cleaning
When I access my site I got this error:
You have been blocked from accessing this site. If you feel this is a
mistake please email abuse#securedserverspace.com
Which is I think is not a Magento error but more of a server error anyways whatever it is how do I fix it? Please help.
Case 1:
You have to consult with hosting provider.
Case 2: you have doubt regarding code then you can update via following method.
Update to Magento 1.9.3.1 - Via FTP -
1) Enable Maintenance Mode by creating a file in root magento folder called maintenance.flag
2) For admin (you) to have access to the frontpage while you perform upgrade (check everything as it should be)
Find this
$maintenanceFile = 'maintenance.flag';
Add following to line 49 and 50
$ip = $_SERVER['REMOTE_ADDR'];
$allowed = array('Your Ip Address');
Where the ip-address is your IP. Replace line 59 should be
if (file_exists($maintenanceFile)) {
With
if (file_exists($maintenanceFile) && !in_array($ip, $allowed)) {
3) Disable Compiling and also disable cache. Remember to flush cache.
4) Unpack the Magento 1.9.3.1 files on your computer and upload them to your root.
5) Refresh your webpage when the files are uploaded. You can see in Admin section that the magento
has been updated.
NB! Remember to check for upgrades for your third party modules / themes if you have this. This will only upgrade magento.
Also a good idea before uploading the files is to delete the error_log in your root folder and logs under var/log. This way you can see what errors may occur when you have done the proceeding.
Related
Using Magento 2.2.1 freshly installed
I use php 7.1.1
I am using Adyen payment gateway
https://github.com/Adyen/adyen-magento2
the extension developer says its not due to their extension. I have enabled every php extension on server side thats needed. So now it comes to magento 2
Tried to checkout as guest and then I see
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
https://{siteurl.com}/rest/default/V1/guest-carts/1a41b8daeba4d90df7c5dca2085dd732/payment-information
When I try to use COD or Check the checkout process is smooth. Haven't tried with paypal or others
**Can you please help ??
If you need me to perform any steps in either server side or magento 2 please tell me the steps on what to do I will post the output here**
I have solved the issue
Solution : I used a third party extension and installed it through magento 2 admin directly which resulted the extension was not installed properly. I have used composer to install the extension and it solved the issue
I work for Adyen.
It is indeed required to install the Adyen plugin on Magento through Composer. This will include all the dependencies and prevent the issue that is shown here.
For further references you could visit our Github page:
https://github.com/Adyen/adyen-magento2
Hope that it helps!
For the unexpected error (e.g 500), we should enable error reporting on the bootstrap:
app/bootstrap.php
ini_set('display_errors', -1) // enable this line remove # from start.
you will get the real issue on screen
i have a serious problem in Magento Admin Backend. After login its shows a BLANK Page. i used the same files and database in different server, there it was working fine but when i have transferred files into LIVE then Admin issues came. Please help me over this as i got frustrated from last some dayz. If you need any more dertails then plz ask but i need to resolve this soon. Link: http://studywings.com/index.php/admin/
Magento ver: 1.7
flush your magento root /var/cache folder and /var/session folders, It may have previous server session that may cause problems.
Otherwise disable all third party modules and try again. I think this will help
I had the Same problem,
i have also debug the any errors occured, i tried index.php file
ini_set('display_errors', 1);
error_reporting(E_ALL);
$_SERVER['MAGE_IS_DEVELOPER_MODE'] = true;
pleced above code in index.php file. after that i have tried admin login.
showing the errors are session related, header already send errors.
i have to add the code in root/index.php file in top add the following line.
ob_start();
after that tried the login its worked.
Cheers..!
Is url changes to this after click login button or not?
http://yourdomain.com/index.php/admin/index/index/key/(key value)/
if url changes but not not show the dashboard page then go to
app/code/core/Mage/Core/Model/Session/Abstract/Varien.php
make copy of this file
Find the code for setting session cookie parameters these started on line 77
Comment out the final three lines and be sure to remove the comma after $this->getCookie()->getPath(). You should end up with this:
// set session cookie params
session_set_cookie_params(
$this->getCookie()->getLifetime(),
$this->getCookie()->getPath()
// $this->getCookie()->getDomain(),
// $this->getCookie()->isSecure(),
// $this->getCookie()->getHttponly()
also line 104 comment out :
//call_user_func_array('session_set_cookie_params', $cookieParams);
If there is no change in url after click login then try to uncomment display error and see error_log file of your server
I think this problem is due to file permissions. As you added files from one server to another, permissions might be get changed.. Try to give the permissions to all the files. Check this http://www.mage-shop.com/forum/threads/3-Magento-Admin-Backend-Blank-Page-Error
There are a number of things that can cause it, but it's most common after migrating to a new server, last time it happened to me it was an excessively low php memory_limit setting on the new server - the Admin part of the site uses a lot more resources per user than the frontend.
In general when having this issue:
Flush out your cache by emptying var/cache
Clear out sessions by emptying var/sessions
Check the magento error logs/reports for an error code in var\logs and var/reports
Turn on magento error logs in mysql if logging isn't already on! (look in core_config_data for WHERE path like 'dev/log/active'
Check if your php configuration is displaying errors
Check your apache/php error logs for more clues - memory errors will show up here for example
Try this solution
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce
Consider also installing XDebug
Hope this helps you!
Just to complete the other answers....
I am upgrading a magento install, and got the same problem, in the end I had another folder inside of var/
magento/var/minifycache
Only worked after clear deleting the files inside of this folder.
I had the same problem after uninstalling an extension. I thought that clearing cache would be enough, and I did without success... later speaking with the technical team, they commented me that it did not work because I hace memcache installed, and needed to be done the cleaning via system - backend (that i coudl not see...)
When I first started using Magento and I first made a backup, I ticked the "put website into maintenance mode" button. Once this was done when I tried to visit my site I was given a 503 error (I think). I found that this was due to Magento creating a maintenance.flag file.
I've come to understand that this is used to stop people accessing your site when you are updating things or backing up.
Is it possible to use a maintenance.flag file to block people from visiting your site while you're physically updating and checking? I have 2 servers a test and a live server. The live server uses SSL and is much faster than the free testing server that I have. Currently I'm developing changes on the test server and then uploading to the live server once I know it al works and looks OK.
Since we applied the SSL to the live server. Certain things are (or are not) happening when I do updates. I'm wondering if I can temporarily block access to my site while I check my updates then allow people back on.
The maintenance.flag file blocks me out of my site as well so as far as I can understand what I want to do is not possible.
Yes, it's possible to set Maintenance Flag and then have your index.php check for a set of addresses that are let through while serving everyone else a 503 page. Only those systems will be allowed admin and public access while maintenance.flag is set. Find the section in index.php and make some modifications. I use the following on Magento 1.4.2.0, check to make sure 1.7 uses the same mechanism in index.php:
$maintenanceFile = 'maintenance.flag';
$ip = $_SERVER['REMOTE_ADDR'];
/***************
* IP's allowed in maintenance.
* Use publicly visible IP addresses on LIVE, local if on DEV
***************/
$allowed = array('10.0.0.100','10.0.0.101','10.0.0.20');
if (file_exists($maintenanceFile) && !in_array($ip, $allowed)) {
$basePath = dirname($_SERVER['PHP_SELF']);
include_once dirname(__FILE__) . '/errors/503.php';
exit;
}
Store Maintenance : http://www.magentocommerce.com/magento-connect/store-maintenance.html
This extension will take care of your needs.
I created a Working Joomla 2.5 website in a sub domain. When I moved the site to the root and out of the sub domain folder I get the following error when I log out. Fatal error: Call to a member function init() on a non-object in /directory/templates/rt_clarion/error.php on line 20
The build works fine in the sub domain but not in the root. I've tried the stock Joomla Templates and I still get an error at logout. I tried disabling the Joomla SEF, nothing. Anyone have any ideas what might be?
The site was moved by using akeeba backup and restoring it in the root directory.
I'm using Joomla 2.5.4, K2 v2.5.7, Rockettheme Template Clarion v1.2. Again the build works flawlessly in the subdomain.
First step find out what is causing the server to throw a 500 error - check your servers log file. It may be a simple as a permissions problem, eg. most servers are configure to throw a 500 error if the destination has permissions of 777.
After moving a Joomla! installation from a sub-domain you may need to update the Global Configuration - you can either do this through the Admin screens or by directly editing configuration.php. This often happens when people create the Joomla! site in a sub-directory and the move the site and delete the sub-directory.
The things you need to check are the paths to things like log & tmp directories, e.g.
public $log_path = '/host/public_html/asite/sub-directory/logs';
public $tmp_path = '/host/public_html/asite/sub-directory/tmp';
May need to be changed to:
public $log_path = '/host/public_html/asite/logs';
public $tmp_path = '/host/public_html/asite/tmp';
I'd suggest renaming the template directory and reinstalling that template since that is where the error is occurring, unless you're comfortable exploring the configuration/options for re_clarion
1) Switch to the default template: If you still have errors, the problem is coming from new installation. If not, it's your template (go step 2).
2) Backup your Clarion template folder on your HDD and uninstall it from your backend.
3) Install it again and check for errors. If everythings is OK, overwrite your Clarion folder with backuped data.
We recently migrated our Multi-domain magento setup from a shared host to a dedicated server.
All is working fine fronted, but when I try to go to the admin section I get a 404 error on anything after login.
It seems to work if I remove index.php from the url but then as soon as I click on another link in the admin section it 404's again with the index.php back in the URL.
-- You need to go your server directly and do this via SSH/ FTP
You have to delete the following file
app/etc/use_cache.ser
If you get an error after that like
Notice: Undefined index: 0 in
/srv/www/vhosts/javra.com/htdocs/munchad2/app/code/core/Mage/Core/Model/Mysql4/Config.php
on line 92
Then go to your Database Management.
Open PhpMyAdmin
Go to your database
Click SQL
Run the following SQL Query:
_
SET FOREIGN_KEY_CHECKS=0;
UPDATE `core_store` SET store_id = 0 WHERE code='admin';
UPDATE `core_store_group` SET group_id = 0 WHERE name='Default';
UPDATE `core_website` SET website_id = 0 WHERE code='admin';
UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN';
SET FOREIGN_KEY_CHECKS=1;
Some thing strange happens with the cache when you move the databases from one server to another so it seems like you need to clear it out.
Check in this way
> http://www.yourstore.com/index.php/admin/
or
> http://www.yourstore.com/admin/
After migration from www.domain1.com/magento/ to www.domain2.com/magento/
I was getting 500 Internal Server Error.
So I just renamed my .htaccess to htaccess.txt.
And my frontend started working fine,
But at Backend http://www.yourstore.com/admin/ I was getting Same 500 Internal Server error.
After trying many option suggested online nothing worked for me and after that I tried to access admin via following URL and voilà worked perfect, Hope this help others.
Try to access as this > http://www.yourstore.com/index.php/admin/
Does the dedicated server have mod_rewerite enabled? Does the apache configuration allow .htaccess files to make changes to configuration directives via AllowOverride? Both of those are common ways that the Magento config gets pooched up.
This is an old thread but I've also had an issue with ownership what was returning a 404 in admin.
I'd been doing some work on securing the server and some files were owned as root, not apache. So a chown -R apache:apache . fixed it right up.