Home / user-60251

Antarr Byrd's questions

Martin Hope
Antarr Byrd
Asked: 2021-05-10 21:29:23 +0800 CST
  • 0

I'm trying to connect to a database via SSH from my docker container. I'm getting an error

could not connect to server: Connection refused
    Is the server running on host "0.0.0.0" and accepting
    TCP/IP connections on port 5433?

I have a script to open the port and it works fine on my development, OSX Catalina.

bin/tunnel.sh

#!/usr/bin/expect -f
spawn ssh -fNg -L 5432:0.0.0.0:5432 myserver
expect "connecting"
send "yes"
expect "assword:"
send "mypassword\r"
interact

ENTRYPOINT

set -e

if [ -f tmp/pids/server.pid ]; then
  rm tmp/pids/server.pid
fi

service cron restart
./bin/tunnel.sh
foreman start -f Procfile.production web

database.yml

production: &production
  <<: *default
  # sslmode: "require"
  host: 0.0.0.0
  # pool: 100
linux ruby-on-rails ssh-tunnel docker debian-buster
Martin Hope
Antarr Byrd
Asked: 2017-03-19 23:27:06 +0800 CST
  • -1

I'm trying to use port 80 on caddy but I'm getting an error saying the port is already in use. listen tcp :80: bind: address already in use. When I check to see what is using it this is what I get. 

sonar@SonarQube:~$ netstat -an | grep ":80"
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN     
tcp        0      0 10.1.1.5:42214          168.63.129.16:80        TIME_WAIT  
tcp        0      0 10.1.1.5:42222          168.63.129.16:80        TIME_WAIT  
tcp6       0      0 :::80                   :::*                    LISTEN

How can I kill whatever is running on 80? Could running sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/caddy cause it? If so how do I undo it ?

update (after adding -p)

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      -               
tcp        0      0 10.1.1.5:42768          168.63.129.16:80        TIME_WAIT   -               
tcp        0      0 10.1.1.5:42760          168.63.129.16:80        TIME_WAIT   -               
tcp6       0      0 :::80                   :::*                    LISTEN      -

update 2

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1316/nginx -g daemo
tcp        0      0 10.1.1.5:39152          91.189.95.83:80         TIME_WAIT   -               
tcp        0      0 10.1.1.5:49340          168.63.129.16:80        TIME_WAIT   -               
tcp        0      0 10.1.1.5:46654          91.189.88.161:80        TIME_WAIT   -               
tcp        0      0 10.1.1.5:48740          91.189.88.162:80        TIME_WAIT   -               
tcp        0      0 10.1.1.5:49314          52.176.58.79:80         TIME_WAIT   -               
tcp        0      0 10.1.1.5:49284          168.63.129.16:80        TIME_WAIT   -               
tcp6       0      0 :::80                   :::*                    LISTEN      1316/nginx -g daemo
linux
Martin Hope
Antarr Byrd
Asked: 2017-03-19 23:25:55 +0800 CST
  • 0

I'm trying to visit a SonarQube installation I have installed behind the Caddy web server. When I visit the site I don't get a response. I've tried proxying 8999(secure) and 9000(unsecure) with Caddy.

Caddyfile

https://52.176.62.43 {
  tls self_signed
  gzip
  proxy / 127.0.0.1:8999  
}

http://52.176.62.43 {
  tls off
  gzip
  proxy / 127.0.0.1:9000
}

sonar.properties

# Binding IP address. For servers with more than one IP address, this property specifies which
# address will be used for listening on the specified ports.
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=127.0.0.1

# Web context. When set, it must start with forward slash (for example /sonarqube).
# The default value is root context (empty value).
#sonar.web.context=
# TCP port for incoming HTTP connections. Default value is 9000.
#sonar.web.port=9000
sonar.web.https.port=8999

curl

curl -I https://52.176.62.43/
curl: (7) Failed to connect to 52.176.62.43 port 443: Operation timed out
linux
Martin Hope
Antarr Byrd
Asked: 2016-02-10 09:01:26 +0800 CST
  • 1

I'm trying to configure monit on my server using chef solo. When I visit port 2812 response saying this webpage is not availble.

config/chef/files/default/monitrc

set daemon 30
set pidfile /var/run/monit_real.pid
set logfile syslog facility log_daemon
set idfile /var/monit/id
set statefile /var/monit/state
set eventqueue
    basedir /var/monit/events
    slots 100
set httpd port 2812
    allow admin:"secret"
include /etc/monit/conf.d/*

monit recipe

package 'monit' do
  action :install
end

service "monit" do
  supports :status => true, :restart => true, :start => true,:stop => true
  action [ :enable, :start ]
end

directory '/etc/monit' do
  owner 'deploy'
  group 'deploy'
  mode '0755'
  recursive true
  action :create
  notifies :restart, resources(:service => "monit"), :immediate
end

cookbook_file '/etc/monit/monitrc' do
  source 'monitrc'
  owner 'deploy'
  group 'deploy'
  mode '0755'
  action :create
end

cookbook_file '/etc/monit/conf.d/puma.conf' do
  source 'monit-puma'
  owner 'deploy'
  group 'deploy'
  mode '0755'
  action :create
end

cookbook_file '/etc/monit/conf.d/nginx.conf' do
  source 'monit-nginx'
  owner 'deploy'
  group 'deploy'
  mode '0755'
  action :create
end

execute 'sudo monit reload'
execute 'sudo monit start all'
monitoring