The virtual machine works correctly, but when I try to access http://local.cocorico.cc (192.168.50.42), there is no service available. (ERR_CONNECTION_REFUSED).
When I try to log in via ssh, I don't have the credentials.
------------------------ the host file is correct-----------------------------
Copyright (c) 1993-2009 Microsoft Corp.
This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
This file contains the mappings of IP addresses to host names. Each
entry should be kept on an individual line. The IP address should
be placed in the first column followed by the corresponding host name.
The IP address and the host name should be separated by at least one
space.
Additionally, comments (such as these) may be inserted on individual
lines or following the machine name denoted by a '#' symbol.
For example:
102.54.94.97 rhino.acme.com # source server
38.25.63.10 x.acme.com # x client host
localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
192.168.50.42 local.cocorico.cc
::1 localhost
----------------------- the service is running-------------------------------------
C:\Users\Juan\coco4>vagrant up local
WARNING: Vagrant has detected the vagrant-triggers plugin. This plugin conflicts
with the internal triggers implementation. Please uninstall the vagrant-triggers
plugin and run the command again if you wish to use the core trigger feature. To
uninstall the plugin, run the command shown below:
vagrant plugin uninstall vagrant-triggers
Note that the community plugin vagrant-triggers and the core trigger feature
in Vagrant do not have compatible syntax.
To disable this warning, set the environment variable VAGRANT_USE_VAGRANT_TRIGGERS.
Bringing machine 'local' up with 'virtualbox' provider...
==> local: Checking if box 'ubuntu/trusty64' version '20190429.0.1' is up to date...
==> local: Configuring cache buckets...
==> local: Machine already provisioned. Run vagrant provision or use the --provision
==> local: flag to force provisioning. Provisioners marked to run always will still run.
==> local: Machine 'local' has a post vagrant up message. This is a message
==> local: from the creator of the Vagrantfile, and not from Vagrant itself:
==> local:
==> local: Please add this line to your /etc/hosts:
==> local: 192.168.50.42 local.cocorico.cc
* virtual machine is running properly and responding ping
The virtual machine works correctly, but when I try to access http://local.cocorico.cc (192.168.50.42), there is no service available. (ERR_CONNECTION_REFUSED). When I try to log in via ssh, I don't have the credentials.
------------------------ the host file is correct----------------------------- Copyright (c) 1993-2009 Microsoft Corp.
This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
This file contains the mappings of IP addresses to host names. Each entry should be kept on an individual line. The IP address should be placed in the first column followed by the corresponding host name. The IP address and the host name should be separated by at least one space.
Additionally, comments (such as these) may be inserted on individual lines or following the machine name denoted by a '#' symbol.
For example:
localhost name resolution is handled within DNS itself. 127.0.0.1 localhost 192.168.50.42 local.cocorico.cc ::1 localhost
----------------------- the service is running------------------------------------- C:\Users\Juan\coco4>vagrant up local WARNING: Vagrant has detected the
vagrant-triggersplugin. This plugin conflicts with the internal triggers implementation. Please uninstall thevagrant-triggersplugin and run the command again if you wish to use the core trigger feature. To uninstall the plugin, run the command shown below:vagrant plugin uninstall vagrant-triggers
Note that the community plugin
vagrant-triggersand the core trigger feature in Vagrant do not have compatible syntax.To disable this warning, set the environment variable
VAGRANT_USE_VAGRANT_TRIGGERS. Bringing machine 'local' up with 'virtualbox' provider... ==> local: Checking if box 'ubuntu/trusty64' version '20190429.0.1' is up to date... ==> local: Configuring cache buckets... ==> local: Machine already provisioned. Runvagrant provisionor use the--provision==> local: flag to force provisioning. Provisioners marked to run always will still run.==> local: Machine 'local' has a post
vagrant upmessage. This is a message ==> local: from the creator of the Vagrantfile, and not from Vagrant itself: ==> local: ==> local: Please add this line to your /etc/hosts: ==> local: 192.168.50.42 local.cocorico.cc* virtual machine is running properly and responding ping