{"action":"created","issue":{"url":"https://api.github.com/repos/bitwarden/core/issues/244","repository_url":"https://api.github.com/repos/bitwarden/core","labels_url":"https://api.github.com/repos/bitwarden/core/issues/244/labels{/name}","comments_url":"https://api.github.com/repos/bitwarden/core/issues/244/comments","events_url":"https://api.github.com/repos/bitwarden/core/issues/244/events","html_url":"https://github.com/bitwarden/core/issues/244","id":308728224,"number":244,"title":"Installing bitwarden issues with different ports behind proxy and missing folders","user":{"login":"stevenhrabok","id":21085185,"avatar_url":"https://avatars2.githubusercontent.com/u/21085185?v=4","gravatar_id":"","url":"https://api.github.com/users/stevenhrabok","html_url":"https://github.com/stevenhrabok","followers_url":"https://api.github.com/users/stevenhrabok/followers","following_url":"https://api.github.com/users/stevenhrabok/following{/other_user}","gists_url":"https://api.github.com/users/stevenhrabok/gists{/gist_id}","starred_url":"https://api.github.com/users/stevenhrabok/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stevenhrabok/subscriptions","organizations_url":"https://api.github.com/users/stevenhrabok/orgs","repos_url":"https://api.github.com/users/stevenhrabok/repos","events_url":"https://api.github.com/users/stevenhrabok/events{/privacy}","received_events_url":"https://api.github.com/users/stevenhrabok/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-03-26T20:44:01Z","updated_at":"2018-03-28T20:30:19Z","closed_at":null,"author_association":"NONE","body":"Hello,\r\n\r\nI've been testing out deployment of bitwarden using the bitwarden.sh script on a Synology DSM. I've managed to complete an install by manually changing docker-compose.yml as well as creating missing folders.\r\n\r\nI'm wondering if my understanding of the prompts is being interpreted wrong for my setup.\r\n\r\nCurrently I am attempting the following deployment:\r\n\r\n**Synology Reverse Proxy in front of bitwarden**\r\nbw.domain.com:80 -> localhost:8223 (hoping bitwarden redirects on x-forwarded-proto to https)\r\nbw.domain.com:443 -> localhost:8223 (using certificate on synology for bw.domain.com for ssl offload)\r\n\r\n**Run bitwarden.sh install**\r\nEnter domain: bw.domain.com\r\nUse Let's Encrypt: n\r\nDo you have an SSL certificate to use: n\r\nDo you want to use the default ports (80/443): n\r\nHTTP port: 8223\r\nInstallation behind reverse proxy: y\r\nDefault ports (80/443) on your reverse proxy: y\r\nPush notifications: y\r\n\r\nFrom this point, ports in the docker-compose.yml end up being 80 and 443 which clash with synology's webservers, which I had to manually change to 8223 and 8243 as a workaround.\r\nI'm under the impression 80 and 443 should have changed in the docker-compose.yml for the host ports. And really 443 should be removed if behind a reverse proxy with ssl-offload.\r\n\r\n**Run bitwarden.sh start**\r\nPulls containers\r\nStarting containers\r\nFails with bind mount errors for missing folders:\r\n```\r\nERROR: for api  Cannot start service api: Bind mount failed: '/volume1/docker/bwdata/core' does not exists\r\nERROR: for attachments  Cannot start service attachments: Bind mount failed: '/volume1/docker/bwdata/core/attachments' does not exists\r\nERROR: for identity  Cannot start service identity: Bind mount failed: '/volume1/docker/bwdata/core' does not exists\r\nERROR: for mssql  Cannot start service mssql: Bind mount failed: '/volume1/docker/bwdata/mssql/backups' does not exists\r\n```\r\n\r\nseems not all the folders are being created. If I manually create the folder structure the containers will run. This is the current existing folders after setup:\r\n```\r\nroot@nas:/volume1/docker# ll bwdata/\r\ntotal 36\r\ndrwxr-xr-x+ 8 root root 4096 Mar 26 14:35 .\r\ndrwxr-xr-x+ 5 root root 4096 Mar 26 14:34 ..\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:36 docker\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:35 env\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:35 identity\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:35 nginx\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:34 scripts\r\ndrwxr-xr-x+ 2 root root 4096 Mar 26 14:35 web\r\n```\r\n\r\nOther issue found after the manual changes, the email sent still shows http:// instead of https:// for the application base url. As a result since the nginx config doesn't redirect on http to https it will be insecure in its connection.\r\n\r\nCan anyone assist or help clarify if the process I'm using is wrong for bitwarden behind a reverse proxy with ssl offload. And the missing folders, could this be a result of an unsupported system (synology) or am I encountering something different.\r\n\r\nThank you"},"comment":{"url":"https://api.github.com/repos/bitwarden/core/issues/comments/377025617","html_url":"https://github.com/bitwarden/core/issues/244#issuecomment-377025617","issue_url":"https://api.github.com/repos/bitwarden/core/issues/244","id":377025617,"user":{"login":"kspearrin","id":1190944,"avatar_url":"https://avatars3.githubusercontent.com/u/1190944?v=4","gravatar_id":"","url":"https://api.github.com/users/kspearrin","html_url":"https://github.com/kspearrin","followers_url":"https://api.github.com/users/kspearrin/followers","following_url":"https://api.github.com/users/kspearrin/following{/other_user}","gists_url":"https://api.github.com/users/kspearrin/gists{/gist_id}","starred_url":"https://api.github.com/users/kspearrin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kspearrin/subscriptions","organizations_url":"https://api.github.com/users/kspearrin/orgs","repos_url":"https://api.github.com/users/kspearrin/repos","events_url":"https://api.github.com/users/kspearrin/events{/privacy}","received_events_url":"https://api.github.com/users/kspearrin/received_events","type":"User","site_admin":false},"created_at":"2018-03-28T20:30:19Z","updated_at":"2018-03-28T20:30:19Z","author_association":"OWNER","body":"That's really a development issue/bug, not a feature request. So you can open it here on GitHub."}}
{"actor":{"display_login":"kspearrin"}}