Unable get it to run on an Ubuntu docker installation #639
-
Trying to run it in docker with compose. The web portal shows the home page fine, but clicking login/signup results in an DB server console logs show:
The backend container shows errors like this:
The front end container shows:
My compose file with changes I made:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
@DarthHeizenberg my setup is a bit different but I did spend a good hour or two with a similar issue. It all boiled down to me realising firstly there was not only one "frond end". So there is the web front end exposed but also the server front end, and both seemed to need domain names and be reverse proxied. That, and also the trusts needed to be specified correctly. So I have https://adventures.gadgeteerza.co.za as my web front end and have https://adventuresimages.gadgeteerza.co.za as the server domain. I also opted for the new db version, which is working fine. So in my case I have "both front ends" exposed to my reverse-proxy-net network with just the db only in the adventurelog network (the other two also part of this network). This is the docker-compose that is working for me and maybe it will help you troubleshoot what is out of sync - but it is lilley either the trust settings, or visibility of seeing the other container:port correctly.
|
Beta Was this translation helpful? Give feedback.
-
@Danie10, thanks again for your help! I got it to work by comparing your compose with mine. I'm not using a rev. proxy setup (all internal on the home network for now). I needed the container network defined like you have and not use square braces around the CSRF value (which is weird given that other bits of documentation around the web show that format). |
Beta Was this translation helpful? Give feedback.
-
@Danie10 it's a pleasure. I need to try to get my head around separating it into logical pieces and hope to do a video about this project soon. I'm not sure why that second domain name is required but it did confuse me quite a bit, made worse with the reverse proxy. But glad at l;east my partial bird's nest of a docker-compose helped. |
Beta Was this translation helpful? Give feedback.
@DarthHeizenberg my setup is a bit different but I did spend a good hour or two with a similar issue. It all boiled down to me realising firstly there was not only one "frond end". So there is the web front end exposed but also the server front end, and both seemed to need domain names and be reverse proxied. That, and also the trusts needed to be specified correctly.
So I have https://adventures.gadgeteerza.co.za as my web front end and have https://adventuresimages.gadgeteerza.co.za as the server domain. I also opted for the new db version, which is working fine.
So in my case I have "both front ends" exposed to my reverse-proxy-net network with just the db only in the adventurelog netw…