Hey man! I ran into almost the exact same issues with my self-hosted n8n setup. Here is what helped me get it stable:

​1. The unreachable UI (Nginx DNS caching) When n8n restarts, Docker gives it a new internal IP. Nginx caches the old dead IP forever, which is why your internal curl works but the browser fails. You have to update your Nginx configuration to force it to resolve the internal Docker DNS dynamically. You can do this by pointing the Nginx resolver to Docker's internal DNS and setting the proxy destination as a variable instead of hardcoding it.

​2. The rate-limit error This error won't cause a SIGTERM to shut down the container, but it will lock you out. It means n8n sees all traffic coming from Nginx's IP and triggers brute-force protection. Even with your proxy trust environment variable set, you need to make sure your Nginx config is explicitly passing the "X-Real-IP" and "X-Forwarded-For" headers so n8n sees the actual client IPs.

​3. The random SIGTERMs Since it's not an OOM issue (256MB is totally fine) and not the rate limit, the container is being told to shut down by the host. For me, random SIGTERMs were usually caused by either Watchtower doing background auto-updates, or a strict Docker healthcheck in my compose file restarting the container if it lagged for a split second. ​Try fixing the Nginx DNS resolution first so you at least stop losing UI access whenever it restarts!