I set up a DigitalOcean server running ubuntu 18.04 and am trying to run Jenkins on it. I followed the instructions to the letter in this tutorial:
https://www.digitalocean.com/community/tutorials/how-to-install-jenkins-on-ubuntu-18-04
which works perfectly until Step 4. When I enter:
http://your_server_ip_or_domain:8080
substituting the DigitalOcean ip for "your_server_ip_or_domain", of course, the browser says "This site cannot be reached". Every step before that worked perfectly. The firewall is open to it.
I also made sure the JRE was installed.
EDIT: I read in another tutorial that Jenkins does not support Java 10 or 11, so I removed Java 11 and installed Java 8, and followed this tutorial:
https://linuxize.com/post/how-to-install-jenkins-on-ubuntu-18-04/
I also installed a web server using the following command:
sudo apt-get install nginx
Same error whether I put the ipaddress in the browser or ipaddress:80 or ipaddress:8080. I can ping the ip from outside the network ok. Any ideas?
I figured it out. Nginx is listening on port 80 so you need to open the firewall to that port as well. Use the following command:
sudo ufw allow 80
Now I can get the default web page for nginx by using ipaddress:80 and jenkins by entering ipaddress:8080
Related
I'm trying to install SearXNG and direct a subdomain to the port that SearXNG uses. Following the instructions has gone smoothly until the following:
When all services are installed and running fine, you can add SearXNG to your HTTP server
As it does not say how I go about this.
All previous instructions were followed successfully up to and including
sudo -H ./utils/searxng.sh install all
and I was expecting lsof to show a service related to searxng running on a port that I could then redirect using caddy however I don't see anything related to caddy using a port and I'm not sure what I need to run, or what port I'm meant to add to my Caddyfile.
I have installed it with command "sudo yum install ngingx" and its visible from computer host using its own ip in the browser, but in other computer in the same LAN and resolving ping it doesnt work and answers a timeout error. I know there is a /etc/nginx/nginx.conf file but I didnt see any valid configuration to resolve this (or I didnt search very well).
Machine has internet and resolves ping to other machines in lan
Could somebody guide me?
I use virtualbox to run Fedora
Thank you, here I left nginx.conf enter image description here
First of all, are you using bridge mode in virtualBox? If so and this is still not working, check if Fedora has enabled the firewall by typing in a shell:
systemctl status firewalld.service
If active, check the zone where the main adapter is configured
firewall-cmd --get-active-zones
Add ports 443 and 80 to the zone related to your interface (for instance FedoraWorkstation)
firewall-cmd --zone=FedoraWorkstation --permanent --add-port=80/tcp
firewall-cmd --zone=FedoraWorkstation --permanent --add-port=443/tcp
This should do the trick
Finally the problem was that apache is installed by default in fedora workstation and main page of nginx was showing apache as current web server, so any changes made in nginx wasnt being loaded. Solution: purge apache from system and reboot. Now nginx load as the main web server and changes made are applied
I have done everything according to manuals from https://jfrog.com/open-source/ :
My Ubuntu version is 20.04. Since there is no "focal" in https://releases.jfrog.io/artifactory/artifactory-debs/, I've added "bionic":
$ cat /etc/apt/sources.list.d/artifactory.list
deb https://releases.jfrog.io/artifactory/artifactory-debs bionic main
Then I've installed jfrog-artifactory-oss version 7.12.6 and tried launching the service.
It has launched, but browser, connected to ports :8081 or :8082 of localhost, shows that 3 services don't start:
So, what does it need?
I came here, because I had the very same problem on docker.
I finally figured out, that inside the docker the environment variables http_proxy, https_proxy, HTTP_PROXY and HTTPS_PROXY where all set to localhost:8080. This caused the problem for me.
So when I start the docker this way, everything works as expected:
docker run --name artifactory-cpp-ce -ehttp_proxy="" -e https_proxy="" -e HTTP_PROXY="" -e HTTPS_PROXY="" -v $JFROG_HOME/artifactory/var/:/var/opt/jfrog/artifactory -d -p 8081:8081 -p 8082:8082 releases-docker.jfrog.io/jfrog/artifactory-cpp-ce:latest
On my machine, I found that libvirtd was running. It wasn't libvirtd, itself, that prevented artifactory from coming up. It was the fact that the virbr0 interface was up. It doesn't seem to be a problem bringing this interface back up after artifactory comes up.
For us this was on a Windows OS which was running McAfee Services. McAfee services listens on port 8081, same as the default Artifactory. Changing McAfee listening port was not an option for us.
I copied the JFROG_HOME\artifactory\var\etc\system.full-template.yaml, changed the name to system.yaml and searched for 8081 and changed it ( uncommented) to a different port. Restarted the Artifactory Service.
I am attempting to run my ASP.NET Core 1.1 web API in a Docker container, but I cannot connect to the web API from a browser or curl. To troubleshoot, I have also brought up standard nginx and Apache httpd containers and cannot connect to these either, so I believe this is a Docker/Docker Toolbox/configuration issue rather than a problem with my application.
I'll focus on what I have done with nginx and Apache:
I am running Docker Toolbox on Windows 7 Professional, and everything seems to work as I would expect.
Docker commands all work as expected
I can access the underlying Windows filesystem
I can get the expected results from curl http://localhost (if I start the default IIS website on Windows 7)
So now I shut down IIS and run nginx in a container:
$ docker run -d -p 80:80 nginx
45bb1f373c11b820d8431de3eb3bf222d57d412de53e8625f461b62c4279e644
Docker now shows nginx running:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
45bb1f373c11 nginx "nginx -g 'daemon off" 47 seconds ago Up 48 seconds 0.0.0.0:80->80/tcp, 443/tcp admiring_pike
But I cannot connect with either curl (within the Docker Toolbox command prompt) or a web browser in Windows:
$ curl http://localhost
curl: (7) Failed to connect to localhost port 80: Connection refused
I get exactly the same results if I run an Apache 2.4 (httpd) container.
Any ideas? Thanks! Peter
I have found the answer in another question here.
Because Docker Toolbox is running on a lightweight Linux VM, it has its own IP address. One needs either to map localhost to the VM using DOCKER_HOST ir access the VM via it's IP address, found using the command:
docker-machine ip default
As you are running on VM, you need to follow this docker document from here.
After that run the following command to check the IP address of your VM.
docker-machine ip default
Start the nginx and hit [ip default address]:port in the browser. It works!
When I run meteor, it just says killed.
Did Digital Ocean install a new firewall or block some ports recently? I'm pretty sure these used to work. ping www.google.com seems to work fine