Sorry for a lengthy post. I’ve been stuck here for about 9 days.
Result of successful vagrant up --provision
The command vagrant up --provision was successful. I copied the output to a gist,
However, whenever I try to access the domain, http://trellis.local, I get “Unable to connect” in both FireFox and Chrome.
- Windows Version 10.0.18363 Build 18363
- WSL 1 running Ubuntu
- On WSL, ansible --version = 2.8.0 (also matches in vagrant.default.yml)
- vagrant 2.2.9 on both Windows and WSL.
- VirtualBox GUI Version 6.1.14 r140239 (Qt5.6.2)
Let me know if I missed something.
Is site key trellis.local the key for both vault.yml and wordpress_sites.yml? Is there a canonical listed?
Yes, and Yes, everything is trellis.local.
What does /etc/hosts look like?
Here is the full cat /etc/hosts output. Snippet:
127.0.1.1 trellis.local trellis ## vagrant-hostmanager-start 192.168.50.5 trellis.local 192.168.50.5 www.trellis.local ## vagrant-hostmanager-end
Can you ping trellis.local? How about 192.168.50.5?
Yes, here’s the result.
Can you run vagrant ssh?
Do you even have a bedrock site installed?
vagrant@trellis:/srv/www/trellis.local/current$ ls CHANGELOG.md composer.json composer.lock config LICENSE.md phpcs.xml README.md vendor web wp-cli.yml
Is nginx running?
Active: active (running) since Thu 2020-09-24 17:19:34 UTC; 9min ago
but there appears to be an error.
Sep 24 17:19:34 trellis systemd: nginx.service: Can't open PID file /var/run/nginx.pid (yet?) after start: No such fi
Here is the full output of sudo nginx service status.
Is MariaDB running?
Yes, here’s the receipt.
(out of desperation) Does the adapter used by VirtualBox for your Vagrant box show the same IPv4 address as vagrant-default.yml: 192.168.50.5?
VirtualBox is using two adapters, one is NAT, the other is Host-Only Ethernet Adapter #2. To check IPv4 address for Ethernet Adapter #2, go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Hover over each of the Ethernet adapters until you find the name of the one being used by VirtualBox. Right-click on the adapter > Properties > Double-click on Internet Protocol Version 4 (TCP/IPv4) -> Shows 192.168.50.5.
Does .bashrc allow WSL and Windows to “talk” to each other about VirtualBox?
Yes, I followed these instructions in the docs, replacing /mnt/c with /mnt/e to reflect VirtualBox installation path.
- First, I’m going to look into the nginx error in point 4 above.
- If that doesn’t work, I’ll look into something-something disable Windows firewall.
I’ve already tried starting fresh a couple times, with the same result each time.
Edit: By starting fresh, I mean re-cloning roots/trellis, not the example project.
However, at this point… Does anyone have any tips, please?