Logging in to support.discord.com using zendesk doesn't work.
When attempting to log into support.discord.com, I can't click sign in, as a cookie is blocking me. Discord have told me as it's a specific problem with Firefox, I needed to ask, it also appears to be something that I've setup in Firefox, as a fresh install worked fine.
In the popup for logging in, I get a banner message stating: "Cookies required to use Firefox
To continue signing in using Firefox, allow cookies to be stored on this device. You might see this screen more than once. " with a continue hyperlink at the bottom. This generates a popup asking me to accept a cookie. I accepted this, but it's still blocking me from logging in. I have tried disabling my extensions that might block the cookie, and they have also allowed the cookie that was requested.
On a brand new browser, it's fine. I have strict blocking enabled, with ublock and duckduckgo's extension (all were disabled when I was testing if they were blocking it) and I still can't log in. I'm not sure what else is being blocked (other than google analytics, but that shouldn't stop me logging in).
I do also get some console errors: Uncaught ReferenceError: $ is not defined
<anonymous> https://p23.zdassets.com/hc/theming_assets/678183/96508/script.js?digest=9147164294935:417
script.js:417:12 Some cookies are misusing the recommended “SameSite“ attribute 3 Uncaught (in promise) TypeError: At.otDataLayer is undefined
updateGtmMacros https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 Init https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 t https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 t https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 o https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 promise callback*r https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 l https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 l https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 t https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 t https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 o https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 promise callback*r https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 l https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 l https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7 <anonymous> https://cdn.cookielaw.org/scripttemplates/6.33.0/otBannerSdk.js:7
otBannerSdk.js:7:203586 Cookie “_zendesk_authenticated” has been rejected because it is already expired. signin Third-party cookie not allowed auth.js:1:994 Require storage access for firefox: true auth.js:1:1294 Third-party cookie not allowed auth.js:1:994
Alle Antworten (4)
Hmm... Firefox recently rolled out "Total Cookie Protection" to more users. This limits how sites can use "third party" or "cross-site" cookies, meaning cookies from different websites than the one you see in the address bar. Some sites pass you back and forth between different servers during login because they have their services spread out over a number of different servers. That could be the problem here.
You can make exceptions to this feature when needed (for each server that you visit as part of the process of using this company's services). More info in the following articles:
- Introducing Total Cookie Protection in Standard Mode
- Total Cookie Protection and website breakage FAQ
For Discord:
This is easy because you can simply use the shield icon at the left end of the address bar. Click the shield then click the blue slider switch. The shield should now show a slash mark through it.
For Zendesk:
There is an extra step of opening the embedded login form in a new tab so you can access the shield:
- right-click (one button? Ctrl+click) a blank area within the login form
- click This Frame to expand the submenu
- click Open Frame in New Tab
This makes the Zendesk address the top level or "first party" site.
Turn off Enhanced Tracking Protection for this server by clicking the shield icon at the left end of the address bar and then clicking the blue slider switch. The shield should now show a slash mark through it. You can close this tab.
After all that, any improvement?
So, I can log in by opening the embedded form in a new tab, which logs me in fine, however, disabling everything on that new tab doesn't fix support.discord.com.
Did disabling Enhanced Tracking Protection on support.discord.com help at all?
If not, did it at least resolve the third party cookie errors or do you still see those in the console?
No and no sadly.