Really struggling getting everything up and running with docker compose and portainer #84
Replies: 2 comments
-
|
I was able to resolve this, maybe this is standard knowledge but I struggled with this for a while. I made the env variable for the url as follows, and redployed the stack.
|
Beta Was this translation helpful? Give feedback.
-
|
I'm having similar problems using portainer to manage the docker elements. Had this all working perfectly for a week and then it started telling me somethings wrong. I don't see anything in the container logs on portainer that indicate a problem, yet can log in to the web interface (ssl issues all good as i've tried http and https to see if that's the problem) and just get the something wrong see logs message. Any suggestion on troubleshooting with limited knowledge I have. I feel like I'm missing a step to locating /storage/logs on the terminal too. I can't find it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Having an issue with using the docker-compose file (no proxy) and Portainer stacks.
I think my issue boils down to the SITE_URL environment variable. I don't have a site that I can use, I was only hoping to test it out internally and access by IP address. However, if I enter in the IP address into that field, when I navigate to the Freescout login page, it looks off, and errors on login. Then the link to the homepage shows a url with duplicate IP address info like so:
The log for the freescout-app stops here:
And the hyperlink to the Homepage for Freescout is showing like this:

Here is my docker compose contents
Beta Was this translation helpful? Give feedback.
All reactions