Cachet: Setting Site URL doesn't change most site links from localhost:<port>

[stlasalle]

This is a cross-post from https://github.com/CachetHQ/Docker/issues/262 as this repo seems to have a lot more activity...

cachet_ver: v2.3.13
docker version: 17.09.0-ce
docker-compose version: 1.17.1

I have just set up the docker image on a cloud server, and have set it up behind an nginx reverse proxy with SSL as mentioned at the bottom of this page. After having completed the initial setup, almost all the links still start with localhost:6789.

This shows the Site URL set by me, but when I hover over 'components' on the left panel I am still directed to localhost:6789/dashboard/components

From reading other github issues this seems related to Cachet issue #1545

Does anyone have any suggestions?

[jbrooksuk]

Are you running behind a proxy?

[Pacerino]

I have the same issue but not with the container. Im using Nginx with php7.0.
I have 2 Servers in the intranet. One for the Reverse Proxy with Nginx and the Cachet server itself.
I got it running and can see everything from the Internet but the links generated are pointing to the intranet IP address which lead me into a "Server not found" error from my browser.
Tried to setting the URL via APP_URL and in the database.

[stlasalle]

@jrbooksuk yes, it's behind an nginx reverse proxy.

[jbrooksuk]

You need to add your proxy IP to ./config/trustedproxy.php

[stlasalle]

Hi @jbrooksuk, this is for cachet-docker so I don't want to edit the PHP files directly as I'd have to re-edit them whenever the docker image is restarted. Is there a fix for docker?

[NeilHanlon]

The support for docker of this project is lackluster at best.

Really turning me off from this in general.

But yes, the application should force all urls to just use the site URL. It's up to the user to configure it correctly--especially for emails. I just got an email with a link using an IP address, not my configured hostname.

[farhank3389]

Has this been fixed for docker? @NeilHanlon @stlasalle were you able to find a solution to this?

[jbrooksuk]

The support for docker of this project is lackluster at best.

@NeilHanlon the support for Docker is contributed by @djdefi completely on his own time. Please feel free to contribute back, as Ryan is always reviewing and improving Docker. Thanks Ryan ❤️

[jbrooksuk]

Also, Docker issues must be opened at CachetHQ/Docker.