Debug: Port 443 is already being handled

Support Onion Services
1

Hi,

I launched my TOR Daemon.

And It’s look-like that my Onion service, should come up soon (how long it’s take generally for the propagation of the .onion to be completed ?)

As I’ve seen

[notice] Bootstrapped 100% (done): Done

in my notices log

–
But what worry me is in the debug log I see in loop the following:

[debug] circuit_remove_handled_ports(): Port 443 is already being handled; removing.

What is it ?

Thanks.

1 Like
2

I have a similar problem and can’t find anything.
I have a Tor running on a router with OpenWrt and I don’t have a hidden service or bridge only a SocksPort configured. I also don’t have a webserver on the 443 port but my logs filled with repeating messages like this:

[debug] conn_write_callback(): socket 10 wants to write.
[debug] flush_chunk_tls(): flushed 514 bytes, 0 remain.
[debug] connection_handle_write_impl(): After TLS write of 514: 0 read, 536 written
[debug] circuit_remove_handled_ports(): Port 443 is already being handled; removing.
[debug] circuit_remove_handled_ports(): Port 443 is already being handled; removing.
[debug] circuit_remove_handled_ports(): Port 443 is already being handled; removing.
[info] channelpadding_send_padding_cell_for_callback(): Sending netflow keepalive on 2 to [scrubbed] ([scrubbed]) after 8441 ms. Delta 0ms
3

Hello!

If you could, provide the output of the command sudo ss -anlp4 or sudo netstat -anp

This will show you open ports and what processes are running on them.

2 Likes
4

An old thread, but not resolved. I have the same issue on me device. OpenWrt router, no hidden services, and logs spammed with:

Oct 16 21:20:37.000 [debug] circuit_remove_handled_ports(): Port 443 is already being handled; removing.

Netstat confirms port 443 is not being used by anything else.

EDIT: More importantly, on this device I’m not running Tor as a relay. It is set to listen for SOCKS connections only. @0xbytes old reply seems to imply that Tor is trying to listen on 443 and can’t. Why is it trying to listen at all and how can I configure it not to?

5

Could it be that you have port 443 configured to access the router?

Maybe I’m saying something obvious and unreasonable but the only thing I can think of is that the router itself has the port listening.

something of the style

##::[[— OpenWrt uHTTPd Config —]]::##

Servers -----##
#=
# Main #
#—
config uhttpd ‘main’
list listen_http ‘192.168.1.1:80’
list listen_https ‘192.168.1.1:443’

6

No, nothing else is listening on it. Not even the local web server - it’s not operating on https.

I don’t think this error message has anything to do with the local port 443 being occupied. For example, on my machine I can use socat to listen on 0.0.0.0:443 and forward it to 80, and it works just fine:

$ socat TCP4-LISTEN:443 TCP4:192.168.1.10:80
$ netstat -telunp
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      4289/socat

So clearly nothing is occupying port 443 locally, and tor should have not trouble binding it if it wants.

I also can’t think of why tor would want to bind 443 locally, since on this device it’s operating only as a client/SOCKS server and it’s binding 9050 for SOCKS.

7

The message comes from the place where circuits are being built/used.
I didn’t dig deep into it, but you can assume, that a remote port is meant, not a local one.

There is no reason to enable the debug log level as relay operator or client-side user until a dev asks you to do so.

If it would be something critical, it would show up as an error or a warning and you would see it in a lower log level also.

Don’t search for problems, if you don’t have any.