Error: 504 Gateway-Timeout when all containers are up and healthy.

[Al3xTh3Gr3at]

Describe the bug
When starting ALv4 dev setup, the gui doesn't bring up the login page and has an error of "Error: 504 Gateway-timeout

To Reproduce
Steps to reproduce the behavior:

1. Go To /git/alv4/assemblyline-base/dev/depends
2. $docker-compose -f docker-compose-minimal.yml up -d --wait
3. Go to /git/alv4/assemblyline-base/dev/core
4. $docker-compose -f docker-compose.yml up -d --wait
5. Wait until all containers are started and healthy.
6. Open your browser and navigate to https://localhost
7. No local login option with Error: API Server unreachable, we will auto-reconnect once the server is back online...

Expected behavior
https://localhost brings up the AssemblyLine GUI.

Screenshots
If applicable, add screenshots to help explain your problem.

Workaround

1. run $docker inspect depends-nginx-1 and find the Gateway and IPAddress
2. 

3.Go To /git/alv4/assemblyline-base/dev/depends
4. nano docker-compose-minimal.yml (scroll to the bottom)
5. Make sure the IPs are in the same subnet.

Environment (please complete the following information if pertinent):

• Assemblyline Version: 4.5.0.29
• Browser: FireFox

[cccs-rs]

Is this with using the latest commit from assemblyline-base? Mostly because you reference 4.3.1.x as the version and we're currently on 4.5.0.x so I wonder if it's a bug that's since been patched.

[kam193]

Have you tried to restart Nginx container? I have an issue that Nginx is sometimes failing to find containers that weren't available when it was starting. I just restart Nginx container to fix it.

[Al3xTh3Gr3at]

Apologies, it is from the latest version..

[cccs-rs]

Running this myself, I haven't encountered any issues and in my case the gateway gets set to 172.24.0.1 which doesn't match the IP that's set for NGINX by default (172.17.0.1) but the default matches the IP shown for ip addr show docker0.

Perhaps in your system, the IP address for Docker is different and you may need to set that instead in the docker-compose.yml?

[Al3xTh3Gr3at]

Yup, setting it in the yml file fixed the issue! Thank you

…

On Fri, Jun 7, 2024, 09:21 cccs-rs ***@***.***> wrote: Running this myself, I haven't encountered any issues and in my case the gateway gets set to 172.24.0.1 which doesn't match the IP that's set for NGINX by default (172.17.0.1) but the default matches the IP shown for ip addr show docker0. Perhaps in your system, the IP address for Docker is different and you may need to set that instead in the docker-compose.yml? — Reply to this email directly, view it on GitHub <#234 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHMDGWKIJUBV557DB7HZJFLZGGXW7AVCNFSM6AAAAABI5A2RTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUHAZDONRQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>