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.
Related
I transferred my magento installation on ubuntu with files and mysql db dump to my development machine on Windows 10 with XAMPP installed.
I can up the frontend, but I cannot login my admin backend.
I am sure the password and user name are exactly as my installation on ubuntu, why happened? It just stay on the login form and saying all the time invalid formkey, I viewed the source formkey value just generated there.
There mentioned issue with charset, tried no help.
There is no any error logged in var/report and XAMPP apache errorlog, access_log to /index.php/admin is 200, looks good.
will you have any idea? thanks in advance.
Possible causes include
Incorrect permissions on var/session, preventing session files from
being saved
Incorrect configuration of database/redis/other session storage,
preventing saving of session values
A module is instantiating sessions to early, preventing the correct
session names from being set
The cookie domain in System -> Configuration -> Web -> Session Cookie
Management doesn't match the actual site domain.
You're using the localhost as your server domain, and using a version
of webkit that has trouble/bugs setting cookies for localhost in some
situations.
Easier is just to use the IP-address 127.0.0.1 to access Magento.
Open magento database and run below query.
update `core_config_data` set `value`='/' where `path`='web/cookie/cookie_path';
update `core_config_data` set `value`='[magentohost]' where `path`='web/cookie/cookie_domain';
If you have setup multiple store with subdomains, add Cookie Domain: .magentohost.com
Add a dot “.” follwed by Magento URL.
source : CodePetals
I have changed System > Configuration > Advanced > Admin > Security > Allow Magento Backend to run in frame from it's default "Only from same domain" to "Enabled" and I am not able to login to my admin panel. it says 404 not found.
I want to reset back to "only from same domain" from the (script/.htaccess) backend.
Is it possible.
Thanks
This should not be a problem - you could try to clear your cache folders with rm -rf <YOUR MAGENTO ROOT>/var/*.
If that does not help you can set this setting back to "Only from same origin" via database query.
For that please run the following command on your Magento database:
UPDATE core_config_data SET value=2 WHERE `path`='admin/security/domain_policy_backend';
I have done the following steps to resolve this 404 error. Hope might help someone.This error has been resolved by programming.
Go to your cpanel and launch phpMyAdmin.
Locate your Magento Database and select the core_config_data table.
Locate and edit the following rows:
Scope:"Default" and Path:"admin/url/custom"
Select the NULL checkbox and save.
Scope:"Default" and Path:"admin/url/use_custom"
Change value from 1 to 0 and save.
Scope:"Default" and Path:"admin/url/use_custom_path"
Change value from 1 to 0 if it isn't already and save.
Locate and delete the following rows:
Scope:"Stores" and Path:"web/secure/base_url"
Scope:"Stores" and Path:"web/unsecure/base_url" (should be located on the last page)
Delete /var/cache folder
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...)
My Magento web site home page has a redirect loop error. When I try to open it it goes to my old server url and gives the error:
The webpage resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
When I try to go into admin it takes to me old server admin url without any error.
I down loaded the fresh data base and connected my store to that it works fine but when i connect it my old data base it give same error.
Please advise me.
This isn't an ideal solution, but I was having issues with Magento 1.9.x.
The setup was: Nginx Proxy & SSL Terminator => Apache Webserver
No matter what I did enabling SSL caused a redirection loop. I narrowed the issue down to Magento rather than the Nginx configurations.
It was like Magento didn't know it was receiving a secure connection from Nginx even though the correct headers were set.
The dirty solution was to add some code to the very bottom of index.php within the magento root directory (ie. /var/www/magento) just before the Mage::run... line, like so:
if( isset($_SERVER['HTTP_X_FORWARDED_PROTO']) ) {
$_SERVER['HTTPS'] = 'on';
$_SERVER['SERVER_PORT'] = 443;
}
Mage::run($mageRunCode, $mageRunType);
Wrong permissions can also cause this to happen. So in addition to truncating the var/cache and var/session folders, go ahead and make sure that you have the proper permissions on the app, skin, and includes directories, sub-directories and files. I believe the suggested permission setting is 644. You can do this with a proper FTP client such as FireZilla.
Go to table core_config_data
Update these value to be your localhost url(or whatever url you are providing while installation):
web/secure/base_url //(new url)
web/unsecure/base_url // (new url)
Empty the var folder.
I got it fixed.
I manually deleted my cache i was unable to login in my amdin and it get fixed
My issue was Cloudflare, put it in Development mode and it worked. It was cache related.
Issue: ERR_TOO_MANY_REDIRECTS - redirected you too many times
This issue is related cookie domain name.
For ex: if you already installed Magento 2 in www.example.com, and now you change magento base path to sub domain path like www.subdomain.example.com means, then you need to update your cookie domain entry inside of core_config_data table. You cannot access magento 2 backend so you can use following query to check record exist else use insert query.
SELECT * FROM `core_config_data` WHERE `path` REGEXP 'cookie_domain'
if record exit then update subdomain.example.com to the value column.
else
INSERT INTO `core_config_data` (`scope`, `scope_id`, `path`, `value`) VALUES ('default', 0, 'web/cookie/cookie_domain', 'subdomain.example.com');
Then flush cache using command php bin/magento cache:flush
Refresh magento 2 admin, now you can access admin. try this. thanks.
Note: if you are not using cookie domain, then don't configure this settings, if you configuration wrong then also you can face this error, so to fix that error update value to default configuration.
I had the same issue and after reloading and reloading my page I noticed that the error message responded to www.mydomain.tld and sometimes to mydomain.tld. I'm using Plesk on the server and I remembered that I set the Domain to always be called without www. I just changed that to none in the hosting settings of the domain. Lucky me, that solved that issue. Hope that helps someone else.
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.