/connect doesnt work for openai when server is remote

[iamhenry]

Description

when I tried with the tui /connect for openai auth on a vps it resulted in a failed "localhost" connection

However, it works if you do opencode auth login > openai

Report from another use on discord with the same issue:

I’m trying to sign in with an OpenAI pro sub, on a VPS but it’s giving me: 

~~~
This site can’t be reached

localhost is currently unreachable.
ERR_CONNECTION_FAILED’’’ after redirecting from the sign in page, it seems like it’s due to the redirect being on a different machine, but I’ve been able to do it with all my other providers so far

It’s for http://localhost:1455/auth/callback?code=…
~~~

Plugins

No response

OpenCode version

1.1.18

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• opencode mcp auth fails silently in remote/headless sessions (SSH, devcontainer) #7887: opencode mcp auth fails silently in remote/headless sessions (SSH, devcontainer) - This describes similar localhost connection issues in headless environments
• [FEATURE]: Allow custom OAuth redirect URI configuration for MCP servers #7377: Allow custom OAuth redirect URI configuration for MCP servers - Addresses the core problem that redirect URIs are hardcoded and cannot be configured for different deployment scenarios (like VPS environments)
• bug: OAuth uses wrong authorization URL and missing redirectUri config #5766: OAuth uses wrong authorization URL and missing redirectUri config - Related issue about OAuth redirect configuration needs

Your issue specifically involves the TUI failing to redirect to localhost on a VPS, which is directly related to the redirect URI configuration problem mentioned in these issues.

Feel free to ignore if none of these address your specific case.

[rekram1-node]

Yeah I could see how vps could be causing this

[iamhenry]

discord thread: https://discord.com/channels/1391832426048651334/1460293126328549446

[chriswiggins]

I've just closed #8798 in favour of this, but I have made the changes to get this to work, but I think we'd need to update the OpenAI OAuth redirect URLs somehow?

If you reverse proxy OpenCode web (in our case, we're running OpenCode insider a coder workspace), then ChatGPT OAuth doesn't work, because the OAuth server callback is started on another port.

I've made the changes necessary (in my local environment) to make this work, however it looks like this may be a bit more difficult given the OAuth client ID likely has its redirect URL locked down to http://localhost:1455/auth/callback

It would be great to get some more info on this, and whether or not there is a potential other flow we can use (device code?) to get this to work in OpenCode web!

[mihnearad]

I managed to get it to work, in my case

If you’re running OpenCode on a remote server over SSH, the OAuth callback to http://localhost:1455/auth/callback will fail unless you forward the port to your local machine.

What worked for me:

ssh -L 1455:127.0.0.1:1455 user@remote-ip

This forwards your local `localhost:1455` to the remote server’s `localhost:1455`, where OpenCode is listening for the callback.

After reconnecting with this tunnel and re-running the auth flow, the login worked

Hope this helps anyone else running into this

[tangotechhq]

I managed to get it to work, in my case

If you’re running OpenCode on a remote server over SSH, the OAuth callback to http://localhost:1455/auth/callback will fail unless you forward the port to your local machine.

What worked for me:

ssh -L 1455:127.0.0.1:1455 user@remote-ip
This forwards your local localhost:1455 to the remote server’s localhost:1455, where OpenCode is listening for the callback.

After reconnecting with this tunnel and re-running the auth flow, the login worked

Hope this helps anyone else running into this

this worked perfectly for me thank you! just a simple cmd with your ssh command, then copy the link, authenticate, works, close cmd.