orikbot/second-brain
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Self-Hosting.md and add Immich Access Revisit Plan

Browse Source
This commit is contained in:
Orik
2026-04-21 15:21:25 +00:00
parent b9335b8aae
commit 9ae699974b
2 changed files with 212 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
04_Topics/Self-Hosting.md
View File

@@ -64,3 +64,12 @@
- Proxmox is for ephemeral/experimental services
- Dell is for always-on base services (DNS, backups, HA)
- Synology is bulk storage + media
## Pangolin reverse proxy notes
- Pangolin runs in Docker, so when exposing a service that is running directly on the VPS host, the backend must be reachable from the container network, not just from the host itself.
- For Pangolin public resources that forward to host-level services, use the Docker-to-host reachable IP (`172.17.0.1`) rather than `127.0.0.1`.
- `127.0.0.1` inside the Pangolin container refers to the container loopback, not the VPS host loopback.
- If a VPS service is bound only to `127.0.0.1:<port>`, Pangolin cannot reach it from the isolated Docker network.
- For example, Gitea did not work when forwarded to `127.0.0.1:3000`; removing the `127.0.0.1` bind and exposing the service on a host-reachable interface made it work.
- Practical rule: when a reverse proxy lives in Docker but the upstream service lives on the host, confirm both the host IP and the bind address are reachable from the container namespace.