I GIVE Up - Self Hosted

Hello

I give up i have purchased a Self Hosted business plan i have install all according with instruction and when i want to build a app i am getting error Sorry, there was an error processing your message.

Or Internal Server error I anyone available to hire so i get the configuration perfectly

Thank you

Hi Alin, don’t give up — we’re here to help you get it working! :raising_hands:

Let’s troubleshoot this together. To start, could you share:

  1. The exact error message you’re seeing (screenshot if possible)

  2. Your hosting environment — are you on a shared hosting platform (like Elestio, Railway, etc.) or a dedicated server?

This will help us pinpoint what’s going wrong!

Thank you ok, I know that we are using Amazon and veracel is not giveme any error just internal server error :frowning:

Thanks for the info! AWS + Vercel configured — that’s helpful.

To narrow down the “Internal Server Error”, could you share:

  1. A screenshot of the error — does it appear when you first open App Builder, or only after you type a prompt?

  2. Your v0 API key setup — what Base URL are you using? (e.g., https://v0.dev/api or a custom proxy)

  3. Your Teable version — visible at the bottom of the admin panel

The error could be a misconfigured v0 endpoint or an API key issue — a screenshot will help us pinpoint it quickly!

We’re using AWS EC2 (dedicated server) with Docker Compose deployment.

  • Instance: t3.medium (4GB RAM, 2 vCPU)
  • OS: Amazon Linux 2023
  • Region: eu-west-2 (London)
  • Nginx as reverse proxy
  • Cloudflare for DNS & SSL

Thanks for the details! Could you briefly describe what you’re seeing and share a couple of screenshots — one of your v0 configuration in the settings, and one of the error itself? A short screen recording works too if that’s easier.

hello v0 info/config they wanted to see?

v0 info/config they wanted to see?

Hi Alin! To help us diagnose this, could you share:

  1. Test results on the App Builder settings page — click the Test buttons for “Test Public Access”, v0 API key, and Vercel API Token, and let us know which pass/fail

  2. Can you chat in the AI panel? — try clicking “Generate” on the left side of the App Builder and see if you can have a conversation there

  3. A screenshot of the error you’re seeing

Thanks!

As yiu ca see is all green

Hi Alin!

  1. Can you chat in the AI panel? — try clicking “Generate” on the left side of the App Builder and see if you can have a conversation there

  2. A screenshot of the error you’re seeing

Thanks!

1 Like

Hi @Alin_Turi

If your v0 plan is the free one, it’s “normal”, I have the same errors. With a v0 free plan, you get $5 credits per month, you can use them with Teable or directly with v0.

But there’s also another limit : you can’t do more than a few requests per day. That’s probably why you get these error messages, I got the sames and the daily limit is the reason.

When you work with Teable’s app builder, open a tab to v0 and you will see exactely what happens + the error messages.

Cheers,

Christophe

Thank you so much, do you have experiance with Amazon server ? I cannt upload a CSV file, a big one is uplaoding and nothing else happen :frowning: Thank you

This is a multi-layer upload limit problem. When using Cloudflare + Nginx + Docker, large file uploads get silently blocked at one of several layers. Here’s the
diagnostic breakdown and fix:


Layer 1: Cloudflare (Most Likely Culprit)

Cloudflare proxied mode has strict upload limits:

  • Free plan: 100MB max
  • Pro: 200MB
  • Business/Enterprise: 500MB+

Large uploads often silently fail because Cloudflare drops the request without a clear error.

Fix options:

Option A — Bypass Cloudflare for uploads (Recommended)
In Cloudflare DNS settings, temporarily set your domain to “DNS only” (grey cloud) instead of “Proxied” (orange cloud) for the upload test.

Option B — Use Cloudflare Workers or tune limits
If on a paid plan, go to: Cloudflare Dashboard → your zone → Settings → Network → Max Upload Size


Layer 2: Nginx client_max_body_size

Default is 1MB. This silently returns a 413 error that the frontend may not display properly.

Edit your Nginx config:

http {
client_max_body_size 500M; # Increase as needed
client_body_timeout 300s;
proxy_read_timeout 300s;
proxy_send_timeout 300s;
proxy_connect_timeout 300s;
}

Then reload:
sudo nginx -t && sudo nginx -s reload


Layer 3: Teable / Docker Compose Environment

Add these to your docker-compose.yml or .env file for the backend service:

environment:

  • BACKEND_UPLOAD_FILE_SIZE_LIMIT=524288000 # 500MB in bytes

Quick Diagnostic

Run this to see where it’s failing:

Test upload directly (bypassing Cloudflare) using your EC2 public IP

curl -v -X POST https://YOUR_EC2_IP/api/import
-H “Content-Type: multipart/form-data”
-F “file=@your_large_file.csv”
–insecure 2>&1 | grep -E “< HTTP|413|timeout|error”

If you get 413 → Nginx limit issue
If it hangs/times out → Cloudflare or proxy timeout issue
If it works via IP but not domain → Cloudflare is blocking it


Recommended Fix Order

  1. First: Set Cloudflare DNS to “DNS only” temporarily and test
  2. If that works: Fix Nginx client_max_body_size
  3. Then: Re-enable Cloudflare proxy and configure upload limits there

What size is the CSV file you’re trying to upload?

I am trying to upload 90mb is upload and after is just freez :frowning:


90MB is a very large CSV — that’s likely 200,000–500,000+ rows of data.

A few honest points:

Why it freezes:

  • Your server (t3.medium, 4GB RAM) may run out of memory processing it
  • Nginx / Cloudflare is likely cutting the connection silently

My suggestion — split the file first:

Split into chunks of 10,000 rows each
Then upload one chunk at a time.

Also worth asking yourself:

  • Do you really need all that data in Teable?
  • Is this historical data or active records?

For a CRM use case, you likely only need active customers — filter the CSV down to what you actually use before importing. A clean 5,000-row file will perform much better
than 500,000 rows on your current server size.

What kind of data is in this CSV?

Yes there are database with taxi booking information and customer trends so yes I got around 60k lines and lots of columns

The funny think is if i upload in app.teable is working perfectly:(

And the app builder is not :frowning:

I cannot build even a small app

I tested the “CRM Lite” version (only Customers + All Bookings) and it still fails with the same Internal Server Error. That suggests it’s not caused by “too many tables/fields”, but a general App Builder issue on your instance (service/config/permissions/bug).

To find the real cause (not guess), you need one of these:

If you have server/admin access (recommended)
Check the Teable backend logs around 14:16 Europe/London for a 500 on the app builder endpoint. The logs will show the exact exception (DB error, auth issue, feature flag, etc.).

Tell me how Teable is deployed and I’ll give the exact command:

Docker / Docker Compose?
Kubernetes?
Hosted / managed?
If you don’t have server access
Send your admin this info:

Any “create app” request returns 500, even with only 2 tables
Exact time: 2026-03-10 14:16 Europe/London
Base ID: bser07fmheEFu8ScGup
Workaround (until App Builder works)
You can still use the standard Teable UI as a CRM (views, filters, linked records, forms). I can help you set up:

“Customers (CRM)” view
“Bookings pipeline” view
“Customer 360” view (lookup/rollup fields)
automations (follow-ups, tagging, notifications)
Which deployment is it: Docker, Kubernetes, or hosted?

Task completed

@
Add context

Paste or drag and drop to upload here
Describe what you want to do

gpt-5.2

Here’s how to pull the exact logs for the App Builder error:

docker compose logs backend --since 24h 2>&1 | grep -iE “app.?builder|appbuilder|500|error|exception” | tail -50

Or watch it live while triggering the error:

docker compose logs -f backend
Then immediately try to open App Builder in your browser — the error will appear live.

A screenshot or short screen recording of the error in the browser would also help a lot — even just the error message shown on screen is enough for us to identify the
issue.

Self-hosting can get quite complex as you’ve seen — Nginx limits, Cloudflare config, Docker tuning, App Builder issues… all piling up.

Have you considered using our cloud-hosted version at https://teable.ai instead? Everything works out of the box, no configuration headaches. :blush: