Skip to content
Snippets Groups Projects

Torbrowser surf localhost through Tor

    • Closed (moved) Issue created by Trac @tracbot

    Hi!

    I have a big problem. Yesterday I installed a program called xampp. I typed in the address bar of the TOR browser https://127.0.0.1 and it's working. However, I would need the localhost is reached, but this does not work. Why? Someone can help me?

    Trac:
    Username: toldmikl

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Trac added component::applications/tor browser owner::tbb-team priority::medium reporter::toldmikl resolution::wontfix severity::normal status::closed tbb-torbutton type::defect labels

      added component::applications/tor browser owner::tbb-team priority::medium reporter::toldmikl resolution::wontfix severity::normal status::closed tbb-torbutton type::defect labels

    • Trac
      Trac @tracbot ·
      Author

      Trac:
      Username: toldmikl

      tor

    • Trac
      Trac @tracbot ·
      Author

      Trac:
      Username: toldmikl

    • Trac
      Trac @tracbot ·
      Author

      I attach the picture so you can see what I want to do. I want to open this file: localhost/index.html. How can I do it?

      Trac:
      Username: toldmikl

    • C
      cypherpunks @cypherpunks ·

      Support of localhost was destroyed by MiCthulhu because code wasn't maintained. Need to code some another support, or to fix Firefox bug and then possible to put localhost back to network.proxy.no_proxies_on.

    • C
      cypherpunks @cypherpunks ·

      Trac:
      Type: task to defect
      Priority: critical to normal

    • C
      cypherpunks @cypherpunks ·

      Trac:
      Summary: I can't use xampp localhost in TOR Browser to Torbrowser surf localhost through Tor

    • E
      Erinn Clark @erinn ·

      Trac:
      Owner: mikeperry to tbb-team
      Keywords: N/A deleted, tbb-torbutton added
      Component: TorBrowserButton to Tor Browser

    • B
      bugzilla @bugzilla ·

      Replying to cypherpunks:

      Support of localhost was destroyed by MiCthulhu because code wasn't maintained. "Support" (a DNS hole) was destroyed when Firefox started to obey Remote DNS rule. Tor refuses to resolve "localhost". So, even if you add "localhost" to network.proxy.no_proxies_on, you get "Unable to find the proxy server" webpage. Need to code some another support, or to fix Firefox bug Fixed. and then possible to put localhost back to network.proxy.no_proxies_on. If you put something there, you get:

      Torbutton INFO: aProxy is null
TypeError: originalProxy is null domain-isolator.js:77:7

      Should Tor Browser allow it?

      p.s.

      I typed in the address bar of the TOR browser ​https://127.0.0.1 and it's working. Bug. Fixed. In TBB 6.5a2:

      [08-21 17:26:30] Torbutton INFO: tor SOCKS: https://127.0.0.1/ via 127.0.0.1:2f492e7768755f3b659f4dcb9c781b59
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 NEW 0 127.0.0.1:443 SOURCE_ADDR=127.0.0.1:60727 PURPOSE=USER
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 FAILED 0 127.0.0.1:443 REASON=PRIVATE_ADDR
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 CLOSED 0 127.0.0.1:443 REASON=PRIVATE_ADDR
[08-21 17:26:30] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
Tor WARN: Rejecting SOCKS request for anonymous connection to private address [scrubbed].

      But if you add "127.0.0.1" to network.proxy.no_proxies_on, firefox.exe starts to connect to your xampp.

      Trac:
      Milestone: TorBrowserBundle 2.3.x-stable to N/A
      Reviewer: N/A to N/A
      Sponsor: N/A to N/A
      Severity: N/A to Normal

    • Mark Smith
      Mark Smith @mcs ·

      Trac:
      Cc: N/A to brade, mcs

    • C
      cypherpunks @cypherpunks ·

      I opened online banking site only and saw

      [05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445

      I found only this ticket by searching "TorLauncher NOTE: WARN DANGEROUS_SOCKS", so I pasted it here. What do all that mean? Is that site trying to attack my computer, or how can I interpret that? Thanks in advance.

    • Roger Dingledine
      Roger Dingledine @arma ·

      For the original ticket: you are never going to be able to surf to localhost via Tor Browser, because that would open up too many proxy bypass holes.

      For the new comment: neat bug! I have opened #22461 (moved) to track it. It's harmless -- just a scary warning if you happen to be listening to the warnings.

    • Roger Dingledine
      Roger Dingledine @arma ·

      Closing original bug as wontfix, because localhost isn't something you should usefully go to with Tor Browser.

      Trac:
      Status: new to closed
      Resolution: N/A to wontfix

    • Trac closed

      closed

    • cypherpunks mentioned in issue #10686 (closed)

      mentioned in issue #10686 (closed)

    • Roger Dingledine mentioned in issue #22461 (moved)

      mentioned in issue #22461 (moved)

    • Trac mentioned in issue tpo/core/tor#22461 (closed)

      mentioned in issue tpo/core/tor#22461 (closed)

    • Trac moved to tpo/applications/tor-browser#10165 (closed)

      moved to tpo/applications/tor-browser#10165 (closed)

    Please register or sign in to reply