Self-hosted support | Deepgram | Page 1

sudden quest Nov 26, 2025, 9:37 AM

#

I had been working with one of the product consultants on deploying our trial self-hosted deployment and haven't been able to contct them for the last 2-weeks. I also sent another message through the site enquiries late last week with no response. Can someone please reach out to assist?

fast tulipBOT Nov 26, 2025, 9:37 AM

#

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
-# If you haven't done so, ensure your Discord and Github profiles are linked to Deepgram so you can earn points to redeem on cool stuff just by being active!

#

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

The programming language you are working in (e.g. JavaScript, Python).
The deepgram product you are using (e.g Speech to Text, Agent API)
A request ID that triggered your error or issue.

sudden quest Nov 26, 2025, 9:39 AM

#

It is to do with a self hosted STT deployment
No request ID, no programming language

eternal shadowBOT Dec 2, 2025, 10:24 PM

#

:wave: When you say "I had been working with one of the product consultants" was this someone from Deepgram?

sudden quest Dec 4, 2025, 9:41 AM

#

Yes it was Juan Gasca - he responded to me via email immediately after I posted this and I haven’t heard from him since again.
He had provided all the models for our testing of local deployment, and I advised there was an issue and needed support with an issue with quay authorisation.

He was very responsive up till a couple of weeks ago, and we are stuck right now unable to proceed

sudden quest Dec 4, 2025, 9:35 PM

#

I got right through to the end of the self-hosted build and ran into the following error with quay.io:

ubuntu@ip-172-31-40-232:~/config$ sudo --preserve-env=DEEPGRAM_API_KEY docker compose up -d
[+] Running 2/2
! engine Interrupted 2.0s
✘ api Error unknown: failed to resolve reference "quay.io/deepgram/self-hosted-api:release-251029": unexpected status from HEAD r... 2.0s
Error response from daemon: unknown: failed to resolve reference "quay.io/deepgram/self-hosted-api:release-251029": unexpected status from HEAD request to https://quay.io/v2/deepgram/self-hosted-api/manifests/release-251029: 401 UNAUTHORIZED

I relogged in with the quay.io login and ran it again with no success.
My security group oubound rules are currently set to All traffic 0.0.0.0/0 so should be no issue there either.

#Self-hosted support