Hi team,
We’ve been working on deploying our LibreChat-based project and followed your advice, where we removed the netlify.toml file and configured everything manually via the Netlify UI.
Progress so far
The build now completes successfully without any errors.
All required environment variables (including Supabase and OpenAI keys) have been carefully added via the UI.
Supabase credentials (e.g., SUPABASE_URL, SUPABASE_ANON_KEY) are added and marked for use in both Build & Functions.
Our Supabase project is active, not paused, and confirmed working.
Current issue
Despite the successful deployment, the live site immediately throws a 404 Internal Server Error on load. This is the screenshot.
Everything seems correctly configured from our side, but something fails at runtime.
Kindly requesting your help to:
- Review the live site logs for runtime issues.
- Confirm whether all environment variables are being injected properly into the deployed app.
- Help us identify what’s blocking the frontend from rendering correctly.
We’ve spent considerable time trying to troubleshoot this and would greatly appreciate if someone from your team could take a final look or guide us to resolution.
We’re eager to go live on Netlify.
Looking forward to your response.
Kind Regards
@aimatch I might be wrong, but your post reads like it was generated by AI.
If you’re “vibe coding” you should just continue to converse with whatever tools you’re using.
The Netlify support forum is for assistance with Netlify’s systems.
It is not for help with general web development.
Netlify’s staff operate to a “Scope of Support”, they don’t help with project issues…
Base functionality of Netlify’s build and deploy pipeline is supported, but we cannot help you debug any source code used either during build or after deployment.
Community members can help, but they’re volunteers.
Netlify is self service, so you need to debug your project yourself.
This includes looking at logs, the ‘Function Logs’ documentation can be found here:
https://docs.netlify.com/functions/logs/
Again, you will need to confirm this yourself.
Edit and redeploy your code to debug if necessary.
Nobody knows your application better than you do (or the AI you used to generate it).
So you’re the one best placed to determine what it needs, what it’s missing, and why it isn’t working.
In your screenshot I can see that all your requests to /api/ are showing as encountering a 404.
A 404 isn’t an “Internal Server Error” (e.g. 500 error), so there may be nothing in your logs.
You need to ensure that your API is actually running.
If you generated it, it could be that it’s been made in a way that simply won’t run on Netlify.
