MDeLuise / plant-it

🪴 Self-hosted, open source gardening companion app
https://plant-it.org
GNU General Public License v3.0
686 stars 25 forks source link

Cannot connect to backend #85

Closed NascarUk closed 9 months ago

NascarUk commented 10 months ago

Avoid duplicated bug reports

Description

When I run the application on Linux with docker compose and the ports that have been previously discussed I keep getting this error. (This is using both custom docker-compose.yml and the example ones set out in the guide)

Expected behaviour

Correct connection to backend.

Steps to reproduce

Add docker-compose.yml , backend.env and frontend.env in your directory Run sudo docker-compose up -d

Local environment

Running in docker on linux vm. Other docker compose apps run fine. I have added the log file in which I think the error is occuring!

Additional info

_plant-it-backend-1_logs.txt

Please let me know if you need anymore info! I am super excited to get this up and running

MDeLuise commented 10 months ago

Hi @NascarUk, thanks for opening the issue! Can you please provide the content of the files (docker-compose.yml, backend.env, frontend.env) you're using?

NascarUk commented 10 months ago

Frontend.txt Backend.txt docker-compose.txt

MDeLuise commented 10 months ago

I tried to use your configuration and on my side no error, so this is strange. Before inspect deeply the configuration, could you double check the configuration and try to change the backend and frontend ports and start the docker compose please?

nykroy commented 9 months ago

I has the same error and on my case the problem was i has no permissions on db directory

MDeLuise commented 9 months ago

I'm closing this issue as there has been no new reply from the issuer for 2 weeks. If the problem persists even after checking the solution provided by @nykroy, please feel free to open another issue.

partywagon112 commented 9 months ago

I had the same thing, and had to resolve this note from the docs first: https://docs.plant-it.org/installation/configurations/#run-on-a-remote-host