Could not connect to my gitlab instance

[buxx]

Describe the bug

Since some days, plugin display this error :

uK@moz-extension://855a0c8e-8d14-434f-8d3a-9cd5958a5f7e/background.b6bf980a.js:39:486 o@moz-extension://855a0c8e-8d14-434f-8d3a-9cd5958a5f7e/background.b6bf980a.js:39:4612

To Reproduce

No reproduction step. Sorry.

Expected behavior

My gitlab instance is on a local network behaind a self-signed SSL certificate. Extension was working like a charm then, dosen't work anymore. I reset my access token, refilled conect options without success.

How can I have more info about the 500 responses content ? I don't see anything in console. I don't have access to Gitlab server logs :(

Screenshots

No more than indicated before.

Extension version: 2.3.0

GitLab Enterprise Edition v17.6.1-ee

Desktop (please complete the following information):

• OS: Ubuntu 24.04
• Browser Firefox
• Version 132.0.2 (64 bits)

[buxx]

Okay, I followed this page instruction and success to see http request details. But, I can only see gitlab response content 500 Internal Server Error.

I will try to contact my gitlab administrator.

[Mikescops]

Hey,

It would be helpful to know the gitlab instance version too!

Thanks!

[buxx]

Hello @Mikescops ,

Its GitLab Enterprise Edition v17.6.1-ee

[Mikescops]

Thanks I will check what I can find but so far you're the only report that I have on this.

I'm also working on a new version with better error management so I hope it can help.

[buxx]

Thanks a lot !

Update : Since this morning, there is no more error. The only change I can relate is I clear my remaining TODOs in Gitlab side. This me think about a related Gitlab side internal error related to one of my TODOs ...

So, I think its not git-notify related and can close this issue ! Thanks a lot for your work <3

[Mikescops]

Oh I know this bug actually I should have suggested to delete your todos, I don't know what's wrong with it but the Gitlab API crashes when the todos are above a certain amount. I'll try to sort this out in future versions.

Thanks for solving this one!

[buxx]

I get the problem with only one todo, it is :

Your SSH key has expired.

[Mikescops]

Oh interesting, I'll check what I can do 👍

[Mikescops]

In the dev version on main this issue should be solved / won't crash the entire app as I reworked error management.

[buxx]

Nice ! Thanks a lot !