Setting up Lab Environment for Lab 2.1

lobsab

I have Virtual Box and Vagrant installed on my Windows PC with the PowerShell 7.4 version also installed. So, spinning up the machine with "vagrant up", I can't access the Jenkins GUI after the initial setup I did last week.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'lab-env.box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: lfs267-lab-resources_default_1718060238517_13555
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Connection aborted. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases, it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine matches the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 6.1.14 r140239
default: VirtualBox Version: 7.0

****Accessing the Jenkins GUI on the browser via http://localhost:5000/
Here's the error in all my PC browsers (Opera, MS. Edge, and Chrome)****

This site can’t be reached
The connection was reset.

Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_RESET

luisviveropena

Hi @lobsab,

1.- Is there any firewall blocking port 5000?

2.- Can you check if any other application is using port 5000? Not sure if "ss" is available on Windows, but "netstat" should be.

3.- If port 5000 is not in use, you can try destroying the vm and starting it again.

Regards,
Luis.