error：No ephemeral key

[Orange117]

When I start the service, it always shows "No ephemeral key provided by the server." It seems to be related to the realtime API, but I don’t know how to resolve it. Requesting help.

[paulgeorge]

I think this is the same as the error I was seeing, which was something like 'cannot connect to device'. Or maybe 'cannot read properties of undefined (reading 'getUserMedia')

This happened in Chrome and Edge, if I opened the browser developer console, and clicked on the link to the .ts file, it would jump to the line for EPHEMERAL_KEY in App.tsx

Resolution

I was connected to the Windows 11 machine via remote desktop (RDP). When the browser session is started and using RDP, I was not prompted to allow the browser to access audio devices (microphone), instead it just fails to find any microphone, and presents these errors.

When I tried again directly on the machine running the browser, the browser prompted me to allow microphone access, which then allowed the example to run as expected. It is not obvious from the readme that this example requires audio access, I was expecting a typed chat example.

[nm-openai]

Sorry, there were intermittent errors previously for requesting ephemeral keys, but if you refresh the page it subsequently work. Are you still seeing this issue? If so I can escalate to the team and add a retry

[wmartinsneto]

When I start the service, it always shows "No ephemeral key provided by the server." It seems to be related to the realtime API, but I don’t know how to resolve it. Requesting help.

I had this problem too.
The message "No ephemeral key provided by the server" was being displayed in my console error similar to the one on the screenshot above.

If you look at this screenshot again, there is an yellow icon on the corner and the warning: "Next.js (15.1.4) out of date".

So I updated my Node.js to v24.1.01, the latest version today.
Then I ran the openai-realtime-agents successfully, without problems with ephemeral key or any other issue.
Let me know if updating Next.js resolves the issue of you too.