Noble Test 1 - second part (when the connection completes.
root@tor-n:~# journalctl -u tor@default -f Aug 17 06:22:40 tor-n Tor[1703]: Set list of supported TLS groups to: P-256:X25519:P-224 Aug 17 06:22:40 tor-n Tor[1703]: Bootstrapped 0% (starting): Starting Aug 17 06:22:40 tor-n Tor[1703]: Starting with guard context "default" Aug 17 06:22:40 tor-n systemd[1]: Started [email protected] - Anonymizing overlay network for TCP. Aug 17 06:22:40 tor-n Tor[1703]: Signaled readiness to systemd Aug 17 06:22:41 tor-n Tor[1703]: Opening Socks listener on /run/tor/socks Aug 17 06:22:41 tor-n Tor[1703]: Opened Socks listener connection (ready) on /run/tor/socks Aug 17 06:22:41 tor-n Tor[1703]: Opening Control listener on /run/tor/control Aug 17 06:22:41 tor-n Tor[1703]: Opened Control listener connection (ready) on /run/tor/control Aug 17 06:22:41 tor-n Tor[1703]: Bootstrapped 5% (conn): Connecting to a relay Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 10% (conn_done): Connected to a relay Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 14% (handshake): Handshaking with a relay Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 15% (handshake_done): Handshake with a relay done Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 30% (loading_status): Loading networkstatus consensus Aug 17 06:26:41 tor-n Tor[1703]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus. Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 40% (loading_keys): Loading authority key certs Aug 17 06:26:41 tor-n Tor[1703]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services. Aug 17 06:26:41 tor-n Tor[1703]: Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors Aug 17 06:26:41 tor-n Tor[1703]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/10179, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.) Aug 17 06:30:45 tor-n Tor[1703]: Bootstrapped 50% (loading_descriptors): Loading relay descriptors Aug 17 06:30:46 tor-n Tor[1703]: The current consensus contains exit nodes. Tor can build exit and internal paths. ... Aug 17 06:34:50 tor-n Tor[1703]: Bootstrapped 55% (loading_descriptors): Loading relay descriptors Aug 17 06:34:50 tor-n Tor[1703]: Bootstrapped 61% (loading_descriptors): Loading relay descriptors Aug 17 06:34:50 tor-n Tor[1703]: Bootstrapped 67% (loading_descriptors): Loading relay descriptors Aug 17 06:34:51 tor-n Tor[1703]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Aug 17 06:34:51 tor-n Tor[1703]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Aug 17 06:34:51 tor-n Tor[1703]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit Aug 17 06:34:52 tor-n Tor[1703]: Bootstrapped 100% (done): Done root@tor-n:~# ss -eeapnt | grep tor LISTEN 0 4096 127.0.0.1:9050 0.0.0.0:* users:(("tor",pid=1703,fd=6)) ino:13454 sk:4 cgroup:/system.slice/system-tor.slice/[email protected] <-> root@tor-n:~# curl -v -x socks5h://127.0.0.1:9050 -s https://check.torproject.org/api/ip * Trying 127.0.0.1:9050... * Connected to 127.0.0.1 (127.0.0.1) port 9050 * SOCKS5 connect to check.torproject.org:443 (remotely resolved) * SOCKS5 request granted. * Connected to 127.0.0.1 (127.0.0.1) port 9050 * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=check.torproject.org * start date: Jul 25 00:05:12 2026 GMT * expire date: Oct 23 00:05:11 2026 GMT * subjectAltName: host "check.torproject.org" matched cert's "check.torproject.org" * issuer: C=US; O=Let's Encrypt; CN=YR2 * SSL certificate verify ok. * Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 3: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * using HTTP/1.x > GET /api/ip HTTP/1.1 > Host: check.torproject.org > User-Agent: curl/8.5.0 > Accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing < HTTP/1.1 200 OK < Date: Mon, 17 Aug 2026 07:21:00 GMT < Server: Apache < X-Content-Type-Options: nosniff < X-Frame-Options: sameorigin < X-Xss-Protection: 1 < Referrer-Policy: no-referrer < Strict-Transport-Security: max-age=15768000; preload < Content-Type: application/json < Content-Length: 35 < * Connection #0 to host 127.0.0.1 left intact {"IsTor":true,"IP":"185.220.101.5"} -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2163259 Title: Tor sunsets <=4.8 - update to 4.9.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tor/+bug/2163259/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
