Hidden Service "Generic SOCKS Error"
I recently set up a hidden service. The address for this hidden service is spydaroo7gtsipwm.onion. When I first start Tor on the server, it will work fine. Then after a while, maybe after a few visits or a few hours, it stops working. Both apache2 and Tor continue to run, but Tor Browser just acts as though it doesn't exist (cannot connect). Logs show errors of "general socks error". Tor2web services like onion.to also stop working and give generic SOCKS error. The way to fix this is to restart Tor on the server. It then works, but eventually will return to having a socks error. Does anyone know a reason for why this is happening or how to fix it? — Spydar007 http://spydar007.com PGP Key ID: D3364A0B
On 21 Jul 2016, at 15:49, Darcy Marshall <root@spydar007.com> wrote:
I recently set up a hidden service. The address for this hidden service is spydaroo7gtsipwm.onion. When I first start Tor on the server, it will work fine.
What version of Tor are you running, and on what OS?
Then after a while, maybe after a few visits or a few hours, it stops working. Both apache2 and Tor continue to run, but Tor Browser just acts as though it doesn't exist (cannot connect). Logs show errors of "general socks error". Tor2web services like onion.to also stop working and give generic SOCKS error.
What is the exact error in the Tor client log? Does the hidden service log a client connection (either introduction or rendezvous) at the same time? If you turn on info or debug level logging on your client or hidden service, your logs might give you more information.
The way to fix this is to restart Tor on the server. It then works, but eventually will return to having a socks error. Does anyone know a reason for why this is happening or how to fix it?
Perhaps your server terminates long-running network connections, and Tor has trouble recovering from this? Perhaps the network goes down or slows down? Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B OTR 8F39BCAC 9C9DDF9A DF5FAE48 1D7D99D4 3B406880 ricochet:ekmygaiu4rzgsk6n
What version of Tor are you running, and on what OS?
Debian 8.5, with Tor version 0.2.7.6 (latest stable from the repository)
What is the exact error in the Tor client log? Does the hidden service log a client connection (either introduction or rendezvous) at the same time? If you turn on info or debug level logging on your client or hidden service, your logs might give you more information.
Client: http://pastebin.com/Pp5xqNgC Server: http://pastebin.com/6Dqu23wV The earlier logs (which I stupidly deleted), would say about SOCKS errors, but it has now changed to saying it's an invalid onion address. The onion address and private key are definitely correct, and it works when Tor is first loaded. Give it 10 minutes, and it will stop working. Try in your own client if there are other sections of the log you want.
On 21 Jul 2016, at 23:38, Spydar007 <root@spydar007.com> wrote:
What version of Tor are you running, and on what OS?
Debian 8.5, with Tor version 0.2.7.6 (latest stable from the repository)
What is the exact error in the Tor client log? Does the hidden service log a client connection (either introduction or rendezvous) at the same time? If you turn on info or debug level logging on your client or hidden service, your logs might give you more information.
Client: http://pastebin.com/Pp5xqNgC Server: http://pastebin.com/6Dqu23wV
The earlier logs (which I stupidly deleted), would say about SOCKS errors, but it has now changed to saying it's an invalid onion address. The onion address and private key are definitely correct, and it works when Tor is first loaded. Give it 10 minutes, and it will stop working.
The log message "Invalid onion hostname" is logged by "parse_extended_hostname" when the onion address is the wrong length or the wrong format. Please retry on the client with the correct address. Please also capture the failures out of the server log, not just the debug entries at the time - there's likely a disconnection from the network, or a descriptor upload failure.
Try in your own client if there are other sections of the log you want.
No thanks. Happy to help, but it seems you have some sort of network issue. Adding another client won't tell me much more. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B OTR 8F39BCAC 9C9DDF9A DF5FAE48 1D7D99D4 3B406880 ricochet:ekmygaiu4rzgsk6n
I switched from apache2 to nignx and my .onion site worked better , nginx is more lightweight therefore makes it faster etc(You might have problem with tor and not the webbserver it self, but if u Dont find a sulotion i recommend switching :) Darcy Marshall <root@spydar007.com> skrev: (21 juli 2016 07:49:48 CEST)
I recently set up a hidden service. The address for this hidden service is spydaroo7gtsipwm.onion. When I first start Tor on the server, it will work fine.
Then after a while, maybe after a few visits or a few hours, it stops working. Both apache2 and Tor continue to run, but Tor Browser just acts as though it doesn't exist (cannot connect). Logs show errors of "general socks error". Tor2web services like onion.to also stop working and give generic SOCKS error.
The way to fix this is to restart Tor on the server. It then works, but eventually will return to having a socks error. Does anyone know a reason for why this is happening or how to fix it?
— Spydar007 http://spydar007.com PGP Key ID: D3364A0B
------------------------------------------------------------------------
_______________________________________________ tor-onions mailing list tor-onions@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions
-- Sincerly Flipchan
participants (4)
-
Darcy Marshall -
Flipchan -
Spydar007
-
Tim Wilson-Brown - teor