Yeah, that’s a problem.
Daniel Ellison

You’re welcome Daniel!

Another issue that I found is that when running vagrant up you need to make sure that SSH is enabled on your router gateway.

Also, to assist with setting up quickly you can clone Jarred Wasinger’s Ethereum development environment here, as well as installing Virtual Box and Vagrant, and running vagrant init and vagrant up in the directory where the Vagrant file is.

Also, if the specs on your machine aren’t great, like mine (I have 7.5 GiB of memory and an Intel® Core™ i3–2130 CPU @ 3.40GHz × 4 processor), then running a VM might be slow, so you can spin up a VM on a cloud service provider like AWS, with a guide on setting up the server like this one here and a guide on how to connect via SSH here. Again, this is another tip from Jared Wasinger.
Another point that I had an issue with was that Intel Virtualization Technology was not enabled, which caused an error when running Vagrant up, because Jared’s vagrant file uses a memory of 4096, e.g. the error is like this: Stderr: VBoxManage: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
. So unless you want to reduce this to below 3000 (and have a slower VM), then check your BIOS settings if this error occurs.
More details on my issues with running vagranta or setting up an Ethereum dev. environment are here.

Like what you read? Give James Ray a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.