Can't login to staging servers without deleting cookies first. Magento 1.9Cookies not working with subdomainsCan't Login to Admin after Installing ExtensionCookie Issue on Multistore InstallationCan't login to second store on subdomainWhat's the correct cookie config for a Magento site split across multiple instances as subdomains?dev.example.com Frontend Login Creates Sessions for example.com (Can't login)Magento 1.9.2.2: Can't login into admin panelSetting Magento Session CookiesM1: cookie issues in example.com and staging.example.comMagento 1.9 - Customers can't login to frontend [Page refreshes]Magento 2 Cookies break login on subdomains
Someone whose aspirations exceed abilities or means
Why do some employees fill out a W-4 and some don't?
When would it be advantageous not apply Training Ground's cost reduction?
What speaks against investing in precious metals?
How to hide an urban landmark?
How come the nude protesters were not arrested?
How to tell your grandparent to not come to fetch you with their car?
How to communicate to my GM that not being allowed to use stealth isn't fun for me?
What is the maximum number of net attacks that one can make in a round?
Pre-1972 sci-fi short story or novel: alien(?) tunnel where people try new moves and get destroyed if they're not the correct ones
Thread Pool C++ Implementation
Why we don’t make use of the t-distribution for constructing a confidence interval for a proportion?
Fixing obscure 8080 emulator bug?
Winning Strategy for the Magician and his Apprentice
Geopandas and QGIS Calulating Different Polygon Area Values?
How do governments keep track of their issued currency?
Importance of Building Credit Score?
How to hide rifle during medieval town entrance inspection?
CROSS APPLY produces outer join
How is John Wick 3 a 15 certificate?
Is a lack of character descriptions a problem?
Giant Steps - Coltrane and Slonimsky
Generate basis elements of the Steenrod algebra
Teaching a class likely meant to inflate the GPA of student athletes
Can't login to staging servers without deleting cookies first. Magento 1.9
Cookies not working with subdomainsCan't Login to Admin after Installing ExtensionCookie Issue on Multistore InstallationCan't login to second store on subdomainWhat's the correct cookie config for a Magento site split across multiple instances as subdomains?dev.example.com Frontend Login Creates Sessions for example.com (Can't login)Magento 1.9.2.2: Can't login into admin panelSetting Magento Session CookiesM1: cookie issues in example.com and staging.example.comMagento 1.9 - Customers can't login to frontend [Page refreshes]Magento 2 Cookies break login on subdomains
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
We have multiple clones of our main shop at www.mainsite.com for testing and developing.
e.g. test.mainsite.com, fbk.test.mainsite.com and isk.test.mainsite.com,
There is a big issues with the cookies...
Users can't work in all test sites at the same time (Frontend and Backend). They first have to delete all other cookies from the other domains before they can login.
The cookie domain is matching the domain name on every domain, on mainsite.com the cookie domain is mainsite.com
on test.mainsite.com the cookie domain is test.mainsite.com
and so on...
The cookie path is set to /
everywhere
magento-1.9 magento-1.8 magento-1 login cookie
add a comment |
We have multiple clones of our main shop at www.mainsite.com for testing and developing.
e.g. test.mainsite.com, fbk.test.mainsite.com and isk.test.mainsite.com,
There is a big issues with the cookies...
Users can't work in all test sites at the same time (Frontend and Backend). They first have to delete all other cookies from the other domains before they can login.
The cookie domain is matching the domain name on every domain, on mainsite.com the cookie domain is mainsite.com
on test.mainsite.com the cookie domain is test.mainsite.com
and so on...
The cookie path is set to /
everywhere
magento-1.9 magento-1.8 magento-1 login cookie
1
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
No, they are not
– Black
May 28 at 10:40
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06
add a comment |
We have multiple clones of our main shop at www.mainsite.com for testing and developing.
e.g. test.mainsite.com, fbk.test.mainsite.com and isk.test.mainsite.com,
There is a big issues with the cookies...
Users can't work in all test sites at the same time (Frontend and Backend). They first have to delete all other cookies from the other domains before they can login.
The cookie domain is matching the domain name on every domain, on mainsite.com the cookie domain is mainsite.com
on test.mainsite.com the cookie domain is test.mainsite.com
and so on...
The cookie path is set to /
everywhere
magento-1.9 magento-1.8 magento-1 login cookie
We have multiple clones of our main shop at www.mainsite.com for testing and developing.
e.g. test.mainsite.com, fbk.test.mainsite.com and isk.test.mainsite.com,
There is a big issues with the cookies...
Users can't work in all test sites at the same time (Frontend and Backend). They first have to delete all other cookies from the other domains before they can login.
The cookie domain is matching the domain name on every domain, on mainsite.com the cookie domain is mainsite.com
on test.mainsite.com the cookie domain is test.mainsite.com
and so on...
The cookie path is set to /
everywhere
magento-1.9 magento-1.8 magento-1 login cookie
magento-1.9 magento-1.8 magento-1 login cookie
edited May 31 at 9:15
Asad Khan
50814
50814
asked May 23 at 16:10
BlackBlack
442420
442420
1
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
No, they are not
– Black
May 28 at 10:40
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06
add a comment |
1
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
No, they are not
– Black
May 28 at 10:40
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06
1
1
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
No, they are not
– Black
May 28 at 10:40
No, they are not
– Black
May 28 at 10:40
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06
add a comment |
2 Answers
2
active
oldest
votes
You dont have to delete cookies. You can use Chrome incognito mode or firefox private browsing.
Doesn't solve the issue but certainly makes working with it easier.
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
add a comment |
The cause of the bug is a wildcard selector in the cookie domain which is set for unknown reasons, e.g. .test.mainsite.com
So if you are logged in into test.mainsite.com
, then a cookie with cookie domain .test.mainsite.com
is set. If you now try to login to fbk.test.mainsite.com
then it does not work, because a cookie with cookie domain .fbk.test.mainsite.com
is getting set, but there is already a cookie with the cookie domain .test.mainsite.com
which also matches fbk.test.mainsite.com because of the dot at the start which is a wildcard selector.
We solved it by changing the cookie domain of the main site from mainsite.com
to www.mainsite.com
and changing the subdomain names to this:
fbk.test.mainsite.com -> fbk-test.mainsite.com
isk.test.mainsite.com -> isk-test.mainsite.com
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f275896%2fcant-login-to-staging-servers-without-deleting-cookies-first-magento-1-9%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You dont have to delete cookies. You can use Chrome incognito mode or firefox private browsing.
Doesn't solve the issue but certainly makes working with it easier.
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
add a comment |
You dont have to delete cookies. You can use Chrome incognito mode or firefox private browsing.
Doesn't solve the issue but certainly makes working with it easier.
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
add a comment |
You dont have to delete cookies. You can use Chrome incognito mode or firefox private browsing.
Doesn't solve the issue but certainly makes working with it easier.
You dont have to delete cookies. You can use Chrome incognito mode or firefox private browsing.
Doesn't solve the issue but certainly makes working with it easier.
answered May 30 at 23:05
Dominic XigenDominic Xigen
1,090211
1,090211
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
add a comment |
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
1
1
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
Thats not a good solution for the problem, it is only a workaround.
– Black
May 31 at 8:59
add a comment |
The cause of the bug is a wildcard selector in the cookie domain which is set for unknown reasons, e.g. .test.mainsite.com
So if you are logged in into test.mainsite.com
, then a cookie with cookie domain .test.mainsite.com
is set. If you now try to login to fbk.test.mainsite.com
then it does not work, because a cookie with cookie domain .fbk.test.mainsite.com
is getting set, but there is already a cookie with the cookie domain .test.mainsite.com
which also matches fbk.test.mainsite.com because of the dot at the start which is a wildcard selector.
We solved it by changing the cookie domain of the main site from mainsite.com
to www.mainsite.com
and changing the subdomain names to this:
fbk.test.mainsite.com -> fbk-test.mainsite.com
isk.test.mainsite.com -> isk-test.mainsite.com
add a comment |
The cause of the bug is a wildcard selector in the cookie domain which is set for unknown reasons, e.g. .test.mainsite.com
So if you are logged in into test.mainsite.com
, then a cookie with cookie domain .test.mainsite.com
is set. If you now try to login to fbk.test.mainsite.com
then it does not work, because a cookie with cookie domain .fbk.test.mainsite.com
is getting set, but there is already a cookie with the cookie domain .test.mainsite.com
which also matches fbk.test.mainsite.com because of the dot at the start which is a wildcard selector.
We solved it by changing the cookie domain of the main site from mainsite.com
to www.mainsite.com
and changing the subdomain names to this:
fbk.test.mainsite.com -> fbk-test.mainsite.com
isk.test.mainsite.com -> isk-test.mainsite.com
add a comment |
The cause of the bug is a wildcard selector in the cookie domain which is set for unknown reasons, e.g. .test.mainsite.com
So if you are logged in into test.mainsite.com
, then a cookie with cookie domain .test.mainsite.com
is set. If you now try to login to fbk.test.mainsite.com
then it does not work, because a cookie with cookie domain .fbk.test.mainsite.com
is getting set, but there is already a cookie with the cookie domain .test.mainsite.com
which also matches fbk.test.mainsite.com because of the dot at the start which is a wildcard selector.
We solved it by changing the cookie domain of the main site from mainsite.com
to www.mainsite.com
and changing the subdomain names to this:
fbk.test.mainsite.com -> fbk-test.mainsite.com
isk.test.mainsite.com -> isk-test.mainsite.com
The cause of the bug is a wildcard selector in the cookie domain which is set for unknown reasons, e.g. .test.mainsite.com
So if you are logged in into test.mainsite.com
, then a cookie with cookie domain .test.mainsite.com
is set. If you now try to login to fbk.test.mainsite.com
then it does not work, because a cookie with cookie domain .fbk.test.mainsite.com
is getting set, but there is already a cookie with the cookie domain .test.mainsite.com
which also matches fbk.test.mainsite.com because of the dot at the start which is a wildcard selector.
We solved it by changing the cookie domain of the main site from mainsite.com
to www.mainsite.com
and changing the subdomain names to this:
fbk.test.mainsite.com -> fbk-test.mainsite.com
isk.test.mainsite.com -> isk-test.mainsite.com
answered May 31 at 9:14
BlackBlack
442420
442420
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f275896%2fcant-login-to-staging-servers-without-deleting-cookies-first-magento-1-9%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This seems to just be an issue with magento 1. Im going to see if I can find the github issue for you
– Morgan Smith
May 23 at 17:49
Are your cookie domains overridden on any other config scope?
– eddhall
May 28 at 10:27
No, they are not
– Black
May 28 at 10:40
magento.stackexchange.com/questions/71283/…
– MagenX
May 29 at 8:06