Error fetching connectors

Resolved 💬 24 comments Opened May 27, 2025 by adamftt Closed May 27, 2025

What version of Codex is running?

It's not working

Which model were you using?

_No response_

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

!Image

What is the expected behavior?

working codex!

What do you see instead?

!Image

Additional information

_No response_

View original on GitHub ↗

24 Comments

MirceaMatei-Superplay · 1 year ago

Hi! Me and a colleague also have this issue. For me it was working fine a few hours ago and my colleague was just trying to set it up for the first time and got this too.

EDIT: Important note: me and my colleague are using the browser version, not the CLI.

dphil · 1 year ago

Same issue here trying to access Codex through the browser. I had set up github connections last week successfully but not done any work with Codex beyond that yet. I tried opening it this morning and am receiving the above errors, due to a 500 response from the POST https://chatgpt.com/backend-api/aip/connectors/list_accessible and POST https://chatgpt.com/backend-api/aip/connectors/links/list_accessible apis called by the frontend. Although, on one attempt to retry, the first api call succeeded but the second still failed, resulting in one of the two UI error messages still showing.

jerrychangusa · 1 year ago

We are also seeing this "Error fetching connectors" issue this morning.

morris2016 · 1 year ago

just restarted and got it too
seems like a global issue

MirceaMatei-Superplay · 1 year ago

Now it is back online for me. Didn't do anything specific for it to get fixed.

SamuelBrudner · 1 year ago

This is markedd as completed but I currently have this issue

Kindjhali · 1 year ago

Ok I also have this issue

dbc148 · 1 year ago

I'm getting this issue now too!

lucadaneluzzosalesforce · 1 year ago

Me to, maybe they have server side issues

jerrychangusa · 1 year ago

the issue has fixed and has returned

arreolavega · 1 year ago

the service is completely down

Turbocaspal · 1 year ago

Ok, same here... Any news?

LarryStewart2022 · 1 year ago

Same issue. :-(

michael-jeremiah-walker · 1 year ago

having this issue as well

jamintz · 1 year ago

Same

davebrown1975 · 1 year ago

And another...

antdke · 1 year ago

having this issue right now : (

devleifr · 1 year ago

same

antdke · 1 year ago

Looks like they updated their status page
!Image

MattStarfield · 1 year ago

adding my name to the list of folks having this issue right now...

Hirama · 1 year ago

just payed sub, and right now it stopped working 🫠

nicolonic · 1 year ago

Same, same

killoder · 1 year ago

Issue has returned again !

!Image

antdke · 1 year ago

Update: Fixed for me!

Back to shipping 🚢