Bad gateway (502) error on localhost

[pravesh-kasare]

Checklist

• I've searched through the existing issues and this bug has never been reported before

Subject of the issue

Steps to reproduce

1. configured the G3W suite using docker compose on win 11 os
2. step by step configured the files
3. after running docker up -d and accessed the localhost:8080 web page displaced showing bad gate way instead of login page shown in readme file

Environment

• g3w-admin: 3.6
• g3w-client: 3.8.6
• browser: MS edge
• operating system: Win 11 desktop

Link to your project

No response

Additional info

No response

[pravesh-kasare]

[Raruto]

Hi @pravesh-kasare

#105 (comment)

The 502 (bad gateway) error is a bit more common when working with docker services.

Usually you just have to wait for the installation and/or starting of all services to finish completely.

Sometimes the server seems to be doing nothing special, so be very patient..

#105 (comment)

The docker container (which is a Linux OS) is trying to run windows-only compatible files.

Please try again after double checking line endings of your local files 👉 #69

👋 Raruto

[pravesh-kasare]

hi,
after executing

docker-compose up -d

Post GIS is running but g3w suite exiting

however after executing

docker compose -f docker-compose-dev.yml up -d

Both post GIS and G3W suite exiting..

with error:

time="2023-07-24T17:37:14+05:30" level=warning msg="Found orphan containers ([g3w-suite-docker-certbot-1 g3w-suite-docker-redis-1 g3w-suite-docker-nginx-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

Also --remove-orphans unknown command.

[pravesh-kasare]

and 502 bad gateway problem not solved

[pravesh-kasare]

[Raruto]

#105 (comment)
#105 (comment)
#105 (comment)

First of all, please don't use this platform not as a chat (think before posting, then post one comment at a time..).

As I've pointed out here 👉 #102 (comment), reporting to others your steps-by-step (in a detailed manner) is crucial to understanding what is going wrong.

---

502 bad gateway problem not solved

Overall, it's not clear what you're trying to achive since you're mixing docker development configs:

docker compose -f docker-compose-dev.yml up -d

with production configs:

docker-compose up -d

The 502 page is just an informational message and is only shown in the production version (when you work with docker containers you should think of it as the equivalent of a "maintenance page").

You should investigate server logs further if you suspect more serious problems.

Ultimately, I advise you to read again (and more carefully) all the necessary steps to follow to start working with docker in here and here.

If you're new to docker, please have a look at dedicated support forums like stackoverflow.com for any additional help and information.

👋 Raruto