draw.io stuck at "Starting..."

1,591 views
Skip to first unread message

Xander

unread,
Nov 9, 2017, 11:51:14 AM11/9/17
to draw.io
Hello!
When I started using draw.io, I selected google drive as a place to store my resources, but it didn`t work (could not connect to google drive) so I changed it to github and everything was fine. 
The next day i start draw.io and it gets stuck at the "Sarting..." page (picture of the screen: https://gyazo.com/4584aa711efa0469c264b7781887683). I suspected the site was down so i just downloaded the offline version from google store. 
Next day i get the same thing so I asked a friend if she had the same problem, but she could use the site just fine so i opened an incognito tab and the site was fine so I thought it had something to do with the session/cookies so i opened the console (f12) and for "https://www.draw.io" i cleared all cookies and it was fine, BUT I noticed that something  logged me off my gmail account. 
After a few days of not knowing why i was constantly being logged off my gmail i realized that it was because i was deleting the cookies for draw.io which i find quite weird. Anyway after realizing this I went to the google drive settings and disconnected draw.io from there and that seemed to have fixed my problem. I was no longer getting stuck on Starting so i didn`t have to clear cookies which meant i was no longer getting gmail disconnects (this was yesterday).
Today  I opened draw.io and again i`m getting stuck at that dreaded page, but i don`t find draw.io as being connected to my gmail. 

In incognito, if i log on gmail and github, it works just fine, but there are less cookies. The ones that aren`t in incognito are called: OTZ, S, dsc and there are 4 "_cfduid" instead of 2 like in incognito

I`m really not sure what`s causing this, but it`s really annoying, but after deleting S (which didn`t appear to do much) and OTZ, it got unstuck (with the google drive option still grayed out).
After deleting those 2 cookies, i wasn`t able to make them come back, but everything seemed fine yesterday as well. 
Does anyone know what causes those 2 cookies to be created and how to avoid it (since they or just OTZ seem to be the reason why i get stuck at the starting page) ?


Xander

unread,
Nov 11, 2017, 2:06:33 AM11/11/17
to draw.io
As expected, today I somehow got again the OTZ cookie and draw.io got stuck again. 
Some inf about that cookie:
Domain: apis.google.com Expires/Max-Age:2017-12-10T20:55:16.000Z
Size: 33
Not Http, but is Secure

Deleting it solved the problem again, but it sure is annoying. Does anyone know what`s making that cookie ?

David Benson

unread,
Nov 11, 2017, 5:11:30 AM11/11/17
to draw.io
What's the 3 line summary of this problem?

Xander

unread,
Nov 11, 2017, 6:31:40 AM11/11/17
to draw.io
1) Something creates this OTZ cookie
2) The cookie is preventing me from using draw.io (page gets stuck)
3) Constantly having to delete the cookie is annoying 

When i started the post i also started troubleshooting the issue and that`s why from page get`s stuck i got to the OTZ cookie and i suspect it has something to do with the fact that at the beginning i opted for the google drive option,but i`m not sure. 

Gaudenz Alder

unread,
Nov 14, 2017, 12:25:59 AM11/14/17
to draw.io
The only cookie that we create in the draw.io domain for Google auth is called ".guid", and I don't see an OTZ cookie in my browser console when using draw.io. Are you using any browser extensions that may be causing this? What is the exact name and what is the value of the cookie (please do not post auth tokens here)?

Xander

unread,
Nov 14, 2017, 3:39:17 AM11/14/17
to draw.io
I seems like the "Blur" extension is causing this and by disabling the "Account saving for this site" feature (found in settings) seems to have fixed it. 

I think that because i chose google drive first it remembered that way of "logging in" and since it appears grayed out during normal log in (for me at least: https://gyazo.com/fe8dfd9471a1fda62d8d2abd8750bda5) it was getting stuck.

Thank you and I`ll come with updates if this was not actually what was causing my problem. 
Reply all
Reply to author
Forward
0 new messages