⌘K
Anshuman Bhardwaj Hi @amorepi, welcome to the Vercel Community! I'm sorry that it's taking longer than you expected. Let me check with our team to see if there's something we can do.
Anshuman Bhardwaj Hi @amorepi, it seems like Hostinger has 7 days after the transfer to decline or approve it. If they do nothing, it automatically gets approved after those 7 days. So, based on your request, it seems like the transfer will complete on the 18th. There's nothing we can do to expedite this process.
イタズラ Experienced this earlier today with the small model. I don't mind if it's a small mistake, but generating completely invalid code and charging to fix it is a little off:
Anshuman Bhardwaj Hi @hayko97, I'm sorry you are facing this issue. Can you share some examples of the issues you faced? Chat IDs or URLs will help us narrow the issue down.
Jacob Paris There doesn't appear to be a systemic issue with the keys (low 401 rate and I can successfully follow your steps) Evidence points to your API key being rejected. The thing to focus on here is the cURL request, since that eliminates anything weird Codex could be doing You will get a 401 if that $V0_API_KEY variable is undefined, in case your export V0_API_KEY command executed in a different environment and the variable didn't carry over to when you ran your curl command, so make sure you test them back to back ➜ ~ export V0_API_KEY="v1:……………………………………………………………………………………………O" ➜ ~ curl -s -o /dev/n
loai Hi Jacob, Thanks again for following up — I finally managed to get the Vercel key itself working, but I’ve run into a second, CLI-specific problem that’s preventing me from switching my default provider back to OpenAI. Where things stand now | Step | Result | | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------- | | 1. curl with V0\_API\_KEY | ✅ returns 200 (v0-1.5-md) — so the key & billing are good. | | | 2. codex --provider ver
William I couldn't get it to work too. I followed the v0 docs and have the provider vercel added in config.json , and then I have V0_API_KEY in env along side OPENAI_API_KEY (which seems to be the cause of the issue) curl with V0_API_KEY returns 200 as well I think it is an upstream issue reported in the codex repo: github.com/openai/codex/issues/987 and the issue seems to be related to being logged in with openai keys and then trying to switch to other providers.
Jacob Paris Can you explain what you mean with missing versions? If I understand your timeline you worked on a file you renewed your subscription you did further work in the same chat at some point those versions were reverted?
Soko Technologies Timeline is accurate except the last one: I was able to continue working on the same project after renew but I am unable to deploy the changes. I was able to do that prior to the renewal. I tried to download the latest changes I made so I can commit the most recent version and I was unable to download the files. I checked back later and both the code and the preview for the latest version (and all versions after the renewal) can't be loaded. See attached the screen I am currently seeing when I switch to the latest version.
Soko Technologies @jacobparis any update on this please? This is a huge blocker for me and I need to know whether there'd be any resolution to this quickly so we can start looking at alternative approaches to continuing with work.
