sudo vim /etc/caddy/Caddyfile sudo systemctl reload caddy

pomofocus.duckdns.org { reverse_proxy :4000 { transport http { # Required for WebSocket support keepalive 30s } # Forward headers for HTTPS/WebSocket header_up X-Forwarded-Proto {https} header_up Host {host} } }

ENV ERL_MAX_PORTS=1024 The maximum number of Erlang ports are being allocated, causing dramatic memory usage. Limiting the max number of ports should drop memory usage from >2GB to <200MB https://elixirforum.com/t/elixir-erlang-docker-containers-ram-usage-on-different-oss-kernels/57251

Delete fallback cookie session storage -> phx:fallback:be = true

When using "Proxied" on a free Cloudflare account, and your local ISP is Deutsche Telekom (DTAG), you request gets routed through the US. In my case (confimred with traceroute) it meant the following: Me (Germany) -> Cloudflare (USA) -> Hetzner Server (Germany) (The actual traceroute had some more stops, but you get the gist). So instead of routing the the Cloudflare address in Düsseldorf (right next door) it hopped over the Atlantic. A cross-atlantic round trip comes with quite a bit of latency, that had me scratching my head, since in local dev even with network throttling I had better performance, and the same Hetzer server responded pretty quickly to duckdns. Turning off "Proxied" and setting it to "DNS only" solves this problem, while losing you most of Cloudflares built in features. The only other possibility seems to be upgrading to a paid Cloudflare plan. This is where I found the explanation for the current situation: https://community.cloudflare.com/t/our-server-in-frankfurt-germany-eu-is-being-proxied-from-the-newark-nj-us-datacenter/610483/9?u=chaika

Free disk space: df -h /

https://github.com/elixir-sqlite/exqlite/issues/323 Downgrade Exqlite to a working version: {:ecto_sqlite3, ">= 0.0.0"}, {:exqlite, "~> 0.29.0", override: true},