-
Notifications
You must be signed in to change notification settings - Fork 241
502 Bad Gateway after set-up #130
Comments
docker inspect docker-magento2_web_1. |
Many thanks for the response @Aleksanteris. I tried running inspect on the web container and got this:
So I added this to /etc/hosts:
Checking the docker containers with $ docker ps -a | grep meanbee
Which looks about right doesn't it? However I got still get "magento2.docker refused to connect. " in my browser from http://magento2.docker and http://magento2.docker:32796/ and "Bad gatway from http://192.168.1.80:32801/ and http://192.168.1.80:32802/ I am getting to the varnish container with http://192.168.1.80:32802/ because I see it in the logs, but how to I diagnose the "Bad Gateway" response please? |
Got this from running docker logs on the web container:
|
Hey guys, I have the same issue on High Sierra; is there some news on it? |
set UPDATE_UID_GID=false in the global.env |
Also, have this issue. |
I'm not aware of anything specifically wrong with High Sierra. I've been using these images on that version of the OS without problem for a while. |
Running Windows 10. Exact same problems as described.
This worked for me. Remembering the quickstart asks you to create |
Same error for me |
Hi, seems to be related to the php container version used by default in docker-compose.yml. Update: Good luck, |
@benvansteenbergen with 7.1:
|
@benvansteenbergen and with 7.2: |
Magento 2 itself is not compatible with php 7.2 I believe it's something they're working on as part of 2.3 release They've got a lot to update though! |
Same here. 7.1 is not working on High Sierra. |
This is a magento 2 issue |
After setting |
@benhtn did you manage to solve this issue? I have the same problem |
@benvansteenbergen I recreated containers using php 7.1 (by setting meanbee/magento2-php:7.0-xxx->meanbee/magento2-php:7.1-xxx) and Magento 2.2 (by setting M2SETUP_VERSION=2.1.* -> M2SETUP_VERSION=2.2.*). And still I get 502 bad gateway. For me this is network issue, but I don't know how to solve it. When issuing |
docker-compose up -d
docker ps
docker-compose run --rm cli magento-command setup:store-config:set --base-url="http://magento2.docker:32785/"
|
@DominicWatts it looks like this helped, I managed to access magento webpage after setting this magic base-url. Thank you very much! |
Also have this problem, how do I fix it? Console shows
Docker ps output.
So to fix I need PHP 7.1 and to apply the mcrypt patch to one file? I have edited the php version in the docker-compose.yml and ran Still getting this Magento 2.2.5 Docker PS output after changing to PHP 7.1.
Unable to connect on localhost port 80 either. Edit:
In the global.env And adding port 80 to varnish resolved.
|
Try connecting localhost on port 32809 (see docker ps output). Or modify varnish port from 80 to 80:80 in your docker-compose.yml
Good luck!
Verstuurd vanaf mijn iPhone
… Op 7 dec. 2018 om 06:39 heeft Liam Mitchell ***@***.***> het volgende geschreven:
32809
|
@LiamKarlMitchell I'm using php 7.1. To avoid mcrypt issue I've just changed in docker-compose.yml line |
Same error for me, PHP 7.4 and Magento 2.4 |
@ndoublehwp did you find a solution? |
Hi there,
I am running this on a macbook with High Sierra, and Docker CE Version 18.06.0-ce-mac70 (26399).
I completed the quick set-up (all seemed fine with the magento installer), then guessing from the output of docker ps, I visited
http://localhost:32798
But I get 502 Bad Gateway - nginx/1.9.15
I also added a /etc/hosts entry to point to
127.0.0.1 magento2.docker
And tried visiting
http://magento2.docker:32798
But still the same.
I can see varnish running usingthe varnishlog command in the varnish container. I see the 502 error there too. e.g.
I tried disabling varnish (removing the block in docker-compose.yml and add the block for nginx), but after restart I cannot access anything (port 80 - refused to connect).
I can see nginx is running in the web container:
Can you give me any ideas/ can I provide further information to assist diagnosis?
The text was updated successfully, but these errors were encountered: