Problem with training lab
Answered
Hi,
I am following Cloudbees online course named "CloudBees University: Jenkins - Fundamentals" but I meet an issue. Indeed, I want to access to my Jenkins application from my browser. I followed all the steps in "Install Lab Environment", my vagrant is up and running and all my containers are running too.
Unfortunately, I tried to connect to localhost:5000/index.html and the application is not reachable. I looked for any solution on the CloudBees support and on Google but I didn't find any solution.
Anyone has ideas about it please?
Regards,
Julien
-
I found the solution. Indeed, for unknown reason my containers were in state "Unhealthy". I did a docker stop on them then docker start.
I hope this post help someone.
0 -
Hi,
I have the same issue but my containers are healthy, even are only 6 containers and no one on port 5000.
Could you help me with a solution?
Thank you,
Iulian
0 -
Here is the vagrant up log: https://gist.github.com/iulian-lucaci/08fa76dfb98a52eb115ee87a237f3ce4
Thanks,
Iulian
0 -
Hi,
I don't understant why you can't start your Jenkins. Maybe you should stop all the containers and restart them. Unfortunately, any solution is provided in the training document :/
0 -
Hello,
I am facing the same issue.
http://localhost:5000/index.html
This site can’t be reachedThe webpage at http://localhost:5000/index.html might be temporarily down or it may have moved permanently to a new web address.
ERR_SOCKET_NOT_CONNECTED
--------------------------------------------------------------------------------------------
http://www.websocket.org/echo.htmlIt shows message :
This browser supports WebSocket.
----------------------------------------------------------------------
Log:
samsung@DESKTOP-R22DT9L MINGW64 /e/cloudbees-training-jenkins-fundamentals
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> 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: Running 'pre-boot' VM customizations...
==> 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: butler
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: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.samsung@DESKTOP-R22DT9L MINGW64 /e/cloudbees-training-jenkins-fundamentals
$ vagrant status
Current machine states:default running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.samsung@DESKTOP-R22DT9L MINGW64 /e/cloudbees-training-jenkins-fundamentals
Thanks,
Samir SInha
0
Please sign in to leave a comment.
Comments
5 comments