Port 8082 not available - port

I installed a Jenkins server on port 8080.
Then I installed GitBlit, which usually takes port 8080 too, so that I changed to port 8082.
On the machine I can call localhost:8082, but from remote 192.168.178.3:8082 is not available.
Jenkins response works on 192.168.178.3:8080
I opened the port on the hardware firewall. Still no response.
The last thing I could image is the Windows firewall, but even after opening the port for TCP for in and out its not working?
Or where do you think the problem is?

If you are using Gitblit GO, the default config for Gitblit GO will bind to localhost and will be unreachable from another machine. Check out server.httpBindInterface and server.httpsBindInterface.

Perhaps you need to do any port forwarding on your hardware firewall?
If you suspect Windows, you can add your program/service to the exception list in you Win Firewall settings. You can make this by going to:
START->Control Panel->Windows Firewall->Windows Firewall with Advanced Security
and modify Inbound and Outbound rules.

Related

Cannot connect to Jenkins

I installed Jenkins on my windows server and it works when accessing it from localhost:8080.
When I try to access it from outside the server like serveripaddress:8080 it's not accessible.
There is a inbound rule in firewall to named Jenkins for port 8080 for java.
running netstat:
Any idea what can I do in order to be able to access it from outside the server?
Browsing to localhost:8080/manage there is an alert:
It appears that your reverse proxy set up is broken.
It's a bit unclear in your question whether you had set up a firewall rule on your local computer or the server.
Make sure you have opened inbound port 8080 on TCP on your servers firewall.
To make sure the firewall is not the issue, you could test by turning off the firewall completley, assuming the server is not exposed to the web.

How can I access my local development server over the internet?

I have Wamp 3.1.7 running on a Windows 10 machine. The goal is to have the projects on this server accessible via the internet.
The server is available and working as expected over LAN when accessed with the LAN IP, e.g.
http://10.0.0.3/.
The server runs behind my router, which has its web interface running on port 80, so when I access my public IP, traffic on port 80 goes to the router login page.
Steps taken to try and solve the issue:
change the port my server is listening to from 80 to 8080. (this is working, both locally and over LAN, accessed with http://10.0.0.3:8080)
Add inbound rules on windows firewall for port 8080, set to allow all.
Add port forwarding on the router settings (forward incoming traffic on port 8080 to local IP 10.0.0.3:8080 as per https://portforward.com/d-link/dsl-g2562dg/)
Using PFPortChecker, it says that port 8080 on public_ip is open and able to send data.
I remain unable to access my server. When I go to public_ip:8080, I get ERR_CONNECTION_TIMED_OUT.
As stated above, going to public_ip just displays the router login page.
So as far as I can tell: port 8080 is open, my server is accessible over LAN on port 8080.
What am I missing? Where else could my traffic be blocked?
Stupid mistake on my side.
Answer found here: Public IP Web Page "Connection Timed Out" When Connected To
The issue was that you cannot access the server with the public_ip if connected the LAN the server is running on.

Install Jenkins on windows server and access it using VM's external ip [google-compute-engine]

I have created a VM instance with windows OS (windows-server-2019-dc-v20200211) in Google cloud.Established RDP connection and installed Jenkins on the VM, but how can I access it from other networks using the VM's external ip?
Could someone help me on this!!
Note: I want to install Jenkins in windows server and not on Linux.
I'll suggest you should check the following:
First, make sure your local firewall on windows server is enabled and allows connections on port 8080. Secondly, Network ACL for both incoming traffic on TCP 8080 and outcoming traffic on TCP port 8080 should be allowed.
Also check some of these stackoverflow use cases for more help: [1]https://superuser.com/questions/1212645/cannot-expose-jenkins-externally [2]https://apple.stackexchange.com/questions/31376/how-can-i-open-port-8080-of-mac-os-x-lion [3] Jenkins server is not accessible by host name (ip address)

Can't access jenkins remotely

I installed jenkins on my remote server.
If I do at the server:
wget http://server.url:8080
I get the page without any problem. At my computer, I get that:
--2014-01-09 14:11:33-- http://server.url:8080/
Resolving server.url (server.url)... 54.205.148.55
Connecting to server.url (server.url)|54.205.148.55|:8080... faied: Connection timed out.
Retrying.
I already tried changing --httpListenAddress= parameter at config file (I set it to 0.0.0.0) and nothing happens. It's installed on an Ubuntu 12.04 and it has Apache running on port 80.
Any idea?
Thanks!
EDIT: I also tried with no result disabling iptables and ufw.
Can you check the bind IP address of Jenkins, if you want to access your Jenkins from outside it should be 0.0.0.0:8080 or YOUR_SERVER_IP:8080
Check using the command: netstat -tunlp
Stop the firewall: systemctl stop ufw
From your output it looks like you are trying to connect on port 8080, but you said that you have apache listening on port 80.
If the port mismatch is not the issue it is probably another firewall blocking your traffic.
Can you run a telnet from your computer to the Jenkins server and see if you can connect?
telnet 54.205.148.55 8080
or
telnet 54.205.148.55 80
Depending on which port you are actually listening on.

Cloudera CDH3 Remote Connection

I have the out of the box Cloudera CDH3 installed on a CentOS 6.2. I am able to connect to the Cloudera Mananger (port 7180) or Hue (port 8088) locally, but not able to connect remotely. Is this the OS locking down the port? Thank you for the help.
I've never used Cloudera Manager, however have used Hue; what IP are you listening on?
If you have it configured for localhost or 127.0.0.1, then you wont be able to make the connection externally. To fix this, you need to make it listen on whatever your external IP is.
ie /sbin/ifconfig eth0 (Or wlan0, eth1, etc).
Hope that helps.

Resources