Error starting TCP server on port 443 #36

ghost · 2014-11-29T16:10:03Z

hey i get this error on most networks " Error starting TCP server on port 443. Check that you have the necessary permissions (i.e. root), no other servers are running and the correct network interface is set in Responder.conf. " and sometimes its a different port. can someone help?

digininja · 2014-11-29T16:49:37Z

Do you have permissions, are you running as root?

Is anything else listening on that port? Use netstat -antp to see.
On 29 Nov 2014 16:10, "Zaxscdvf" [email protected] wrote:

hey i get this error on most networks " Error starting TCP server on port
443. Check that you have the necessary permissions (i.e. root), no other
servers are running and the correct network interface is set in
Responder.conf. " and sometimes its a different port. can someone help?

—
Reply to this email directly or view it on GitHub
#36.

ghost · 2014-11-29T16:59:22Z

i am root and i used the command

netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:3141 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:1433 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3594/python
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 2727/stunnel4
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3594/python
tcp 0 0 192.168.1.9:54543 24.244.53.16:80 ESTABLISHED 3311/gnome-panel
tcp 0 1 192.168.69.143:34512 24.244.53.16:80 FIN_WAIT1

digininja · 2014-11-29T17:01:32Z

I can see stunnel listening on port 443 so that will stop responder
starting a listener on it.
On 29 Nov 2014 16:59, "Zaxscdvf" [email protected] wrote:

i am root and i used the command

netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:3141 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:1433 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3594/python

tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 2727/stunnel4

tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3594/python

tcp 0 0 192.168.1.9:54543 24.244.53.16:80 ESTABLISHED 3311/gnome-panel
tcp 0 1 192.168.69.143:34512 24.244.53.16:80 FIN_WAIT1

—
Reply to this email directly or view it on GitHub
#36 (comment).

ghost · 2014-11-29T17:04:20Z

how do i stop the stunnel from listening on port 443?

digininja · 2014-11-29T17:04:53Z

Shut it down
On 29 Nov 2014 17:04, "Zaxscdvf" [email protected] wrote:

how do i stop the stunnel from listening on port 443?

—
Reply to this email directly or view it on GitHub
#36 (comment).

ghost · 2014-11-29T17:06:57Z

ya what command

ghost · 2014-11-29T17:07:11Z

i dont know shit by the way.

digininja · 2014-11-29T17:08:04Z

Quick and dirty

kill -9 2727
On 29 Nov 2014 17:07, "Zaxscdvf" [email protected] wrote:

ya what command

—
Reply to this email directly or view it on GitHub
#36 (comment).

ghost · 2014-11-29T17:08:54Z

k thanks

ghost · 2014-11-29T17:11:16Z

ah shit didnt work ran the netstat again, so do i have to kill all those then?

Active Internet connections Proto Recv-Q Send-Q Local Address tcp 0 0 0.0.0.0:389 tcp 0 0 0.0.0.0:3141 tcp 0 0 0.0.0.0:587 tcp 0 0 0.0.0.0:139 tcp 0 0 0.0.0.0:110 tcp 0 0 0.0.0.0:143 tcp 0 0 0.0.0.0:80 tcp 0 0 0.0.0.0:21 tcp 0 0 0.0.0.0:53 tcp 0 0 0.0.0.0:88 tcp 0 0 0.0.0.0:25 tcp 0 0 0.0.0.0:1433 tcp 0 0 0.0.0.0:445 tcp 0 0 192.168.1.9:39855 tcp 0 0 192.168.1.9:44582 tcp 0 0 192.168.1.9:41803 tcp 0 0 192.168.1.9:60129 tcp 0 0 192.168.1.9:45896 tcp 0 0 192.168.1.9:47292 tcp 0 0 192.168.1.9:37807 tcp 1 0 192.168.1.9:54543 tcp 0 0 192.168.1.9:59548 tcp 0 0 192.168.1.9:45869 tcp 0 0 192.168.1.9:60254 tcp 0 0 192.168.1.9:53289 tcp 0 0 192.168.1.9:51133 (servers and established)
Foreign Address State PID/Program name
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
0.0.0.0:* LISTEN 3892/python
74.125.25.147:443 ESTABLISHED 3676/iceweasel
216.58.216.163:443 ESTABLISHED 3676/iceweasel
192.30.252.88:443 ESTABLISHED 3676/iceweasel
199.59.150.11:443 ESTABLISHED 3676/iceweasel
216.58.216.161:443 ESTABLISHED 3676/iceweasel
192.30.252.128:443 TIME_WAIT -
74.125.25.94:80 ESTABLISHED 3676/iceweasel
24.244.53.16:80 CLOSE_WAIT 3311/gnome-panel
74.125.25.84:443 ESTABLISHED 3676/iceweasel
54.236.195.137:443 TIME_WAIT -
74.125.25.94:443 ESTABLISHED 3676/iceweasel
216.58.216.160:443 ESTABLISHED 3676/iceweasel
216.58.216.160:80 ESTABLISHED 3676/iceweasel

digininja · 2014-11-29T17:17:23Z

The fourth column says what port is being listened on, the number/name at
end is what is listening and it's process ID. With that you can see what is
listening on that port and kill if you want to
On 29 Nov 2014 17:11, "Zaxscdvf" [email protected] wrote:

ah shit didnt work ran the netstat so do i have to kill all those then?

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:3141 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:1433 0.0.0.0:* LISTEN 3892/python

tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3892/python

tcp 0 0 192.168.1.9:39855 74.125.25.147:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:44582 216.58.216.163:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:41803 192.30.252.88:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:60129 199.59.150.11:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:45896 216.58.216.161:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:47292 192.30.252.128:443 TIME_WAIT -

tcp 0 0 192.168.1.9:37807 74.125.25.94:80 ESTABLISHED 3676/iceweasel

tcp 1 0 192.168.1.9:54543 24.244.53.16:80 CLOSE_WAIT 3311/gnome-panel
tcp 0 0 192.168.1.9:59548 74.125.25.84:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:45869 54.236.195.137:443 TIME_WAIT -

tcp 0 0 192.168.1.9:60254 74.125.25.94:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:53289 216.58.216.160:443 ESTABLISHED 3676/iceweasel

tcp 0 0 192.168.1.9:51133 216.58.216.160:80 ESTABLISHED 3676/iceweasel

—
Reply to this email directly or view it on GitHub
#36 (comment).

ghost · 2014-11-29T17:18:01Z

k

lgandx · 2014-11-29T20:38:22Z

Closing this issue since it looks like it was resolved. Thx digninja.

limited-root · 2017-12-17T12:25:34Z

my netstat output is:
tcp6 0 0 :::443 :::* LISTEN
how could i kill it to make responder work for ssl?

hktalent · 2018-12-10T04:06:10Z

#124 #36 #45

lgandx closed this as completed Nov 29, 2014

This was referenced Dec 10, 2018

Ports being "used" #124

Open

can't listen on some ports (5353,5355) #45

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error starting TCP server on port 443 #36

Error starting TCP server on port 443 #36

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

lgandx commented Nov 29, 2014

limited-root commented Dec 17, 2017

hktalent commented Dec 10, 2018

Error starting TCP server on port 443 #36

Error starting TCP server on port 443 #36

Comments

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

ghost commented Nov 29, 2014

digininja commented Nov 29, 2014

ghost commented Nov 29, 2014

lgandx commented Nov 29, 2014

limited-root commented Dec 17, 2017

hktalent commented Dec 10, 2018