Trellis Multisite - Fresh development setup not working at all?

trellis
1

(Note I’m on macOS Sierra if that makes a difference)

Can someone else please try setting up a fresh new Multisite development environment? I cannot get one going at all, following the docs exactly. Currently freezes at ‘vagrant up’ at:

==> default: Bindfs seems to not be installed on the virtual machine, installing now

with errors that it cannot resolve to us.archive.ubuntu.com.

Full error below. I believe this is an issue with Multisite and Landrush. There’s a lot of topics on this on this forum and PR’s dating back to 12 months ago but I can’t find any real answers other than wildcard domains (*.example.dev) being problematic, but since that time the whole site_hosts section of wordpress_sites has been redone.

Any ideas? I’ve had issues with deployment before needing to SSH into the staging/production server and installing Wordpress but this time I cannot even get development up and going.

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

apt-get update && apt-get install -y bindfs

Stdout from the command:

Err:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Err:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  bindfs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.7 kB of archives.
After this operation, 93.2 kB of additional disk space will be used.
Err:1 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 bindfs amd64 1.12.6-2
  Temporary failure resolving 'us.archive.ubuntu.com'


Stderr from the command:

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/universe/b/bindfs/bindfs_1.12.6-2_amd64.deb  Temporary failure resolving 'us.archive.ubuntu.com'

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
2

Update: Adding this to the Vagrantfile gets the entire deploy working. I can even SSH into the box and check if Wordpress is installed. All clear… I just can’t load the site in a browser (yet!)

config.landrush.guest_redirect_dns = false

Update 1: So I went back and recreated the VM of a previous Multisite install that I was having trouble with and can load that one fine. So not sure what the fresh install wasn’t loading (I noticed it wasn’t writing anything to /etc/hosts).

I’m still very curious to see if a fresh Multisite setup works for anyone else, because I think the line above might hopefully be a fix to a lot of Multisite issues being reported with Trellis…

Update 2: I was having an issue where the other sites I had made (e.g. subdomain.example.dev) weren’t loading. I added these subdomains to my /etc/hosts and they load okay (though with security warnings because of my self-signed certificate).

Update 3: I’ve since started a new multisite project that worked without problems, and didn’t need to do any of the above fixes. Though I did uninstall and reinstall landrush as it seemed to be causing most of the issues.

2 Likes
3

When Landrush is used, I don’t believe there is any entries made in /etc/hosts anyways.

I haven’t started a new Multisite project lately, I have one project which is updated to around August 14th and 0.9.8, so Multisite was working up until that point. I can post again if I have time to set up a new project with Multisite.

I don’t see any commits since 0.9.8 that would jump out as breaking Multisite. There are two commits I see that have to do with Multisite though:


1 Like
4

Running into this issue as well. Where did you insert the config.landrush.guest_redirect_dns = false line? Is that in the Vagrant.has_plugin?('landrush') block?

5

Can’t recall, sorry, but I did fix it by starting over. I know that’s small comfort… Also FWIW I’d recommend subfolders over subdirectories for MultiSite.

6

Any specific reason why you recommend subfolders? Other than avoiding landrush problems?

By starting over, do you mean running vagrant destroy and vagrant up or do you mean deleting the whole trellis directory and building a new installation?

7

Last time I just started over completely.

Subfolders are better during theme development because you can’t view with Browser Watch any of the of subdomain sites. And also with subdomains you need to set up a working DNS record for every subdomain for your Let’s Encrypt certificates. Gets very annoying if you’re adding sites later to have to keep doing that over and over.

1 Like