Closed urinal-cake closed 4 years ago
I had another developer that found that if you change
- TRUSTED_HOSTS=localhost,theIpOfYourHost
then it will work
@urinal-cake you are completely correct it's due to the trusted hosts setting. I'll create a bug to cover this and see if we can document it better.
@tobybatch I guess my confusion was that I've included the port with the hostname, Maybe you could point out in the doc that the port should be omitted.
Thanks for the support!
This issue's solution is not complete... Quoting @urinal-cake I had another developer that found that if you change
Excellent solution if one were to know WHERE to change that. It exists in only in two .json files on my system. Both files buried way deep down inside /var/lib/docker which to me appears to be the wrong place to change it.
I tried prefacing my docker command with that variable. No dice still my host is untrusted... No idea where to go from here...
Again, this may be an issue with my lack of reading documentation properly, or not having the correct setup. Are there pre-requisites that I'm not aware of? Does the docker-compose properly take care of downloading and handling nginx?
Describe the bug After starting the docker containers with the command 'docker-compose up -d' and navigating to the IP of the host that has kimai installed, the application in any browser displays a message that the host is untrusted. This appears to be a Symfony issue that, after researching, may be related to the docker-compose file not being correctly configured?
To Reproduce Steps to reproduce the behaviour:
sudo git clone https://github.com/tobybatch/kimai2.git kimai
sudo cd /opt/kimai
docker-compose up -d
Desktop (please complete the following information):
Command used to run the container
docker-compose up -d
Docker compose file (with passwords redacted)
Additional context Fresh new virtual machine with nothing but docker and docker-compose installed. Also, excuse me if I'm missing some crucial steps. I'm new to a fair bit of this.