date:20180130

[vagrant-up] Configuration of the /etc/network/interfaces and /etc/dhcp/dhcpd.conf by Vagrantfile?

2018-01-30 Thread _nobody_ _nobody_



Hello to everyone,


I have an interesting question here: Can I provide by Vagrantfile the 
configuration of /etc/network/interfaces, namely, can I add in the 
etc/network/interfaces the following:


# The USB-Ethernet interface 2
allow-hotplug eth2
iface eth2 inet dhcp


The another question is: can I define by Vagrantfile the following 
dhcpd.conf file?
/etc/dhcp/dhcpd.conf : /etc/dhcp/dhcpd.conf

I have set it like this:


## cat /etc/dhcp/dhcpd.conf
##
## DHCP Server Configuration file.
##   see /usr/share/doc/dhcp-server/dhcpd.conf.example
##   see dhcpd.conf(5) man page
##

default-lease-time 600;
max-lease-time 18000;

subnet 192.168.15.0 netmask 255.255.255.0 {
##   interface enp0s25;
   range dynamic-bootp 192.168.15.100 192.168.15.200;
   option broadcast-address 192.168.15.255;
   next-server 192.168.15.2;
   option subnet-mask 255.255.255.0;
}

host bbb {
   hardware ethernet D0:5F:B8:FF:F8:69;
   fixed-address 192.168.15.20;
   filename "bbb-image";
}

host pdu {
   hardware ethernet 88:b6:27:01:62:43;
   fixed-address 192.168.15.21;
   filename "pdu-image";
}


Or I can import the files, written in some other languages (.xml, .json, 
.jinja2 or something else)?


Any examples of the shelf for these cases?


Thank you,
Zoran (I use this account, since my primary account is on other three Open 
Source mailing lists)


-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/7b7a6c7b-4e85-4fb1-889c-e6e549196bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Laravel cannot make secure connection to server by domain name. Localhost:8000 works

2018-01-30 Thread Alvaro Miranda Aguilera

vagrant by default wouldnt set that

perhaps you had a plugin that now is gone?

hostmanager ?

On Tue, Jan 30, 2018 at 6:28 PM,  wrote:

> I am fairly new to web programming and have come into a tough problem. In
> the past I would be able to access a larvel site by running the command
> "vagrant up" in the homestead folder and then using the site name that I
> indicated in the "Homestead.yaml" file.
>
> Recently I updated my Mac to the latest version of High Sierra. I do not
> know if this is the main culprit, but for some reason now I am unable to
> reach the site by using the domain. I am however able to reach the laravel
> home page by going to localhost:8000.
>
> here is a list of things that I have done trying to fix the issue:
> I have tried uninstalling virtual box, homestead, and vagrant and
> reinstalling them but that has not fixed the issue.
> I tried running vagrant -provisions but that did not help the situation
> Here are my files:
>
> Homestead.yaml
>
> ip: "192.168.10.10"
> memory: 2048
> cpus: 1
> provider: virtualbox
>
> authorize: ~/.ssh/id_rsa.pub
>
> keys:
> - ~/.ssh/id_rsa
>
> folders:
> - map: ~/Code
>   to: /home/vagrant/Code
>
> sites:
> - map: hoomestead1.app
>   to: /home/vagrant/Code/Project1/public
> - map: lxa.app
>   to: /home/vagrant/Code/lxa/public
> - map: beerstreet.app
>   to: /home/vagrant/Code/beerstreet/public
> - map: blackbook.app
>   to: /home/vagrant/Code/blackbook/public
>
> databases:
> - homestead
>
> # blackfire:
> # - id: foo
> #   token: bar
> #   client-id: foo
> #   client-token: bar
>
> # ports:
> # - send: 5
> #   to: 5000
> # - send: 
> #   to: 777
> #   protocol: udp
>
>
> Host Files
>
> ##
> # Host Database
> #
> # localhost is used to configure the loopback interface
> # when the system is booting.  Do not change this entry.
> ##
> 127.0.0.1   localhost
> 255.255.255.255 broadcasthost
> ::1 localhost
>
> 192.168.10.10  homestead.app
> 192.168.10.10  hoomestead1.app
> 192.168.10.10  lxa.app
> 192.168.10.10  beerstreet.app
> 192.168.10.10  blackbook.app
>
> I really have no clue what the problem could be. It was working fine a day
> ago and now will not work. Can anyone please give me a suggestion on things
> I haven't tried yet and should?
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/3aaacdd2-df71-4ec0-a6e9-192a4e8a7351%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezat9kV4dxnRkqrZ9A%3DhnmqTUkdZoNg-bVgv5SrO7Kmfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Multi-machine Vagrantfile driving me loopy (!)

2018-01-30 Thread Jerry Steele

I'm trying to bring up some DO boxes in vagrant

# vim: ft=ruby

Vagrant.configure('2') do |config|

  cluster = {
0 => { 
  'name' => 'backups', 
  'image' => 'ubuntu-16-04-x64' 
},
1 => {
  'name' => 'client1',
  'image' =>  'debian-9-x64'
},
2 => {
  'name' => 'client2',
  'image' =>  'debian-8-x64'
},
3 => {
  'name' => 'client3',
  'image' =>  'ubuntu-16-04-x64'
  }
 } 

  config.vm.provision "ansible" do |ansible|
ansible.playbook = "playbook/site.yml"
ansible.host_vars = {

}
  end

  cluster.each do |i, machine|
config.vm.define "#{machine['name']}" do |machine_id|
  machine_id.ssh.private_key_path = '~/.ssh/id_rsa.digitalocean'
  machine_id.vm.box = 'digital_ocean'
  machine_id.vm.hostname = "#{machine_id['name']}"
  machine_id.image = "#{machine_id['image']}"

  machine_id.vm.provider :digital_ocean do |provider, override|
override.vm.box_url = 
"https://github.com/devopsgroup-io/vagrant-digitalocean/raw/master/box/digital_ocean.box;
provider.token = `echo $DO_API_TOKEN`
provider.region = 'lon1'
provider.size = 's-1vcpu-1gb'
  end
end
  end
end


As you can see, the variables will be the hostname and the image used for 
each box. I found something like the obvoe online and have tried to adapt 
it, but I've had massive problems. I'm still a bit new to Ruby, and am 
having some problems with the syntax. At this point, I get errors like:


vm:
* The hostname set for the VM should only contain letters, numbers,
hyphens or dots. It cannot start with a hyphen or dot.

Vagrant:
* Unknown configuration section '[]'.
* Unknown configuration section 'image='.


Obviously the interpolation is not working. Any idea where to start with 
this? I think I just need a bit of extra knowledge to work out where I'm 
going wrong with both Vagrant and loops in Ruby.

Thanks

Jerry

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/41cb870c-179f-4dd8-bf1f-14090a410f57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Laravel cannot make secure connection to server by domain name. Localhost:8000 works

2018-01-30 Thread totifercuervo



I am fairly new to web programming and have come into a tough problem. In 
the past I would be able to access a larvel site by running the command 
"vagrant up" in the homestead folder and then using the site name that I 
indicated in the "Homestead.yaml" file.

Recently I updated my Mac to the latest version of High Sierra. I do not 
know if this is the main culprit, but for some reason now I am unable to 
reach the site by using the domain. I am however able to reach the laravel 
home page by going to localhost:8000.

here is a list of things that I have done trying to fix the issue:
I have tried uninstalling virtual box, homestead, and vagrant and 
reinstalling them but that has not fixed the issue.
I tried running vagrant -provisions but that did not help the situation
Here are my files:

Homestead.yaml

ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
- ~/.ssh/id_rsa

folders:
- map: ~/Code
  to: /home/vagrant/Code

sites:
- map: hoomestead1.app
  to: /home/vagrant/Code/Project1/public
- map: lxa.app
  to: /home/vagrant/Code/lxa/public
- map: beerstreet.app
  to: /home/vagrant/Code/beerstreet/public
- map: blackbook.app
  to: /home/vagrant/Code/blackbook/public

databases:
- homestead

# blackfire:
# - id: foo
#   token: bar
#   client-id: foo
#   client-token: bar

# ports:
# - send: 5
#   to: 5000
# - send: 
#   to: 777
#   protocol: udp


Host Files

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1   localhost
255.255.255.255 broadcasthost
::1 localhost

192.168.10.10  homestead.app
192.168.10.10  hoomestead1.app
192.168.10.10  lxa.app
192.168.10.10  beerstreet.app
192.168.10.10  blackbook.app

I really have no clue what the problem could be. It was working fine a day 
ago and now will not work. Can anyone please give me a suggestion on things 
I haven't tried yet and should?

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/3aaacdd2-df71-4ec0-a6e9-192a4e8a7351%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Extending a drive size using the vagrant vmware provider?

2018-01-30 Thread Jesse House

I was hoping to script it in the Vagrantfile, it is easy to do after the 
fact using the VMWare GUI - guess I'll just do that and call it good

On Tuesday, January 30, 2018 at 12:14:41 AM UTC-8, Alvaro Miranda Aguilera 
wrote:
>
> better create a new VM thats fit for what you need.
>
> Alvaro.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/455541b5-e970-4ef5-83b4-c5dcf92d6387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Digest for vagrant-up@googlegroups.com - 7 updates in 4 topics

2018-01-30 Thread Clinton Gallagher

I requested 192.168.50.4 in the browser and the vvv.test page loaded with
the following problem notification...

*Problem:* Could not load the site, this implies that provisioning the site
failed, please check there were no errors during provisioning, and
reprovision.

*Note, sometimes this is because provisioning hasn't finished yet, if it's
still running, wait and refresh the page.* If that doesn't fix the issue, see
here for troubleshooting step



// That said PhpInfo runs without problem from that IP

http://192.168.50.4/phpinfo/s


I don't know if I've been clear. I have no problem loading projects or
using the browesr to request sites once I run vagrant up. The problem has
been PhpStorm configuration that doesn;t want to debug the remote server
(VVV/Vagrant)

There's too many PhpStorm configuration settings I don't know what to try
next


On Tue, Jan 30, 2018 at 5:28 AM,  wrote:

> vagrant-up@googlegroups.com
> 
>  Google
> Groups
> 
> 
> Topic digest
> View all topics
> 
>
>- Extending a drive size using the vagrant vmware provider?
><#m_6100356756631765649_group_thread_0> - 2 Updates
>- [ANN] Vagrant 2.0.2 <#m_6100356756631765649_group_thread_1> - 1
>Update
>- SSH-2.0-OpenSSH - Protocol mismatch.
><#m_6100356756631765649_group_thread_2> - 2 Updates
>- Debugging w/ PhpStorm <#m_6100356756631765649_group_thread_3> - 2
>Updates
>
> Extending a drive size using the vagrant vmware provider?
> 
> Jesse House : Jan 29 05:00PM -0800
>
> Does anyone know the proper vagrant vmx configuration to increase the hard
> drive space via Vagrantfile (or maybe it is not possible?)
>
> Thanks,
>
> See: https://github.com/hashicorp/vagrant/issues/8853
> Alvaro Miranda Aguilera : Jan 30 09:14AM +0100
>
> better create a new VM thats fit for what you need.
>
> Alvaro.
> Back to top <#m_6100356756631765649_digest_top>
> [ANN] Vagrant 2.0.2
> 
> Chris Roberts : Jan 29 04:57PM -0800
>
> Hi everyone,
>
> I'm happy to announce the release of Vagrant 2.0.2. This release includes
> a
> number of bug fixes, enhancements, and some new features. Notable updates
> include:
>
> * Updated SMB synced folder implementation
> * Addition of macOS host support to SMB synced folders
> * Improved NFS service detection and interactions
> * Sensitive values handling in Vagrant output
>
> Many more updates and fixes are included in this release. See the
> changelog
> for a complete list:
>
> https://github.com/hashicorp/vagrant/blob/v2.0.2/CHANGELOG.md
>
> Download the latest release:
>
> https://www.vagrantup.com/downloads.html
>
> Cheers!
> - Chris
> Back to top <#m_6100356756631765649_digest_top>
> SSH-2.0-OpenSSH - Protocol mismatch.
> 
> Mohamed Hamed : Jan 29 04:34AM -0800
>
> Dear Alvaro
>
> i have to install openio on vagrant so i have the same problem can you
> help
> me to solve this problem ..
>
> i don't know what is your meaning can i Share your Vagrantfile 
>
>
> On Friday, September 18, 2015 at 6:07:25 AM UTC+2, Alvaro Miranda Aguilera
> wrote:
> Alvaro Miranda Aguilera : Jan 29 07:04PM +0100
>
> you just reply to a 2015 email, i doubt the issue is near close
>
> can you send a new email and describe
>
> what you want to do
> what is not working
> what files are you using
> what errors you get what do you see
>
> etc, any information that can help to understand
>
>
> Thanks
>
>
> On Mon, Jan 29, 2018 at 1:34 PM, Mohamed Hamed  >
> wrote:
>
>
> --
> Alvaro
> Back to top <#m_6100356756631765649_digest_top>
> Debugging w/ PhpStorm
> 
> Clinton Gallagher : Jan 29 09:52AM -0600
>
> Don't understand what you are suggesting Alvaro. Where and what do you
> suggest I edit to use 192.168.50.4
>
> On Sat, Jan 27, 2018 at 2:40 AM, Alvaro Miranda Aguilera
>
> --
> Clinton Gallagher
> tapABILITIES, LLC
> Wauwatosa, Milwaukee County, USA
> TEL 414-774-2557 <(414)%20774-2557> Central
> CEL 414-243-8211 <(414)%20243-8211>
> WWW tapabilities.com
> @tapABILITIES
> Alvaro Miranda Aguilera

[vagrant-up] Re: vagrant up stuck waiting for machine to boot unless VMware Workstation GUI console is open

2018-01-30 Thread Mark Fletcher

Confirming this issue is still present in Vagrant 2.0.2

On Thursday, 18 January 2018 15:08:48 UTC-6, Mark Fletcher wrote:
>
> I can confirm that I can replicate this on my machine.
>
> Setup
> Host OS: fedora 27 workstation
> Vagrant Version: vagrant 2.0.1
> Vagrant Plugin List: vagrant-share 1.1.9, vagrant-vmware-workstation 5.0.4
> VMWare Workstation: 14.1.1 build 7528167
> Boxes used: bento/ubuntu-16.04, puppetlabs/ubuntu-16.04-64-nocm
>
>
> On Tuesday, 2 January 2018 13:48:28 UTC-6, Lucas Rangit Magasweran wrote:
>>
>> Consistently, Vagrant boxes are stuck waiting for machine to boot until I 
>> open the VMware Workstation GUI and leave it open. I'm using VMware 
>> Workstation 12.5.7 on Ubuntu Linux 16.04 64-bit with Vagrant 2.0.0 and 
>> provider plugin vagrant-vmware-workstation 5.0.1.
>>
>> This error is reproducible if I close the GUI and try to halt and up the 
>> Vagrant box again. 
>>
>> Bringing machine 'default' up with 'vmware_workstation' provider...
>> ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
>> ==> default: Verifying vmnet devices are healthy...
>> ==> default: Preparing network adapters...
>> WARNING: The VMX file for this box contains a setting that is 
>> automatically overwritten by Vagrant
>> WARNING: when started. Vagrant will stop overwriting this setting in an 
>> upcoming release which may
>> WARNING: prevent proper networking setup. Below is the detected VMX 
>> setting:
>> WARNING: 
>> WARNING:   ethernet0.pcislotnumber = "33"
>> WARNING: 
>> WARNING: If networking fails to properly configure, it may require this 
>> VMX setting. It can be manually
>> WARNING: applied via the Vagrantfile:
>> WARNING: 
>> WARNING:   Vagrant.configure(2) do |config|
>> WARNING: config.vm.provider :vmare_workstation do |vmware|
>> WARNING:   vmware.vmx["ethernet0.pcislotnumber"] = "33"
>> WARNING: end
>> WARNING:   end
>> WARNING: 
>> WARNING: For more information: https://
>> www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
>> ==> default: Fixed port collision for 22 => . Now on port 2200.
>> ==> default: Starting the VMware VM...
>> ==> default: Waiting for the VM to receive an address...
>> ==> default: Forwarding ports...
>> default: -- 22 => 2200
>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>
>> Stuck here waiting until I open VMware Workstation GUI console. The 
>> following is the output after opening the GUI.
>>
>> default: SSH address: 127.0.0.1:2200
>> default: SSH username: vagrant
>> default: SSH auth method: private key
>> ==> default: Machine booted and ready!
>> ==> default: Configuring network adapters within the VM...
>> ==> default: Waiting for HGFS to become available...
>> ==> default: Enabling and configuring shared folders...
>> default: -- /home/user/code: /vagrant
>> default: -- /home/user/Downloads: /vagrant_data
>> ==> default: Machine already provisioned. Run `vagrant provision` or use 
>> the `--provision`
>> ==> default: flag to force provisioning. Provisioners marked to run 
>> always will still run.
>>
>>
>>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/4711b24a-46eb-4245-b4d6-f118efadd7f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

2018-01-30 Thread Alvaro Miranda Aguilera

hello

22 in the guest gets map to  on the host

the port 22 is ssh protocol so you can connect to the port  using a ssh
protocol client

a web browser is not an ssh client

you can use the web browser to talk to a web server

ssh is not the same as https

Alvaro.

On Tue, Jan 30, 2018 at 12:20 PM, Mohamed Hamed 
wrote:

> Dear Srs,
>
> I have to install vagrant in centos 7.
>
> See attached image.
>
> When access http://127.0.0.1:/
>
> Return this message ...
>
> *SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
> Protocol mismatch.*
>
>
> How to fix this problem?
>
>
> Best Regards,
>
>
>
> On Mon, Jan 29, 2018 at 8:04 PM, Alvaro Miranda Aguilera <
> kiki...@gmail.com> wrote:
>
>> you just reply to a 2015 email, i doubt the issue is near close
>>
>> can you send a new email and describe
>>
>> what you want to do
>> what is not working
>> what files are you using
>> what errors you get what do you see
>>
>> etc, any information that can help to understand
>>
>>
>> Thanks
>>
>>
>> On Mon, Jan 29, 2018 at 1:34 PM, Mohamed Hamed <
>> moham...@motahidagroup.com> wrote:
>>
>>> Dear Alvaro
>>>
>>> i have to install openio on vagrant so i have the same problem can you
>>> help me to solve this problem ..
>>>
>>> i don't know what is your meaning  can i Share your Vagrantfile 
>>>
>>>
>>> On Friday, September 18, 2015 at 6:07:25 AM UTC+2, Alvaro Miranda
>>> Aguilera wrote:

 Hello

 That happen when you use the wrong port in the browser.

  usually is for SSH, so you can use ssh localhost 

 you need to create a port forward for http or https and use that
 http/https port with the browser.

 Share your Vagrantfile and I can tell you if you are missing that or
 not.

 Thanks
 Alvaro.

 On Tue, Sep 15, 2015 at 10:10 PM, Gin Lance 
 wrote:
 > have you solved this problem?
 >
 > On Thursday, January 15, 2015 at 9:38:17 AM UTC+8, Marcelo Amorim
 wrote:
 >>
 >> Dear Srs,
 >>
 >> I install vagrant in Windows 8.
 >>
 >> See attached image.
 >>
 >> When access http://127.0.0.1:/
 >>
 >> Return this message ...
 >>
 >> SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
 >> Protocol mismatch.
 >>
 >>
 >> How to fix this problem?
 >>
 >>
 >> Best Regards,
 >>
 >>
 >> Marcelo Amorim
 >
 > --
 > This mailing list is governed under the HashiCorp Community
 Guidelines -
 > https://www.hashicorp.com/community-guidelines.html. Behavior in
 violation
 > of those guidelines may result in your removal from this mailing
 list.
 >
 > GitHub Issues: https://github.com/mitchellh/vagrant/issues
 > IRC: #vagrant on Freenode
 > ---
 > You received this message because you are subscribed to the Google
 Groups
 > "Vagrant" group.
 > To unsubscribe from this group and stop receiving emails from it,
 send an
 > email to vagrant-up+...@googlegroups.com.
 > To view this discussion on the web visit
 > https://groups.google.com/d/msgid/vagrant-up/52fc8b7a-aa7e-4
 4e1-ad8b-e5432ec719c1%40googlegroups.com.
 > For more options, visit https://groups.google.com/d/optout.

>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Vagrant" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to vagrant-up+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/edeb7c18-7ceb-43db-8f16-13c780296416%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Vagrant" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/vagrant-up/qLaQcbsVNrs/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

2018-01-30 Thread Mohamed Hamed

Dear Srs,

I have to install vagrant in centos 7.

See attached image.

When access http://127.0.0.1:/

Return this message ...

*SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
Protocol mismatch.*


How to fix this problem?


Best Regards,



On Mon, Jan 29, 2018 at 8:04 PM, Alvaro Miranda Aguilera 
wrote:

> you just reply to a 2015 email, i doubt the issue is near close
>
> can you send a new email and describe
>
> what you want to do
> what is not working
> what files are you using
> what errors you get what do you see
>
> etc, any information that can help to understand
>
>
> Thanks
>
>
> On Mon, Jan 29, 2018 at 1:34 PM, Mohamed Hamed  > wrote:
>
>> Dear Alvaro
>>
>> i have to install openio on vagrant so i have the same problem can you
>> help me to solve this problem ..
>>
>> i don't know what is your meaning  can i Share your Vagrantfile 
>>
>>
>> On Friday, September 18, 2015 at 6:07:25 AM UTC+2, Alvaro Miranda
>> Aguilera wrote:
>>>
>>> Hello
>>>
>>> That happen when you use the wrong port in the browser.
>>>
>>>  usually is for SSH, so you can use ssh localhost 
>>>
>>> you need to create a port forward for http or https and use that
>>> http/https port with the browser.
>>>
>>> Share your Vagrantfile and I can tell you if you are missing that or
>>> not.
>>>
>>> Thanks
>>> Alvaro.
>>>
>>> On Tue, Sep 15, 2015 at 10:10 PM, Gin Lance 
>>> wrote:
>>> > have you solved this problem?
>>> >
>>> > On Thursday, January 15, 2015 at 9:38:17 AM UTC+8, Marcelo Amorim
>>> wrote:
>>> >>
>>> >> Dear Srs,
>>> >>
>>> >> I install vagrant in Windows 8.
>>> >>
>>> >> See attached image.
>>> >>
>>> >> When access http://127.0.0.1:/
>>> >>
>>> >> Return this message ...
>>> >>
>>> >> SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
>>> >> Protocol mismatch.
>>> >>
>>> >>
>>> >> How to fix this problem?
>>> >>
>>> >>
>>> >> Best Regards,
>>> >>
>>> >>
>>> >> Marcelo Amorim
>>> >
>>> > --
>>> > This mailing list is governed under the HashiCorp Community Guidelines
>>> -
>>> > https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation
>>> > of those guidelines may result in your removal from this mailing list.
>>> >
>>> > GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> > IRC: #vagrant on Freenode
>>> > ---
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "Vagrant" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> > email to vagrant-up+...@googlegroups.com.
>>> > To view this discussion on the web visit
>>> > https://groups.google.com/d/msgid/vagrant-up/52fc8b7a-aa7e-4
>>> 4e1-ad8b-e5432ec719c1%40googlegroups.com.
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/edeb7c18-7ceb-43db-8f16-13c780296416%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/vagrant-up/qLaQcbsVNrs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CAHqq0ez%2B0tk0uQ3K4H3CKLQ7sEYoYZVyxv4E
> JkQ6EszT5%3D%3DHpg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Best Wishes

Mohamed Hamed

Al-Motahida Education Group

-- 
This mailing list is governed under the HashiCorp Community Guidelines -

Re: [vagrant-up] Extending a drive size using the vagrant vmware provider?

2018-01-30 Thread Alvaro Miranda Aguilera

better create a new VM thats fit for what you need.

Alvaro.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyb8kzjqr3G%2BszZXeuVsejSYdDi908Yp4q2ByXq-r8TyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Configuration of the /etc/network/interfaces and /etc/dhcp/dhcpd.conf by Vagrantfile?

Re: [vagrant-up] Laravel cannot make secure connection to server by domain name. Localhost:8000 works

[vagrant-up] Multi-machine Vagrantfile driving me loopy (!)

[vagrant-up] Laravel cannot make secure connection to server by domain name. Localhost:8000 works

Re: [vagrant-up] Extending a drive size using the vagrant vmware provider?

Re: [vagrant-up] Digest for vagrant-up@googlegroups.com - 7 updates in 4 topics

[vagrant-up] Re: vagrant up stuck waiting for machine to boot unless VMware Workstation GUI console is open

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

Re: [vagrant-up] Extending a drive size using the vagrant vmware provider?

10 matches

Site Navigation

Mail list logo

Footer information