502 Bad Gateway on old and fresh install of Homestead

Posted 4 months ago by ChrisF79

I followed the 5.7 docs to a T on installing Homestead.

Homestead.yaml

ip: "192.168.10.10"
memory: 1048
cpus: 3
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/code
      to: /home/vagrant/code

sites:
    - map: wordpress.test
      to: /home/vagrant/code/wordpress.test

databases:
    - homestead

** /etc/hosts **

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1   localhost
192.168.10.10 wordpress.test

255.255.255.255 broadcasthost
::1             localhost

I can ping wordpress.test just fine and I can SSH into the Vagrant box and go straight to the wordpress.test folder under /home/vagrant/code/wordpress.test

However, when I go into my browser and go to http://wordpress.test I get:

502 Bad Gateway

nginx/1.15.6

Wordpress tries to redirect it to:

http://wordpress.test/wp-admin/setup-config.php

since it is a new installation. It just doesn't make sense.

sites-enabled/wordpress.test/

server {
    listen 80;
    listen 443 ssl http2;
    server_name .wordpress.test;
    root "/home/vagrant/code/wordpress.test";

    index index.html index.htm index.php;

    charset utf-8;



    location / {
        try_files $uri $uri/ /index.php?$query_string;

    }



    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log  /var/log/nginx/wordpress.test-error.log error;

    sendfile off;

    client_max_body_size 100m;

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php7.3-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;


        fastcgi_intercept_errors off;
        fastcgi_buffer_size 16k;
        fastcgi_buffers 4 16k;
        fastcgi_connect_timeout 300;
        fastcgi_send_timeout 300;
        fastcgi_read_timeout 300;
    }

    location ~ /\.ht {
        deny all;
    }

    ssl_certificate     /etc/nginx/ssl/wordpress.test.crt;
    ssl_certificate_key /etc/nginx/ssl/wordpress.test.key;
}

The /var/run/php/php7.3-fpm.sock does exist. I have no idea what's wrong.

Please sign in or create an account to participate in this conversation.

Reply to

Use Markdown with GitHub-flavored code blocks.