{"action":"created","issue":{"url":"https://api.github.com/repos/CachetHQ/Cachet/issues/1545","repository_url":"https://api.github.com/repos/CachetHQ/Cachet","labels_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/1545/labels{/name}","comments_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/1545/comments","events_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/1545/events","html_url":"https://github.com/CachetHQ/Cachet/issues/1545","id":135774745,"number":1545,"title":"Issue wth generated page links behind a reverse proxy","user":{"login":"sebi-hgdata","id":11443582,"avatar_url":"https://avatars.githubusercontent.com/u/11443582?v=3","gravatar_id":"","url":"https://api.github.com/users/sebi-hgdata","html_url":"https://github.com/sebi-hgdata","followers_url":"https://api.github.com/users/sebi-hgdata/followers","following_url":"https://api.github.com/users/sebi-hgdata/following{/other_user}","gists_url":"https://api.github.com/users/sebi-hgdata/gists{/gist_id}","starred_url":"https://api.github.com/users/sebi-hgdata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebi-hgdata/subscriptions","organizations_url":"https://api.github.com/users/sebi-hgdata/orgs","repos_url":"https://api.github.com/users/sebi-hgdata/repos","events_url":"https://api.github.com/users/sebi-hgdata/events{/privacy}","received_events_url":"https://api.github.com/users/sebi-hgdata/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-02-23T15:46:14Z","updated_at":"2016-02-23T22:58:20Z","closed_at":"2016-02-23T15:54:20Z","body":"Hey,\r\n  We are running the cachethq/docker:latest behind our reverse proxy and it seems that all paths that are generated use 'http://our_domain' even if the APP_URL is set with 'https://our_domain'.\r\n  Now, we managed to resolve this by disabling compression in the container's nginx server and using mod_substitue, but there is still one issue with the invite and subscribe emails... these can be resolved that.\r\n\r\n  Don't know if there is a config in Cachet that resolves this or it's truly a bug? \r\n\r\n  Any help  would be appreciated.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/CachetHQ/Cachet/issues/comments/187953557","html_url":"https://github.com/CachetHQ/Cachet/issues/1545#issuecomment-187953557","issue_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/1545","id":187953557,"user":{"login":"sebi-hgdata","id":11443582,"avatar_url":"https://avatars.githubusercontent.com/u/11443582?v=3","gravatar_id":"","url":"https://api.github.com/users/sebi-hgdata","html_url":"https://github.com/sebi-hgdata","followers_url":"https://api.github.com/users/sebi-hgdata/followers","following_url":"https://api.github.com/users/sebi-hgdata/following{/other_user}","gists_url":"https://api.github.com/users/sebi-hgdata/gists{/gist_id}","starred_url":"https://api.github.com/users/sebi-hgdata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebi-hgdata/subscriptions","organizations_url":"https://api.github.com/users/sebi-hgdata/orgs","repos_url":"https://api.github.com/users/sebi-hgdata/repos","events_url":"https://api.github.com/users/sebi-hgdata/events{/privacy}","received_events_url":"https://api.github.com/users/sebi-hgdata/received_events","type":"User","site_admin":false},"created_at":"2016-02-23T22:58:20Z","updated_at":"2016-02-23T22:58:20Z","body":"Done some digging around and seems like my hunch was true. Because we can't integrate Cachet into our apache httpd deployment I made a workaround by adding ``` $this->app['request']->server->set('HTTPS', true); ``` in AppServiceProvider based on the following SO post http://stackoverflow.com/a/35258097"}}