Closed alexnb98 closed 7 months ago
Hello @alexnb98 ,
As i see you're using a Chrome-like browser with the version 2.1.1 of the extension. I did a try on gitlab.com with my own account and could not reproduce the issue.
To debug this further I'll need more information:
That said I have an intuition, can you try to remove the /
at the end of the host address? and use https://gitlab.com
?
If that works, I'll make sure in the code that we handle nicely both case.
Concerning being a sponsor, it's much appreciated, so far I have applied to GitHub sponsor program but it's not approved yet!
Hello, @Mikescops. Thanks for the quick reply. I'm using chrome with the lasted update.
I do use a VPN (CyberGhost) because I'm currently working from Malaysia. But, I have tried connecting to other servers. Also deactivating it and using my hotels wifi. Lastly also switching to my phone connection. In all cases, it does not work. I used a similar extension and there it worked right away, but I like your extension more.
I also removed the /
but unfortunately changed nothing.
Is there anything else I should try?
Ok, so we'll have to debug this together.
For now what I recommend is to inspect what is happening on the console and on the network.
For this head to the Extension settings and click on "inspect views: service worker" :
Then a capture of both tabs network and console:
Even better if you are okay you can share the full log file with me by exporting it by clicking on this button:
Unfortunately, I cannot share the entire .har
file with you, because actually most of the requests are successful and contain sensitive company information.
But I can share some screenshots with you, hopefully, this helps.
It seems odd to me, that if one request failed, I see this error message in all tabs.
Hey, I solved the issue. The thing was that I don't use the "todo" feature. So, I had like 2k todos. Since, I saw that only that request was failing, I "marked all todos as done" and then the request succeeded! Nice, now I can use your amazing extension. Thanks for the fast help!
If I may I'll reopen the issue so I can keep track of two things:
Can confirm that having a trailing slash in the domain name causes the "Could not connect" error. Removing it fixes things. 👍
Hey, thanks a lot for writing this extension, it is exactly what I've been missing all this time. I really would like to use it, but after adding my access code I get these errors. Is there anything I should do to get access. I created an access token with the
read_api
.I would really like to use it and would love to support you, if there is any way to donate. Thanks!