I changed the JENKINS_PORT="-1" (was JENKINS_PORT="8080" by default) in /etc/sysconfig/jenkins
Enabled 8443 by setting JENKINS_HTTPS_PORT="8443"
Restarted Jenkins using Systemctl. Access to Jenkins on 8080 Still working, while 8443 is not.
OS: Centos 7
Java: 8
Jenkins: 2.346.3
Related
I am following along this tutorial to deploy my asp.net application onto Ubuntu. I have installed .Net core 2.0 on my Ubuntu machine using this post. NO issues with that excellent article.
My VM configuration is :
user#instance-2:~/dev/mywebsite$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
I have confirm that .Net core is installed properly.
user#instance-2:~/dev/mywebsite$ dotnet --info
.NET Command Line Tools (2.0.0)
Product Information:
Version: 2.0.0
Commit SHA-1 hash: cdcd1928c9
Runtime Environment:
OS Name: ubuntu
OS Version: 16.04
OS Platform: Linux
RID: ubuntu.16.04-x64
Base Path: /usr/share/dotnet/sdk/2.0.0/
Microsoft .NET Core Shared Framework Host
Version : 2.0.0
Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
Next I have created new dot net web application using below command
dotnet new web
set ASPNETCORE_URLS environment variable
export ASPNETCORE_URLS=http://+:5123
Confirmed that its set properly.
user#instance-2:~/dev/mywebsite$ echo $ASPNETCORE_URLS
http://+:5123
Ran my application using dotnet run. Can see below message on console.
user#instance-2:~/dev/mywebsite$ dotnet run
Hosting environment: Production
Content root path: /home/hemant_shelar/dev/mywebsite
Now listening on: http://[::]:5123
Application started. Press Ctrl+C to shut down.
Expected: I should be able to browse this site from internet using IP address
like : http://35.185.21.120:5123/ But I am not able to access this site from outside. Getting ERR_CONNECTION_TIMED_OUT error.
Note: 35.185.21.120 is IP address of my Ubuntu machine which is in google cloud.
Am I missing any configuration?
UPDATE 1:
I have open port 5123 using below command
sudo ufw enable
sudo ufw allow 5123
Verified that port is opened using below command:
hemant_shelar#instance-2:~/dev/mywebsite$ sudo ufw status
Status: active
To Action From
-- ------ ----
5123 ALLOW Anywhere
5123 (v6) ALLOW Anywhere (v6)
But still same issue.
UPDATE 2
I set environment variable ASPNETCORE_URLS to http://+:80
hemant_shelar#instance-2:~/dev/mywebsite$ echo $ASPNETCORE_URLS
http://+:80
hemant_shelar#instance-2:~/dev/mywebsite$ sudo dotnet run
Hosting environment: Production
Content root path: /home/hemant_shelar/dev/mywebsite
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.
But when I run website its listing on port 5000. Is there any other way to expose site on port 80? e.g. in IIS we use http host header to open multiple sites on port 80.
I'm currently in the process of trying to get Gitlab omnibus installed on my private Debian server, and it works perfectly on port 80, the problem is I also have an Apache server listening on port 80. So I'm trying to get Nginx listening on port 8080 but for some reason I'm getting a
"502
Gitlab is not responding" Error
I have edited both "external_url" in gitlab.rb and also the port number under the server block in the nginx.conf file. and no joy.
If someone could help me that would be great!
Most likely you have another service listening on 8080, I think the omnibus install have some service hooking 8080 - just use 8081 instead.
Edit: I just did a quick search and found that it's the unicorn server that is listening to 8080 with the original omnibus installer.
Note: You will only need to change the external_url in gitlab.rb, no other config file should have to be edited for this.
Edit#2: As #emeraldjava stated there is an option in the configuration file for using another unicorn port: #unicorn['port'] = '8080'
I solved this for Gitlab Omnibus (Community Edition, version 10.1.4) by first setting these in /etc/gitlab/gitlab.rb:
unicorn['port'] = 8081
gitlab_workhorse['auth_backend'] = "http://localhost:8081"
Then running:
sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart
Additionally, if you are running GitLab behind an SSL reverse proxy, you may need to restart that service to get past the cached 502 error page.
Starting with GitLab 13.0, Puma is the default web server and Unicorn has been disabled by default(reference).
so you have to change following configs in /etc/gitlab/gitlab.rb :
external_url 'http://hostOrDomain:8080/'
puma['port'] = 8081
gitlab_workhorse['auth_backend'] = "http://localhost:8081"
I tried to change the server.xml in the Tomcat7 from port=8080 to 8088.
When i start the server using ./startup.sh and then when i hit the URL http://:8088/
i get an error No Route to Host.
JBoss is already running on 8080 , so i want to run tomcat in a different port.
I have WebStorm7 installed on a Windows7 machine.
If I run a meteor project in the Windows7 machine with:
>set NODE_OPTIONS=--debug=47977 & meteor
it prints:
=> Meteor server running on: http://localhost:3000/
=> debugger listening on port 47977
and I can debug with WebStorm7 using the_Node.js Remote debug_ configuration, with Host: 127.0.0.1 and Port: 47977.
If I run a meteor project in a Ubuntu machine (within a Oracle VM VirtualBox, with address 192.168.1.9) with:
$ NODE_OPTIONS="--debug=47977" meteor
it prints only:
=> Meteor server running on: http://localhost:3000/
and I cannot debug with WebStorm from the Windows7 machine using the Node.js Remote debug configuration, with Host: 192.168.1.9 and Port: 47977.
From the ubuntu machine a telnet 127.0.0.1 47977 does not work too. It looks like the debugger is not started at all. What am I doing wrong?
the issue might be related to the fact that node.js debugging is only listening on localhost, so you can't connect to the used port from remote host. The workaround is to use a proxy (see http://delog.wordpress.com/2011/04/08/a-simple-tcp-proxy-in-node-js/, for example)
This proxy can be used as follows:
$: node tcpproxy.js 8585 127.0.0.1 5858
8585 here is the 'exposed' port that webstorm will connect to (you can make this what you wish). You are directing traffic that is coming in on 8585 to 5858 (the local debugging port). Ensure 8585 is open on your firewall if you have one. You have to specify this 'exposed' port in your Remote Debug run configuration as a debug port
I have installed Authbind to run Tomcat on port 80 in Ubuntu.
I have followed http://netthink.com/?p=362 to run Tomcat in Ubuntu in port 80.
When I run Tomcat on the command line by typing ./start.sh, Tomcat starts normally on port 80 without any exception.
In order to run Tomcat from Eclipse I installed the Tomcat plugin from http://www.eclipsetotale.com/tomcatPlugin.html. Everything is fine except that when I want to start Tomcat from Eclipse. When I run Tomcat from Eclipse by the Tomcat plugin, I get the following exception:
java.net.BindException: Permission denied :80
And if I add Tomcat as a server in "Server view" in Eclipse and want to start it from Server view I get this exception:
Port 80 required by Tomcat v6.0 Server at localhost is already in use
But I am sure that there is not any process that acquires port 80, because in the same time when I run Tomcat on the command line by typing ./start.sh, Tomcat starts normally on port 80.
How do I run Tomcat from Eclipse on port 80?
Using another port other than 80 and less than 1024 for Tomcat and start it in Server View in Eclipse gave me the same exception. For example, for port 82:
Port 82 required by Tomcat v6.0 Server at localhost is already in use
You said :
But i am sure that there is not any process that acquires port
80,because in the same time when i run Tomcat in command line by
typing ./start.sh ,tomcat starts normally in port 80.
Did you stop Tomcat in command line before starting it with Eclipse ?
To make sure your Tomcat is stopped, type this :
ps -ef|grep tomcat
You should have something like this if Tomcat is stopped :
user 16428 16373 0 13:56 pts/1 00:00:00 grep --color=auto tomcat
try running eclipse as root and then start tomcat (on port 80).. should work. although not an optimal solution. But should work since 80 is a privileged port in linux and requires sudo permissions to run.
You should start eclipse with: authbind --deep eclipse Since eclipse doesn't start tomcat via startup.sh file, inserting authbind there will have no effect.