Devilbox: 502 Bad Gateway to Devilbox Intranet

[taliptako]

ISSUE TYPE

• Bug Report

1. Host operating system and version: Fedora 32
2. (Windows) Native Docker or Docker Toolbox:
3. Docker version: Docker version 19.03.8, build afacb8b
4. Docker Compose version: 1.25.4
5. (Linux) Is SELinux enabled?: NO I disabled it
6. What git commit hash are you on?: 8c931cdf5636b08ffecd0c73cb40ec4afd239783

SUMMARY

I just clone the devilbox repo set my .env then run docker-compose command on fresh Fedora 32 installation. Now I'm having this 502 Bad Gateway error
Log says
2020/04/12 14:40:57 [error] 299#299: *12 connect() failed (113: No route to host) while connecting to upstream, client: 172.16.238.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://172.16.238.10:9000", host: "localhost"

OTHER INFORMATION

Start command

$ docker-compose up -d php mysql redis

log.zip

compose-env.zip

[taliptako]

This is related with docker cause it works on Ubuntu since i move to Ubuntu LTS 20.04 i'm gonna let F32 users think about this :)

[cytopia]

Thanks for the heads-up

[science695]

@taliptako Can you trace pinging and checking the routes between your host, the php/http container? (you might have to apt update and apt install some network tool packages on http)

You could also try installing an older version of docker (a couple minor versions back)...

If you have both ubuntu anf F32, try comparing the routing tables between the 2 setups.

[DorianLsl]

@taliptako @cytopia
Being on Fedora 32, I had that problem too! But after hours of tearing my hair out, I found the solution.
Once the containers are launched, do an "ifconfig", normally a network interface of type "aa-acXXXXXXffXc" will appear.
You just have to identify this interface as a trusted interface for the firewall :
```

• firewall-cmd --permanent --zone=trusted --add-interface=aa-acXXXXXXffXc
• firewall-cmd --reload