From b8ca1056027e549808246d31ff0381eccd5b1206 Mon Sep 17 00:00:00 2001 From: Tieme van Veen Date: Tue, 10 May 2016 10:56:22 +0200 Subject: [PATCH] Added 'vagrant reload' info on collision_error --- templates/locales/en.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/templates/locales/en.yml b/templates/locales/en.yml index 9db662f4b..481e9b754 100755 --- a/templates/locales/en.yml +++ b/templates/locales/en.yml @@ -1733,7 +1733,11 @@ en: Sometimes, Vagrant will attempt to auto-correct this for you. In this case, Vagrant was unable to. This is usually because the guest machine - is in a state which doesn't allow modifying port forwarding. + is in a state which doesn't allow modifying port forwarding. You could + try 'vagrant reload' (equivalent of running a halt followed by an up) + so vagrant can attempt to auto-correct this upon booting. Be warned + that any unsaved work might be lost. + fixed_collision: |- Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}. forwarding: Forwarding ports...