# Self-hosted installation troubles

**URL:** <https://forum.seatable.com/t/self-hosted-installation-troubles/7352>\
**Category:** Installation\
**Created:** [May 11, 2026, 9:22am UTC](https://forum.seatable.com/t/self-hosted-installation-troubles/7352 "2026-05-11T09:22:21Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![daniel.pan](https://forum.seatable.com/user_avatar/forum.seatable.com/daniel.pan/32/13_2.png) [@daniel.pan](https://forum.seatable.com/u/daniel.pan)\
**Post date:** [June 4, 2026, 12:16am UTC](https://forum.seatable.com/t/self-hosted-installation-troubles/7352/11 "2026-06-04T00:16:21Z")

</div>

According to the [SeaTable Server Installation Guide](https://seatable.com/seatable-enterprise-installation-server-webserver/), 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](https://forum.seatable.com/t/seatable-v5-custom-apache2-proxy-permission-denied/4957)).

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.

---

_[View the full topic](https://forum.seatable.com/t/self-hosted-installation-troubles/7352)._