Describe the Issue

All crawl requests are failing with supabase connection error on self-host instance, even though that the flag for USE_DB_AUTHENTICATION is set to false.

To Reproduce
Steps to reproduce the issue:

1. Deploy the stack using portainer configured with the public repository to fetch and build the application;
2. Call the crawl API with any URL or parameters;

Expected Behavior
A clear and concise description of what you expected to happen when self-hosting.

Expected behaviour, once we set on the environment variables that USE_DB_AUTHENTICATION = FALSE, we expect that the application in its whole respects the configuration. I'm not sure exactly what is happening, but 100% of the attempts fail with the same error.

I managed to get some working on my first setup of firecrawl, but for some reason after a few attempts, all requests started to fail with the same error.

Screenshots
If applicable, add screenshots or copies of the command line output to help explain the self-hosting issue.

Environment (please complete the following information):

• OS: Ubuntu server, LTS
• Firecrawl Version: Latest on master
• Docker Version (if applicable): Latest

Logs
If applicable, include detailed logs to help understand the self-hosting problem.

warn [:]: Authentication is disabled. Supabase client will not be initialized. {}
warn [:]: POSTHOG_API_KEY is not provided - your events will not be logged. Using MockPostHog as a fallback. See posthog.ts for more. {}
info [:]: Number of CPUs: 4 available 
info [:]: Web scraper queue created 
info [:]: Extraction queue created 
info [:]: Index queue created 
info [:]: LLMs TXT generation queue created 
info [:]: Deep research queue created 
info [:]: Billing queue created 
info [:]: Worker 9 started 
info [:]: Worker 9 listening on port 3002 
info [:]: Connected to Redis Session Rate Limit Store! 
warn [:]: You're bypassing authentication {}
warn [:]: You're bypassing authentication {}
debug [api/v1:crawlController]: Crawl 11eded93-0e1b-417d-ad6e-c2c7e8b65003 starting 
debug [api/v1:crawlController]: Determined limit: 10000 
debug [crawl-redis:saveCrawl]: Saving crawl 11eded93-0e1b-417d-ad6e-c2c7e8b65003 to Redis... 
warn [:]: You're bypassing authentication {}
warn [:]: You're bypassing authentication {}
warn [:]: You're bypassing authentication {}
debug [api/v1:crawlController]: Crawl 7aa080c0-73b8-4baa-ad2b-7438d72e3138 starting 
debug [api/v1:crawlController]: Determined limit: 10000 

Additional Context
Add any other context about the self-hosting issue here, such as specific infrastructure details, network setup, or any modifications made to the original Firecrawl setup.

I'm running on a raspberry PI 5, using portainer / docker to deploy the self hosted instance of firecrawl.
O have tried to re-install the setup, change environment variables, different versions ...