# Getting "502 Server Error: Bad Gateway for url: https://api-inference.huggingface.co/models/meta-llama/Llama-3.2-3B-Instruct" error **URL:** \ **Category:** 🤗Hub\ **Created:** [April 16, 2025, 3:31am UTC](https://discuss.huggingface.co/t/getting-502-server-error-bad-gateway-for-url-https-api-inference-huggingface-co-models-meta-llama-llama-3-2-3b-instruct-error/150740 "2025-04-16T03:31:28Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [April 28, 2025, 7:15am UTC](https://discuss.huggingface.co/t/getting-502-server-error-bad-gateway-for-url-https-api-inference-huggingface-co-models-meta-llama-llama-3-2-3b-instruct-error/150740/8 "2025-04-28T07:15:43Z")
> do you have any idea what’s the case with openai/whisper-large-v3 ? The operation seems to have changed. > [@Inference API error with Whisper, return\_timestamps parameter](https://discuss.huggingface.co/t/inference-api-error-with-whisper-return-timestamps-parameter/150043/13): > > Right now the problem was finally solved - it is working correctly on the HF website and with API request. However another change appears in API: no more Auto-detection of audio format, content-type needs to be explitely stated. Briefly in my case: previously I could pass the “application/octet-stream” type (raw bytes) and HF would auto detect it as OGG. But now it causes error “Content type “None” not supported.” . So the solution is to explitely state that it is “audio/ogg” content-type. I… --- _[View the full topic](https://discuss.huggingface.co/t/getting-502-server-error-bad-gateway-for-url-https-api-inference-huggingface-co-models-meta-llama-llama-3-2-3b-instruct-error/150740)._