I have installed nexus sonatype from below url. http://bneijt.nl/blog/post/nexus-on-ubuntu-12.10-installation/ in my EC2 instamce . I have SVN, Jenkins, nexus in the same instance. Apache is running on port 80. Jenkins is running on 8080. I have configured nexus to 9999 port from nexus.properties files. Nexus is running but I am not able to access the dashboard from browser..
I forgot to add the port no in aws security group.
Related
I've installed spinnaker in kubernetes cluster, halyard is running in ubuntu machine.
To access spinnaker UI from my laptop as localhost:9000, I ran hal deploy connect on ubuntu and created ssh tunnel in putty for ports 9000, 8084, 8087 which is in my laptop to ubuntu system where halyard is running.
hal deploy connect
+ Get current deployment
Success
+ Connect to Spinnaker deployment.
Success
Forwarding from 127.0.0.1:8084 -> 8084
Forwarding from [::1]:8084 -> 8084
Forwarding from 127.0.0.1:9000 -> 9000
Forwarding from [::1]:9000 -> 9000
But spinnaker is not connecting, and ssh even logs says - connection is refused...
however 've tried to running other application directly on ubuntu, created ssh tunnel for that and through localhost:portNumber in my laptop is working fine..
please advise.. thanks..
Please take a look on: helm-chart, spinnaker-deployment.
Temporary workaround (until this is fixed) you can add:
spec:
...
- --runtime-config=apps/v1beta1=true,apps/v1beta2=true,extensions/v1beta1/daemonsets=true,extensions/v1beta1/deployments=true,extensions/v1beta1/replicasets=true,extensions/v1beta1/networkpolicies=true,extensions/v1beta1/podsecuritypolicies=true
... to /etc/kubernetes/manifests/kube-apiserver.yaml
At the end restart kubelet.
Make sure you followed every steps from this tutorial.
I'm facing a problem trying to install ssl on my amazon ec2 instance running tomcat 7.
Everything is up and running at port 8080 but when I try to reach through port 443 i get cannot reach site error.
My setup is as follows:
Domain from GoDaddy, configured to redirect to my amazon ec2 instance public ip (also dns management transferred to aws).
Amazon ec2 (linux) - security groups enabled port 8080 + 22 + 443
Tomcat 7 - running dynamic web application.
I followed this tutorial by amazon:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-amazon-linux-2.html
but did not work for me.
I'll be glad if anyone have experience in that field and can help me solve this issue, any further information will be delivered upon request.
Any help is much appreciated.
Best regards,
Oran.
I have a problem with my registry docker. My "server" VM is on kali-linux. I created the registry docker in HTTP and use a centOS VM as a client. I declared the registry insecure in the client VM and it worked perfectly.
Now I try to put it in HTTPS. In order to do that, I use nginx as a proxy. I followed this tutorial : Step 5 — Setting Up SSL except for Part 8 to make it a service (I don't know why but i can't do it).
Because I don't have a domain name, I used a fake one. In order to be recognized, I added my IP (192.168.X.X) and the domain name I used (myregistryexemple) to the /etc/hosts file on both VM.
As asked by the tutorial, I generated the certificat on my "server" VM (the kali one), and send it by scp to my client VM. I make the centOS vm trust the certificate thanks to this commands :
yum install ca-certificates
update-ca-trust force-enable
cp cert.crt /etc/pki/ca-trust/source/anchors/
update-ca-trust extract
I restart the service docker on the client VM. And launch the docker registry and the nginx proxy with "docker-compose up" on my kali VM.
I tag and try to push an ubuntu on the registry :
docker tag ubuntu myregistryexemple/ubuntu
docker push myregistryexemple/ubuntu
But I get this error :
The push refers to a repository [docker.io/myregistryexemple/ubuntu]
56827159aa8b: Preparing
440e02c3dcde: Preparing
29660d0e5bb2: Preparing
85782553e37a: Preparing
745f5be9952c: Preparing
denied: requested access to the resource is denied
Then I try to push to localhost directly :
docker tag ubuntu localhost:5000/ubuntu & docker push localhost:5000/ubuntu
then I docker login on the domain from the client VM, it worked, but when i tried to pull from my domain registry on the client VM, docker cannot find on the registry the docker images i tried to push.
Do someone has any idea why and knows how to help me ?
Ok so i found a way to make it work.
It is quite simple : Juste follow the complete tutorial I quote on the question ( https://www.digitalocean.com/community/tutorials/how-to-set-up-a-private-docker-registry-on-ubuntu-14-04#step-5-%E2%80%94-setting-up-ssl )
After you created the repository, and before you push/pull a docker image.
You need to go, in both client and server VM, on /etc/hosts .
Add the line : domainChosen serverVmIp
Save and quit it.
Now we need the client to trust the certificate generated. In order to do that, you can use this tutorial : http://kb.kerio.com/product/kerio-connect/server-configuration/ssl-certificates/adding-trusted-root-certificates-to-the-server-1605.html .
Then restart your registry and your docker deamon. And you normaly can use your domain name to push/pull in your registry in https.
I'm using Ansible to spin up a new Amazon EC2 install, and then I install Java and Tomcat (via the yum module). After placing the war for sample project from the Apache website in the webapps directory, I go and run the the command (below), nothing happens. It returns with response, no error. I've checked both the IP and port 8080 and Tomcat is not running.
[centos#sonar-test webapps]$ sudo systemctl start tomcat
[centos#sonar-test webapps]$ sudo systemctl start tomcat
[centos#sonar-test webapps]$
For reference, I was following this tutorial as well:
https://www.digitalocean.com/community/tutorials/how-to-install-apache-tomcat-7-on-centos-7-via-yum
From your comment on my question running curl in your ec2 instance
When I curl I get a large html document with various apache-esque things on it
It means Tomcat is installed and running.
If you don't access it, its because of your security group rules
In your ec2 console, select the Security Groups option. Edit the rules that is associated with your ec2 instance (the one running Tomcat) and permits inbound connections to port 8080 (so you can make request to your Tomcat server) and port 80 if you're running Apache (or nginx/another web server). If you're not sure about security, you can restrict the inbound traffic to come only from your IP so you can test but no-one else can make request.
Tomcat enter localhost: 8080 in webapp directory。Then the weblogic has input localhost: 7001 which directory is in?
I am assuming you want to know where would Weblogic keep the deployed apps.
Weblogic keeps them in $WEBLOGIC_HOME/application directory
$WEBLOGIC_HOME ---> install location of your WebLogic software