Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems access localhost (Chrome: ERR_EMPTY_RESPONSE) #374

Closed
felipefreitasnet opened this issue Oct 17, 2016 · 7 comments
Closed

Problems access localhost (Chrome: ERR_EMPTY_RESPONSE) #374

felipefreitasnet opened this issue Oct 17, 2016 · 7 comments

Comments

@felipefreitasnet
Copy link

Hello!

Recently formatted my macbook, and installed docker (see 1.12.1) and git to run laradock.
But when access http: // localhost I get the message ERR_EMPTY_RESPONSE (Google Chrome)

My project directory:
captura de tela 2016-10-17 as 00 21 25

My docker status:
captura de tela 2016-10-17 as 00 22 03

My hosts:
captura de tela 2016-10-17 as 00 22 47

Chrome Message:
captura de tela 2016-10-17 as 00 22 31

Anyone have any idea what can be?

** sorry for my English :(

Thanks!

@felipefreitasnet
Copy link
Author

UPDATE *****

The problem happens only with apache2, with nginx everything worked.

@calebfavor
Copy link

calebfavor commented Oct 17, 2016

@felipefreitasweb - I had the same problem, the issue is apache is not starting properly due to a config issue (if you check the logs you should see that apache is restarting over and over)

Extra quotes were added to the apache base image (webdevops/Dockerfile@b99e229) so you need to edit 2 files in your laradock folder.

docker-compose.yml: under Apache Server Container change
PHP_SOCKET="php-fpm:9000"
to
PHP_SOCKET=php-fpm:9000

Then in the apache/Dockerfile change:
ARG PHP_SOCKET="php-fpm:9000"
to
ARG PHP_SOCKET=php-fpm:9000

Cheers!

** Edit: fixing link
** Edit: removing env variable

@philtrep
Copy link
Member

@calebfavor Shouldn't ARG PHP_SOCKET="php-fpm:9000" be changed to ARG PHP_SOCKET=php-fpm:9000 instead?

@calebfavor
Copy link

@philtrep Possibly, I am not sure what the correct way is. However I don't see a reason not to reference the composer file directly.

@felipefreitasnet
Copy link
Author

It worked!
@calebfavor Worked perfectly! thanks! :D

I followed exactly what I said, look:

apache2/dockerfile
captura de tela 2016-10-17 as 19 58 00

docker-compose-yml
captura de tela 2016-10-17 as 19 57 42

And run: docker-compose build apache2

Thank you very much!

@calebfavor
Copy link

@felipefreitasweb No worries! As @philtrep mentioned, the arg should indeed be changed to ARG PHP_SOCKET=php-fpm:9000 rather than using the environment variable.

@philtrep
Copy link
Member

#375 should fix this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants