VVV: Bug: Windows: Network connection issues found. Unable to reach

What was The Command Used To Provision

vagrant up --provision

What Kind of VVV Provision Was This

This was a reprovision of an already working VVV

Logs/What Broke

I’ve tried to add a new site and provision but got errors connecting to hosts.

 ▷ Running the 'main' provisioner...
 ▷ Running init hook
 * Bash profile setup and directories.
 * Reloading SSH Daemon
 * checking Ubuntu version
 ✔ Finished init hook in 19s
 * Testing network connection to https://ppa.launchpadcontent.net with wget -q --spider --timeout=5 --tries=3 https://ppa.launchpadcontent.net
 ! Network connection issues found. Unable to reach https://ppa.launchpadcontent.net
 * Testing network connection to https://wordpress.org with wget -q --spider --timeout=5 --tries=3 https://wordpress.org
 ! Network connection issues found. Unable to reach https://wordpress.org
 * Testing network connection to https://github.com with wget -q --spider --timeout=5 --tries=3 https://github.com
 ! Network connection issues found. Unable to reach https://github.com
 * Testing network connection to https://raw.githubusercontent.com with wget -q --spider --timeout=5 --tries=3 https://raw.githubusercontent.com
 ! Network connection issues found. Unable to reach https://raw.githubusercontent.com
 * Testing network connection to https://getcomposer.org with wget -q --spider --timeout=5 --tries=3 https://getcomposer.org
 ! Network connection issues found. Unable to reach https://getcomposer.org
 * Testing network connection to https://deb.nodesource.com with wget -q --spider --timeout=5 --tries=3 https://deb.nodesource.com
 ! Network connection issues found. Unable to reach https://deb.nodesource.com
 * Testing network connection to https://mirror.rackspace.com with wget -q --spider --timeout=5 --tries=3 https://mirror.rackspace.com
 ! Network connection issues found. Unable to reach https://mirror.rackspace.com
#################################################################
 
! Warning! Network Problems:
 
VVV tried to check several domains it needs for provisioning but 7 of 7 failed:
 
 [x] https://ppa.launchpadcontent.net|
 [x] https://wordpress.org|
 [x] https://github.com|
 [x] https://raw.githubusercontent.com|
 [x] https://getcomposer.org|
 [x] https://deb.nodesource.com|
 [x] https://mirror.rackspace.com|
 
Make sure you have a working internet connection, that you 
restarted after installing VirtualBox/Parallels/Vagrant, and that 
they aren't blocked by a firewall or security software.
If you can load the address in your browser, then VVV should
be able to connect.
 
Also note that some users have reported issues when combined
with VPNs, disable your VPN and reprovision to see if this is
the cause.
 
Additionally, if you're at a contributor day event, be kind,
provisioning involves downloading things, a full provision may 
ruin the wifi for everybody else :(
 
Network ifconfig output:
 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::a00:27ff:feb1:285d  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:b1:28:5d  txqueuelen 1000  (Ethernet)
        RX packets 3049  bytes 356876 (356.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2258  bytes 391211 (391.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.56.4  netmask 255.255.255.0  broadcast 192.168.56.255
        inet6 fe80::a00:27ff:fe92:a226  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:92:a2:26  txqueuelen 1000  (Ethernet)
        RX packets 13  bytes 2734 (2.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 51  bytes 6764 (6.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 128  bytes 10544 (10.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 128  bytes 10544 (10.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 
Try provisioning again once network connectivity is restored.
If that doesn't work, and you're sure you have no VPNs and a strong 
internet connection, open an issue on GitHub, and include the 
output above so that the problem can be debugged
 
vagrant halt
vagrant up --provision
 
https://github.com/Varying-Vagrant-Vagrants/VVV/issues
 
#################################################################
 ==================================================================================================
 ! If this check fails despite succeeding in the browser, contact us in Slack or GitHub immediately
 ==================================================================================================
 * Apt package install pre-checks
 ▷ Running before_packages hook
 * Setting up MySQL configuration file links...
 * mysql group exists
 * mysql user present and has uid 9001
 * Copying /srv/provision/core/mariadb/config/vvv-core.cnf to /etc/mysql/conf.d/vvv-core.cnf
 * Copying PHP configs
 * Checking supplementary PHP configs
 ✔ Finished before_packages hook in 0s
 * Registering apt keys
 ▷ Running register_apt_keys hook
 ✔ Finished register_apt_keys hook in 1s
 * Registering apt sources
 ▷ Running register_apt_sources hook
 * git-core/ppa already present, skipping
 * installing MariaDB apt sources
 ✔ Finished register_apt_sources hook in 0s
 * Upgrading apt packages
 * Updating apt keys
gpg: key 3B4FE6ACC0B21F32: 3 signatures not checked due to missing keys
gpg: key 3B4FE6ACC0B21F32: "Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>" not changed
gpg: key D94AA3F0EFE21092: 3 signatures not checked due to missing keys
gpg: key D94AA3F0EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>" not changed
gpg: key 871920D1991BC93C: 1 signature not checked due to a missing key
gpg: key 871920D1991BC93C: "Ubuntu Archive Automatic Signing Key (2018) <ftpmaster@ubuntu.com>" not changed
gpg: Total number processed: 3
gpg:              unchanged: 3
 * Running apt-get update...
Err:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Err:2 http://ppa.launchpad.net/git-core/ppa/ubuntu focal InRelease
  Temporary failure resolving 'ppa.launchpad.net'
Err:3 https://mirror.rackspace.com/mariadb/repo/10.5/ubuntu focal InRelease
  Temporary failure resolving 'mirror.rackspace.com'
Err:4 https://nginx.org/packages/mainline/ubuntu focal InRelease
  Temporary failure resolving 'nginx.org'
Err:5 https://ppa.launchpadcontent.net/ondrej/php/ubuntu focal InRelease
  Temporary failure resolving 'ppa.launchpadcontent.net'
Err:6 https://packagecloud.io/github/git-lfs/ubuntu focal InRelease
  Temporary failure resolving 'packagecloud.io'
Err:7 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Err:8 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Err:9 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
  Temporary failure resolving 'us.archive.ubuntu.com'
Reading package lists...
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/focal/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/focal-security/InRelease  Temporary failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch http://ppa.launchpad.net/git-core/ppa/ubuntu/dists/focal/InRelease  Temporary failure resolving 'ppa.launchpad.net'
W: Failed to fetch https://packagecloud.io/github/git-lfs/ubuntu/dists/focal/InRelease  Temporary failure resolving 'packagecloud.io'
W: Failed to fetch https://mirror.rackspace.com/mariadb/repo/10.5/ubuntu/dists/focal/InRelease  Temporary failure resolving 'mirror.rackspace.com'
W: Failed to fetch https://nginx.org/packages/mainline/ubuntu/dists/focal/InRelease  Temporary failure resolving 'nginx.org'
W: Failed to fetch https://ppa.launchpadcontent.net/ondrej/php/ubuntu/dists/focal/InRelease  Temporary failure resolving 'ppa.launchpadcontent.net'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 * Registering apt packages to install
 ▷ Running register_apt_packages hook
 ✔ Finished register_apt_packages hook in 0s
 * Main packages check and install.
 * Checking for apt packages to remove.
 * No apt packages to remove
 * Checking for apt packages to install.
 * No apt packages to install
 * Running after_packages
 ▷ Running after_packages hook
false
false
 * Adding Mailhog service file
 * Enabling MailHog Service
 * Starting MailHog Service
 * Started MailHog Service
 * Checking for NVM
 ✓ NVM is already installed, checking for updates
fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Could not resolve host: github.com
 ! The 'main' provisioner ran into problems, the full log is available at '/var/log/provisioners/2024.06.11_13-49-05/provisioner-main.log'. It completed in 161 seconds.
---
sites:
  # latest version of WordPress, can be used for client work and testing
  # Check the readme at https://github.com/Varying-Vagrant-Vagrants/custom-site-template
  # wordpress-one:
  #   skip_provisioning: false
  #   description: "A standard WP install, useful for building plugins, testing things, etc"
  #   repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
  #   hosts:
  #     - one.wordpress.test
  #   custom:
  #     wpconfig_constants:
  #       WP_DEBUG: true
  #       WP_DEBUG_LOG: true
  #       WP_DISABLE_FATAL_ERROR_HANDLER: true # To disable in WP 5.2 the FER mode

  piwnicasmakow:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - piwnicasmakow.test
    custom:
      wp_type: none
    nginx_upstream: php83

  brixani:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - brixani.test
    nginx_upstream: php80

  excitingpoland:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - excitingpoland.test
    nginx_upstream: php80

  greenfox:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - greenfox.test
    nginx_upstream: php80

  amtrener:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - amtrener.test
    nginx_upstream: php80

  base:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - base.test
    custom:
      wp_type: none
    nginx_upstream: php83

  cedo:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - cedo.test
    custom:
      wp_type: none
    nginx_upstream: php83

  paluchruda:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - paluchruda.test
    custom:
      wp_type: none
    nginx_upstream: php83

  inspiracje:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - inspiracje.test
    custom:
      wp_type: none
    nginx_upstream: php80

  depcoreagency:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - depcoreagency.test
    custom:
      wp_type: none
    nginx_upstream: php83

  depcore:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - depcore.test
    custom:
      wp_type: none
    nginx_upstream: php83

  gfp:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - gfp.test
    custom:
      wp_type: none
    nginx_upstream: php83

  vidocq:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - vidocq.test
    custom:
      wp_type: none
    nginx_upstream: php83

  opinia:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - opinia.test
    custom:
      wp_type: none
    nginx_upstream: php83

  pickpocket:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - pickpocket.test
    custom:
      wp_type: none
    nginx_upstream: php83

  prodoo:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - prodoo.test
    custom:
      wp_type: none
    nginx_upstream: php83

  tias:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - tias.test
    custom:
      wp_type: none
    nginx_upstream: php83

  paclan:
    repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template.git
    hosts:
      - paclan.test
    custom:
      wp_type: none
    nginx_upstream: php83

extensions:
  core: # The core VVV extensions
    - tls-ca # HTTPS SSL/TLS certificates
    - phpmyadmin # Web based database client
    #- memcached-admin # Object cache management
    #- opcache-status # opcache management
    #- webgrind # PHP Debugging
    #- mongodb # needed for Tideways/XHGui
    #- tideways # PHP profiling tool, also installs xhgui check https://varyingvagrantvagrants.org/docs/en-US/references/tideways-xhgui/
    - nvm # Node Version Manager
    #- php74
    - php80
    - php81
    - php83

# vm_config controls how Vagrant provisions the virtual machine, and can be used to
# increase the memory given to VVV and the number of CPU cores.
# It can also be used to override the default provider being used within Vagrant.

vm_config:
  memory: 2048
  cores: 2
  # as Vagrant currently restricts you to one provider per machine
  # https://www.vagrantup.com/docs/providers/basic_usage.html#vagrant-up
  # provider: virtualbox
  # provider: hyperv
  # provider: parallels
  # provider: vmware_desktop
  # provider: docker

# General VVV options
general:
  db_backup:
    enable: false
    gzip: true
    #exclude:
    #  - wordpress-trunk

  db_restore: false
  db_share_type: false
  #github_token: xxxxxx

vagrant-plugins:
  disksize: 10GB # requires the disk size vagrant plugin

Steps to Reproduce (for bugs)

Your Environment

Operating System: Windows


\ V\ V\ V / v3.13 Ruby:3.1.4, Path:“C:/strony/sites” _/_/_/ git::develop(c4250187)

Platform: mingw32 windows missingWinAdminPriv vagrant-hostsupdater vagrant-goodhosts vagrant-vbguest monochrome-terminal shared_db_folder_disabled Vagrant: v2.4.1, virtualbox: v7.0.18

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 33 (21 by maintainers)

Most upvoted comments

changing the ip address in /etc/resolv.conf

If I remember right this is a generated file, by turning off the VM and turning it back on as part of a provision you’ve probably erased your DNS changes.

changing the file step 3 (Method 2: The not-so-easy way) from https://learnubuntu.com/change-dns-server/

This article backsup the temporary part of the above.

Take a look at Netplan. My next step with that PR was to figure out a netplan YAML file to drop in to add the DNS servers. Modifying an existing netplan YAML file in the VM and applying it should also work.

You definitely don’t need to install resolvectl etc, it should all be doable with what’s already there.

There is a chance your VM has a much older Ubuntu version that doesn’t use this system though.

I’ve went to Virtualbox forum https://forums.virtualbox.org/viewtopic.php?t=94277

Those are all Windows errors and Windows error logs, totally unrelated to what you’re dealing with. If you had the issues that thread is talking about then the provisioners would never have started in the first place and you’d be seeing vagrant errors not provisioner errors.

reinstalled vagrant, VB again - removed, added network interfaces

This rarely fixes problems and usually causes new ones! Unless you’re seeing a VirtualBox or Vagrant error don’t touch these!

turned the firewall off

If the host WIndows OS also had this issue then that might have been the cause, you should turn it back on.

Im still getting ’ Network connection issues found. Unable to reach https://ppa.launchpadcontent.net/’ when provisioning

The provisioner network checks are there to check if it’s safe to continue and help diagnose issues. Some people can provision even when these checks fail and had to disable them manually, we do not know why.

These should be treated as informational and not as an error. Most people who encounter this do so because they didn’t bother to reboot their machine after updating/installing VirtualBox. The problem you’re facing is actually further down in the apt-get update step where it can’t resolve the hosts for packages.