Hi Chris this also worked for me.
After updating the server time IE start working.
Thanks a lot!
Pedro
chrischip - 06 November 2008 10:49 PM
I find out what happened. My server time is incorrect and actually behind the time of my client. The invalidates session cookie in IE and Chrome. For some reason Firefox allows this. As soon as I corrected the system time on my Apache server time it works.
For some of you running a Linux and Apache, this may help. Particularly if you’re also having issues with the installation where you wither can’t log in, or you enter the requested information on a forum during the installation, but when you click next or ok, the screen just comes back empty, without errors.
After bashing my head against a wall for weeks with this issue, it turns out it mod_bandwidth! Commenting this out in the apache configuration file resolved this issue for not only this install, but several other installs and application issues.
If you don’t know what I’m talking about, or how to do this, you should probably have your host do it for you. It only takes a second and actually resolves the issue.
im having the same problem,
cant login to my newly installed admin with any browser. reinstalling with/without rewrite urls didnt help, submit always getting the login page or to the frontend when a wrong password is used.
im hosting at godaddy so i dont think i cant modify the mod_bandwidth configuration.
did anyone solve this problem?
update:
ok, ive found out that godaddy`s preview dns is causing my problem,
is there a solution for it?
I am having the same problem using a local SUSE 10.2 webserver.
I already did two installs. Directly after install I am going to http://suse/magento/index.php/admin/ and enter my username and password, but clicking “login” just returns me to the same screen with name and password emptied.
Using IE7, Firefox and Chrome gives exactly the same result.
Servertime and clienttime are exactly the same.
There is no mod_bandwidth in the Apache configuration.
Going to “forgot password” and back doesn’t help
Nothing helps!
This happened to me when I installed the sample data it changed my password and now I cannot login and on the “install Sample Data” instrructions they don’t even list the password. Im starting to think they are scamming us into buying support.
I’m recently started having this issue. Worked fine for a long time, but then the latest version started having this issue. I was able to get a response after using the correct password, having it go back to the admin form - I clicked onto the “forgot password” page and got this message.
“{{base_url}} is not recommended to use in a production environment to declare the Base Unsecure Url / Base Secure Url. It is highly recommended to change this value in your Magento configuration.”
I then had the idea to check the Base URL settings by checking the attribute in the database (core_config_data) and
config_id scope scope_id path value
1 default 0 catalog/category/root_id 2
was the only entry. There should be over 400.
This is a new installation running the latest version of magento as of 2/12/2009. This is running on WAMP, correctly configured.
replacing ‘localhost’ with the ip worked for me too.
Just wondering, I’m getting this warning in my admin
{{base_url}} is not recommended to use in a production environment to declare the Base Unsecure Url / Base Secure Url. It is highly recommended to change this value in your Magento configuration.
Do i just ignore this, or shall i replace it with....something?
I’m just testing Magento locally at the moment, however am concerned if this warning will effect the store in a live environment.
It’s obvious i don’t really know what it means.
{base_url} refers to the url of your magento webshop. So, you should fill in “http://www.yourwebshop.com” (without quotes and your url).
On my intranet I was experiencing problems (no admin login possible) after filling in the intranet url (http://suse).
After replacing it with the IP “http://IPadres” it worked.
You can edit {base_url} with phpMyadmin in your Magento database in the core_config_data table in the record with value “web/unsecure/base_url” in the “path” field.
I just checked my core_config_data table (after being unable to login to admin and getting the base_url error) and my table has no values. Zero rows. Shouldn’t there be some?
