Self-hosted installation troubles

Admin Talk Installation
11

According to the SeaTable Server Installation Guide, the official recommendation when you already have a web server like Nginx, Apache, or Traefik is to disable the included Caddy proxy and configure your existing web server to forward requests directly to the SeaTable container.

Stacking proxies (Nginx => Caddy => SeaTable) is generally discouraged as it can lead to complex issues with HTTPS termination, certificate renewals, and CSRF token handling, as seen in similar community discussions (e.g., this thread regarding custom proxies).

For those using the new seatable-compose installation method, this usually involves:

  1. Removing caddy.yml from the COMPOSE_FILE list in your .env file.
  2. Configuring your external Nginx (like Nginx Proxy Manager) to point to the SeaTable server’s internal port.