[BUG] Enabling DB auth on self-hosted instance seems to do nothing

[mikelmao]

Describe the Bug After setting up firecrawl and configuring it, it seems that setting db authentication to true, doesn't actually do anything.

To Reproduce Host Firecrawl using the kubernetes configuration

Expected Behavior I would expect the API endpoints to not be accessible without some form of authentication being provided such as a bearer token.

Environment (please complete the following information):

• Kubernetes v1.30

[mikelmao]

After re-deploying it did endup throwing an unauthorized error, so seems to be something I potentially mis-configured..

Is there any information on how to add a new token for authentication?

[rafaelsideguide]

@mikelmao thanks for reaching out! It looks like there’s a little mix-up with the DB authentication feature. Just to clarify, this setting is specifically for our managed services linked to supabase and isn’t suitable for a self-hosted setup like yours on Kubernetes.

Let me know if you need any further clarification on this topic.

[mikelmao]

Ah ok, so there is no configuration possible with our own self-hosted supabase to get authentication to be possible? I'd love to restrict acces to the firecrawl instance so it can only be used internally by our team @rafaelsideguide

[nickscamara]

@mikelmao Not possible yet unfortunately.