Access to XMLHttpRequest at 'https://api.openai.com/v1/audio/speech' from origin 'https://192.168.1.108:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
POST https://api.openai.com/v1/audio/speech net::ERR_FAILED 500 (Internal Server Error)
Whay can be wrong? Or is it possbly an error at openai side since it just worked before
ok, so it might be on the openai side then. is it possible to send bugreports or get more information regarding this to be sure where the problem lies?
The situation is classified as ‘major outage’.
Let’s say this specific problem is not on OpenAI’s side then you will run into whatever issues during your debugging process everytime you call the TTS API.
Otherwise you can swap the TTS model with one from another provider and check if the rest of the app still works fine
thanks. where can I find other models?
Suddenly it worked though (once) but then it stopped working again. So likely a bug on openai side. But would be nice to try with another modell as well.
According to the status page the issue should be resolved by now.
Which is good, I do enjoy to help in this forum but really did not feel like doing a Google search.
Anyways, being able to swap models is good practice. Especially if you plan to go into production some time in the future. It’s worth looking into.
I had this issue that came out of nowhere one day. CORS errors up the wazoo. After much digging into it, I discovered that the URL being passed to the AI needs to be exact. I was passing www. when it was not expecting this and that tiny thing blew up the AI into multiple CORS issues. It had no real pattern while testing, working in some browsers and not in others then would change up all of a sudden. Check the specific URL’s format. www. can break everything.
I have the same problem all of a sudden since today. I did not change anything on my application over the past days and it worked one week ago. Very annoying…