After logging in through Chrome I'm returned to new the session screen. Other browsers work.

Description: After clicking any link on my Home tab I am redirected to enter my credentials. If I enter my credentials again it does not proceed. Steps: navigate to " <a href="https://roll20.net/" rel="nofollow">https://roll20.net/</a> " sign in with my creds Observe Home Tab loads, select any link observe you are redirected to " <a href="https://app.roll20.net/sessions/new" rel="nofollow">https://app.roll20.net/sessions/new</a> " Observe any further action will continue to redirect to this page. Console Log: (index):375 Not logged in - checking cookie GDPR status (index):380 GDPR Cookie Detected (index):1 [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: <a href="https://goo.gl/9p2vKq" rel="nofollow">https://goo.gl/9p2vKq</a>) &lt;input type=​"password" name=​"password" class=​"form-control form-control-sm" id=​"input_login-password" placeholder=​"Password"&gt;​ VM1528 naptha-wick.js:2488 [Violation] 'requestAnimationFrame' handler took 58ms [Violation] Forced reflow while executing JavaScript took 57ms VM1499 SymWaxCS.js:319 [Violation] 'setTimeout' handler took 97ms VM1499 SymWaxCS.js:321 [Violation] 'setInterval' handler took 57ms VM1499 SymWaxCS.js:321 [Violation] 'setInterval' handler took 52ms VM17 SymWaxCS.js:321 [Violation] 'setInterval' handler took 91ms VM1499 SymWaxCS.js:319 [Violation] 'setTimeout' handler took 55ms VM1527 content.js:78 undefined VM1527 content.js:78 undefined VM1499 SymWaxCS.js:322 [Violation] 'setInterval' handler took 73ms Navigated to <a href="https://roll20.net/welcome" rel="nofollow">https://roll20.net/welcome</a> VM1675 v2.js:57 JQMIGRATE: Migrate is installed with logging active, version 3.0.0 VM1675 v2.js:57 JQMIGRATE: jQuery.expr[":"] is now jQuery.expr.pseudos i @ VM1675 v2.js:57 get @ VM1675 v2.js:57 (anonymous) @ VM1675 v2.js:178 Sweetalert2.swal.sweetAlert.Swal.SweetAlert @ VM1675 v2.js:178 (anonymous) @ VM1675 v2.js:178 VM1675 v2.js:57 console.trace i @ VM1675 v2.js:57 get @ VM1675 v2.js:57 (anonymous) @ VM1675 v2.js:178 Sweetalert2.swal.sweetAlert.Swal.SweetAlert @ VM1675 v2.js:178 (anonymous) @ VM1675 v2.js:178 welcome:354 Logged in - checking Account GDPR status: true A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. A cookie associated with a cross-site resource at &lt;URL&gt; was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at &lt;URL&gt; and &lt;URL&gt;. welcome:685 GET <a href="https://s3.amazonaws.com/files.d20.io/images/149973918/mEkPjayI9XtRbWedFqVniQ/med.png?1594574001665" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/149973918/mEkPjayI9XtRbWedFqVniQ/med.png?1594574001665</a> 403 (Forbidden) VM1692 SymWaxCS.js:319 [Violation] 'setTimeout' handler took 189ms VM1722 widgets.js:1 You may have been affected by an update to settings in embedded timelines. See <a href="https://twittercommunity.com/t/deprecating-widget-settings/102295" rel="nofollow">https://twittercommunity.com/t/deprecating-widget-settings/102295</a>. &lt;a class=​"twitter-timeline" data-dnt=​"true" data-tweet-limit=​"2" data-chrome=​"nofooter noheader noborders transparent" width=​"350" href=​"https:​/​/​twitter.com/​roll20app" data-widget-id=​"349515861498937344" data-twitter-extracted-i1594756781892199275=​"true"&gt;​Tweets by @roll20app​&lt;/a&gt;​ VM1692 SymWaxCS.js:321 [Violation] 'setInterval' handler took 61ms VM1692 SymWaxCS.js:322 [Violation] 'setInterval' handler took 51ms Navigated to <a href="https://app.roll20.net/sessions/new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new" rel="nofollow">https://app.roll20.net/sessions/new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new</a> v2.js?1594136624:57 JQMIGRATE: Migrate is installed with logging active, version 3.0.0 v2.js?1594136624:57 JQMIGRATE: jQuery.expr[":"] is now jQuery.expr.pseudos i @ v2.js?1594136624:57 get @ v2.js?1594136624:57 (anonymous) @ v2.js?1594136624:178 Sweetalert2.swal.sweetAlert.Swal.SweetAlert @ v2.js?1594136624:178 (anonymous) @ v2.js?1594136624:178 v2.js?1594136624:57 console.trace i @ v2.js?1594136624:57 get @ v2.js?1594136624:57 (anonymous) @ v2.js?1594136624:178 Sweetalert2.swal.sweetAlert.Swal.SweetAlert @ v2.js?1594136624:178 (anonymous) @ v2.js?1594136624:178 new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:387 Not logged in - checking cookie GDPR status new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:392 GDPR Cookie Detected new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:1 [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: <a href="https://goo.gl/9p2vKq" rel="nofollow">https://goo.gl/9p2vKq</a>) &lt;input name=​"password" type=​"password" placeholder=​"Password"&gt;​ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:1 [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: <a href="https://goo.gl/9p2vKq" rel="nofollow">https://goo.gl/9p2vKq</a>) &lt;input name=​"password" type=​"password" placeholder=​"Password"&gt;​ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:1 [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: <a href="https://goo.gl/9p2vKq" rel="nofollow">https://goo.gl/9p2vKq</a>) &lt;input type=​"password" id=​"password" name=​"password" style=​"width:​ calc(100% - 130px)​;​ max-width:​ 300px;​" autocorrect=​"off" autocapitalize=​"off"&gt;​ v2.js?1594136624:57 JQMIGRATE: jQuery.fn.bind() is deprecated i @ v2.js?1594136624:57 bind @ v2.js?1594136624:57 (anonymous) @ browse.js?1594136623:609 h @ v2.js?1594136624:51 d @ v2.js?1594136624:51 nrWrapper @ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:461 setTimeout (async) nrWrapper @ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:461 (anonymous) @ v2.js?1594136624:51 u @ v2.js?1594136624:51 fireWith @ v2.js?1594136624:51 fire @ v2.js?1594136624:51 u @ v2.js?1594136624:51 fireWith @ v2.js?1594136624:51 ready @ v2.js?1594136624:51 d @ v2.js?1594136624:50 v2.js?1594136624:57 console.trace i @ v2.js?1594136624:57 bind @ v2.js?1594136624:57 (anonymous) @ browse.js?1594136623:609 h @ v2.js?1594136624:51 d @ v2.js?1594136624:51 nrWrapper @ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:461 setTimeout (async) nrWrapper @ new?backto=/campaigns/details/7140733/increasingly-terrible-situations-new:461 (anonymous) @ v2.js?1594136624:51 u @ v2.js?1594136624:51 fireWith @ v2.js?1594136624:51 fire @ v2.js?1594136624:51 u @ v2.js?1594136624:51 fireWith @ v2.js?1594136624:51 ready @ v2.js?1594136624:51 d @ v2.js?1594136624:50 SymWaxCS.js:319 [Violation] 'setTimeout' handler took 68ms SymWaxCS.js:322 [Violation] 'setInterval' handler took 51ms

I can confirm this to be the case. I have been experiencing the same issue since around 10pm PST as of July 13th. No matter the link that is clicked after the initial login takes you back to a login screen that goes nowhere. This is exclusive to Chrome.

I may have found a solution to this issue! I was having the exact same problem, then i cleared all my cookies and reloaded the website and everything worked fine.

I confirm this issue as well. This has been the case for me on July 13. My last successful use was July 12. I made no changes to Chrome or extensions between those two sessions. A workaround is to use a Chrome Incognito window. I allowed three extensions to function in that mode and the Roll20 carries on with no issue. (So far.) This is how I'm able to post this reply at all. Just to be sure, I reduced extensions to those three and tried Roll20 with a regular window—still no go; Chrome stuck to login screen. Looks like Incognito for the time being.

Myself and another user are having the same issue. Looks like a session or cookie issue to me. Both Mac Chrome users.

Dumba said: I may have found a solution to this issue! I was having the exact same problem, then i cleared all my cookies and reloaded the website and everything worked fine. Did this and has worked for me too. Cleared cookies and cache, then restarted Chrome. Am now in Roll20 normally. Fingers crossed that this will last.

I have this same issue too. The workaround with using a chrome incognito window is working for me so far.&nbsp; However, clearing the cache and cookies on chrome didn't work for me when I did it, nor did restarting my laptop. I'm not quite sure what to do now :/

Dumba said: I may have found a solution to this issue! I was having the exact same problem, then i cleared all my cookies and reloaded the website and everything worked fine. The cookies did the trick! I feel silly, I thought I had already done that. One thing I noticed when I went to clear them, it was pretty easy to just search for the "roll20" cookies and just delete those, in case anyone didn't want to just clear every cookie.

same its the cookie