Unable to access Jenkins - jenkins

When I tried to access jenkins using localhost:8080/jenkins I get the following error.
HTTP ERROR 404
Problem accessing /jenkins/. Reason:
Not Found
How to solve this?

Check your webserver which is running, if you use apache turn on the apache server by going to right path
Check this out, Apache web server to route HTTP and HTTPS traffic to Jenkins. This helps too
1.use URLs that lack the pesky port tag
2.receive external port 80 or 443 traffic

Related

Jenkins Jetty redirect http to https

We set our Jenkins ver. 2.150.1 running on a default Jetty (Ubuntu) with https on port 8443. Is it possible to redirect all access from http(8080) to https(8443) without Apache/Nginx proxy? It would be great to use an existing Jetty.
This is not implemented but it could be possible using SecuredRedirectHandler.
Please note this is development is part of Jenkins project: https://github.com/jenkinsci/winstone/.
You can propose a pull request with the change and I will be happy to review/merge
Or at least log a change request here https://issues.jenkins-ci.org/projects/JENKINS.

Https and http both the protocals not able to run in websphere liberty server with springboot

I want to run the health check of the services only with http and all the services as https. facing the issue to configure the particular URI with in-secure protocal (http). tried below but its not working:
Here I am trying to configure the healthcheck with http and all the services with https :
http.requiresChannel().antMatchers("*/healthcheck").requiresInsecure().anyRequest().requiresSecure();
Please help me to resolve this issue
Thanks in advance.

apache tomcat on Google cloud Instance

I have installed java and apache tomcat on my Google cloud instance and have started the tomcat but when I try to connect to my instance from my browser on port 8080 or 8443 I cannot connect it. I should see the apache tomcat's welcome page right? Can someone plz help me with this?
You need to configure firewall to allow those ports.
The best option for your use case would be to use Google Cloud Launcher.
https://console.cloud.google.com/launcher/details/click-to-deploy-images/tomcat.
It should give you an external IP with HTTP and HTTPS tomcat ports open 8080.
Just go to the details of your instance and click on edit.
Now in the firewalls section and check Allow HTTP traffic.
Screenshot

Configuring SSL to work with IIS and parse server

I have an ssl certificate(Geotrust) installed to IIS 8, listening on port 443 and running on windows server 2012-r2. This works when I access https://myapp.example.com and it shows me the standard IIS page. My problem is that I am trying to connect to the parse-server(nodejs, express) running on serverUrl: http://localhost:1337/parse. So when trying to connect to https://myapp.example.com:1337/parse
chrome says: "myapp.example.com finished the connection unexpectedly" and I cant reach the expected site.
ios-simulator says: kCFStreamErrorDomainSSL, -9806.
The connections to http works as expected on the urls described above.
I have tried to set the SSL port to 1337(and portforward 443->1337 on my router), but then I can not start the parse-server on the same port.
First time doing this, so really gratefull if anyone can point me in the right direction!
Solved by doing an reverse proxy in IIS 8.
I needed two applications in IIS and downloaded them like this: yourSite->right-click middle pane->"install application from gallery" and search & download these:
Download URL Rewrite (i downloaded 3.0)
Application Request Routing
This helped a lot:
http://weblogs.asp.net/owscott/creating-a-reverse-proxy-with-url-rewrite-for-iis

Rails Https redirect to http

I have hosted my website http://www.example.com, and it works fine.
when I try to access it by https://www.example.com, my browser says it is unable to connect?
Is this normal? (Is it a DNS issue or a rails app)
This probably isn't a Rails issue, but it's hard to say without more information. The most likely explanation is that your server probably isn't configured to have port 443 open, which is the default port for https connections.
If you are on Amazon EC2, you'll need to manually open port 443 in the EC2 security group configuration.

Resources