Error creating connector – Request timeout

ChatGPT Apps SDK
,
1

For some reason I am unable to create a new connector. Everything works fine with the local MCP inspector too. Any idea if this is just something temporary or?

The only details I’m getting in the network request is: { detail: "Request timeout" }

Screenshot 2025-10-31 at 16.41.25
Screenshot 2025-10-31 at 16.41.25978×1548 113 KB

4

Bump​​​​​​​​​​​​​​​​​​​​​​​​​​​​

5

Hi and welcome to the community!

I can help bring some additional visibility to your issue, but it would also be helpful if you could share a few more details about your specific case. The team will likely ask for them anyway.

Thank you in advance.

6

I have solved my issue, I forwarded my local MCP server to my web server and I stored my password in the URL, but had bad rewrites. This config fixed it.

server {
    listen 80;
    listen [::]:80;
    server_name my-server.com;

    location ^~ /.well-known/acme-challenge/ {
        alias /var/www/letsencrypt/.well-known/acme-challenge/;
        default_type text/plain;
        try_files $uri =404;
    }

    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name my-server.com;

    ssl_certificate /etc/letsencrypt/live/my-server/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/my-server/privkey.pem;

    location /my-password/ {
        rewrite ^/my-password/(.*)$ /$1 break;

        proxy_pass http://127.0.0.1:16434;
        proxy_http_version 1.1;

        proxy_set_header Host 127.0.0.1:16434;
        proxy_set_header Connection "";
        proxy_set_header Accept text/event-stream;

        proxy_buffering off;
        proxy_cache off;
        proxy_read_timeout 3600;
        proxy_send_timeout 3600;

	    sub_filter_once off;
	    sub_filter_types text/event-stream;
	    sub_filter 'data: /message?' 'data: /my-server/message?';
    }
    
    location / {
        return 404;
    }
}

Not sure if that applies to @mmatila though. Probably not. A clearer error message would be better instead of this: { detail: "Request timeout" }