Workaround · Setup & onboarding · Blocks work
Installer ignores custom ports behind reverse proxy and conflicts with Synology
1 source thread · first seen 2018-03
Summary
On Synology the installer still wrote ports 80 and 443 in docker-compose despite proxy answers, and missing folders made the stack fail to start until fixed by hand.
- Affects
- Self-hoster on Synology
- Workaround
- Manually change host ports in docker-compose.yml and create the missing folders
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“which I had to manually change to 8223 and 8243 as a workaround”