# Stuck on 3/4 Hidden Service Published V9.3 **URL:** \ **Category:** Support\ **Created:** [January 13, 2019, 12:04am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908 "2019-01-13T00:04:25Z")\ **Posts on this page:** 16\ **Page:** 2
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [February 26, 2019, 3:18pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/21 "2019-02-26T15:18:52Z")
> [@grace](#): > > On a closer look at the logs, it appears that my test installation has a stubborn inability to open and maintain even one connection to seed nodes (no problem opening and receiving connections to regular peers, only seeds are affected). Thanks for the return @grace . That seems a bit strange, regular peers and seednodes are both onions. Why connection issues with seednodes and not with P2P nodes ? If we could have a look at the concerned part of the logfile, it would be nice. … I ping ~~Gandalf~~ @ManfredKarrer 😉 ---
**Author:** ![grace](https://bisq.community/letter_avatar/grace/32/5_5575768a8748004e209b776fc1b2916d.png) [@grace](https://bisq.community/u/grace)\ **Post date:** [February 27, 2019, 9:51am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/22 "2019-02-27T09:51:13Z")
> [@Homard](#): > > Why connection issues with seednodes and not with P2P nodes ? If I were to make an uneducated guess based solely on external observations, it could be a combination of a two factors: - different network traffic patterns between seeds and peers - my crappy broadband connection. If this doesn’t seem to make any sense, then it probably doesn’t. 🙂 > [@Homard](#): > > If we could have a look at the concerned part of the logfile, it would be nice. I have TWO log fragments for you, which I hope will help to corner the problem. Apologies for the wall. The first one is from a working installation: > Feb-26 04:37:37.908 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: We send a PreliminaryGetDataRequest to peer [fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000). > Feb-26 04:37:51.993 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: > ################################################################# > Connected to node: [fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000) > Received 540 instances > Filter: 1 > MailboxStoragePayload: 276 > Alert: 1 > Arbitrator: 2 > OfferPayload: 260 > ################################################################# > Feb-26 04:37:55.392 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: Start processing 0 items. The second fragment is from my non-working “3/4” installation: > Feb-26 12:16:38.651 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: We send a PreliminaryGetDataRequest to peer [fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000). > Feb-26 12:17:38.555 [JavaFX Application Thread] WARN b.n.p.p.g.RequestDataManager: We have started already a requestDataHandshake to peer. [nodeAddress:8000=fl3mmribyxgrv63c.onion](http://nodeAddress:8000=fl3mmribyxgrv63c.onion) > Feb-26 12:17:38.652 [JavaFX Application Thread] INFO b.n.p.p.g.RequestDataHandler: A timeout occurred at sending getDataRequest:PreliminaryGetDataRequest(supportedCapabilities=[0, 1, 2, 7]) on nodeAddress:fl3mmribyxgrv63c.onion:8000 > Feb-26 12:18:44.754 [[InputHandler-fl3mmribyxgrv63c.onion:8000](http://InputHandler-fl3mmribyxgrv63c.onion:8000)] INFO b.n.p.n.Connection$SharedModel: Shut down caused by exception java.net.SocketTimeoutException: Read timed out on connection=Connection{peerAddress=Optional[[fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000)], peerType=SEED\_NODE, uid=‘1c112047-32de-4631-93e9-5c6a175a30ee’} > Feb-26 12:18:44.774 [JavaFX Application Thread] INFO b.n.p.p.PeerManager: onDisconnect called: nodeAddress=Optional[[fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000)], closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET\_TIMEOUT > Feb-26 12:18:44.822 [JavaFX Application Thread] INFO b.n.p.p.p.PeerExchangeManager: onDisconnect closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET\_TIMEOUT, nodeAddressOpt=Optional[[fl3mmribyxgrv63c.onion:8000](http://fl3mmribyxgrv63c.onion:8000)] The same failure pattern is repeated in the log several times, however the “connected to node” message and item summary (as shown in the first example) never happen on the test installation. Only timeouts and other errors. However, the normal peer connections don’t seem to be similarly affected, or at least not in a significant degree. Strange indeed. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [February 28, 2019, 4:47am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/23 "2019-02-28T04:47:44Z")
@grace @NCKoeter@au_Bits@httphive Sorry to hear about those issues. Can you please send me the log file ([manfred@bitsquare.io](mailto:manfred@bitsquare.io)). You can open it at Account/backup. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [February 28, 2019, 6:13am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/24 "2019-02-28T06:13:46Z")
Could you try with an old bisq version? You would need to rename the current data directory to not overwrite the data there (might be incompatible with downgrade). Not sure if on Window its easy to downgrade, but make a backup just in case before doing it (e.g. de-installing will delete it!). Maybe you can go back to 0.8.1 or so as we can be sure that its a different tor library version. > **[Release v0.8.1 · bisq-network/bisq](https://github.com/bisq-network/bisq/releases/tag/v0.8.1)** > > s/tag/v0.8.1 ---
**Author:** ![NCKoeter](https://bisq.community/letter_avatar/nckoeter/32/5_5575768a8748004e209b776fc1b2916d.png) [@NCKoeter](https://bisq.community/u/NCKoeter)\ **Post date:** [February 28, 2019, 10:36pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/25 "2019-02-28T22:36:03Z")
I will send the logfile after nexxt errors. Because I now again restarted with new data directory and some trades have worked. But it seemed there were 2 specific offers before that I would always get the errors. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [March 1, 2019, 12:35am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/26 "2019-03-01T00:35:31Z")
It can be that there is a bug on the makers side if same offer fails or the makers computer is in sleep mode and network too slow to respond in time. ---
**Author:** ![grace](https://bisq.community/letter_avatar/grace/32/5_5575768a8748004e209b776fc1b2916d.png) [@grace](https://bisq.community/u/grace)\ **Post date:** [March 6, 2019, 1:09pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/27 "2019-03-06T13:09:22Z")
In the particular issue of “3/4”, downgrading to 0.8.1 made no difference in my case (problem persisted). @ManfredKarrer, I have sent a log file, hope it helps. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [March 6, 2019, 6:17pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/28 "2019-03-06T18:17:13Z")
Thanks! So it seems it is a local issue with eiter your onion address, provider, network connectivity or IP. Can you try with a new data directory? You can pass --appName=Bisq\_test so it will create a new wallet and onion address. If that does not help, can you try a VPN or change your IP (e.g. by restarting your network divices or requesting from the provider a new one if its not a dynamic IP)? ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [March 6, 2019, 6:20pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/29 "2019-03-06T18:20:20Z")
@ManfredKarrer isn’t it --appDataDir=‘Bisq\_test’ ? ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [March 6, 2019, 10:22pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/30 "2019-03-06T22:22:50Z")
Works as well. From appName the data dir gets derived. ---
**Author:** ![freimair](https://bisq.community/user_avatar/bisq.community/freimair/32/2018_2.png) [@freimair](https://bisq.community/u/freimair)\ **Post date:** [March 7, 2019, 3:49pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/31 "2019-03-07T15:49:38Z")
Hi @grace, I am now onto investigating Bisq on Tor (also [https://github.com/bisq-network/bisq/issues/2278](https://github.com/bisq-network/bisq/issues/2278)). thanks for the information thus far. If I find anything, I will let you know. ---
**Author:** ![grace](https://bisq.community/letter_avatar/grace/32/5_5575768a8748004e209b776fc1b2916d.png) [@grace](https://bisq.community/u/grace)\ **Post date:** [March 9, 2019, 1:36pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/32 "2019-03-09T13:36:36Z")
Hi @freimair, thanks for looking into this. Just to establish a baseline of things that have already been tried: - versions 0.8.1, 0.9.3, 0.9.4 and 0.9.5 all had the same problem, or very similar - rebooting the router, changing dynamic WAN IP address, also Tor-over-VPN and Tor-over-Tor did not fix the problem (only made everything much slower) - starting with a new data directory, or using an aged one, made no difference - my network connection is _slow_, especially on upload Also, as pointed out in the github issue, running Bisq straight on Tails is not possible; some configuration changes are required to enable it. At a minimum, I found that the following are needed: - `sudo iptables -I OUTPUT -o lo -p tcp -j ACCEPT` - `sudo cp -f /var/run/tor/control.authcookie /home/amnesia/.local/share/` After this, Bisq can be run as unprivileged user _amnesia_: `/opt/Bisq/Bisq --torControlPort=9052 --torControlCookieFile=/home/amnesia/.local/share/control.authcookie` I have sent @ManfredKarrer a copy of my Bisq debug log, can send it to you too if you’re interested. ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [March 9, 2019, 2:00pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/33 "2019-03-09T14:00:45Z")
Hi @grace , What is the type of you connection ? wifi ? How is your IP ? fix or dynamic ? If the question are too indiscreet, please ignore (or answer by PM). ---
**Author:** ![grace](https://bisq.community/letter_avatar/grace/32/5_5575768a8748004e209b776fc1b2916d.png) [@grace](https://bisq.community/u/grace)\ **Post date:** [March 9, 2019, 11:58pm UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/34 "2019-03-09T23:58:15Z")
@Homard, My connection is rural-grade ADSL, decent downlink (1-1.5Mb/s) with slow uplink (150-200kb/s). There is no firewall or UPNP running on my router, no restrictions ISP-side either. WAN IP is dynamic. LAN is a private subnet with NAT. Bisq+Tails computer connected via WiFi or Ethernet. There is no significant difference between the two, since ADSL is always the bottleneck. The same setup has been used successfully to test other peer-to-peer software in the Tails environment, such as OpenBazaar, Bitmessage and Lightning Labs LND, which all worked well (one at a time). 🙂 I hope this gives you an idea. ---
**Author:** ![freimair](https://bisq.community/user_avatar/bisq.community/freimair/32/2018_2.png) [@freimair](https://bisq.community/u/freimair)\ **Post date:** [March 14, 2019, 10:33am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/35 "2019-03-14T10:33:43Z")
> > > Hello, > > Here says Bisq working problem on Tails (reported here: https://githu…b.com/bisq-network/bisq/issues/811) now is solved with https://github.com/bisq-network/bisq/pull/1935, as long as now Bisq can use an external Tor services. > > Yet for me this issue could nt be solved at all. I'm working on it for like 25 hours, but I'm a noob and couldn't do it. What did I do: > > > Now it seems we have this 4 options with this new version: > > \--torControlCookieFile \ > > \--torControlPassword \ > > \--torControlPort \ > > \--torControlUseSafeCookieAuth > > > 1-) I began with the easiest one, using with control port as long as > a line in '/etc/tor/torrc.orig.1' > > reads > > ... > > ControlPort 9052 > > ... > > > So I run > > $./Bisq --torControlPort 9052 > > > Outcome: No Use, Bisq crashes even before connecting to the Tor, exactly as before. > > > 2-) I cannot telnet localhost on Tails either to learn the specifics of my network connection, so my attempt to telnet localhost did not do any good either. > > > 3-) So I go on and open the torrc file on the shared user folder of Tails, this seemed me as the most liable option because the main torrc file of Tails is this afaik. So I type, > > $cat '/usr/share/tor/tor-service-defaults-torrc' > > Now it's read here: > > \------------ > > DataDirectory /var/lib/tor > PidFile /var/run/tor/tor.pid > RunAsDaemon 1 > User debian-tor > > ControlSocket /var/run/tor/control GroupWritable RelaxDirModeCheck > ControlSocketsGroupWritable 1 > SocksPort unix:/var/run/tor/socks WorldWritable > SocksPort 9050 > > CookieAuthentication 1 > CookieAuthFileGroupReadable 1 > CookieAuthFile /var/run/tor/control.authcookie > > Log notice syslog > > \------------ > > So what do I do? > > a-) now I cannot hexdump on this control.authcookie file to Authenticate it because Tails won't let me do it. And I guessed I did not need it either, because there was this safecookie option. So I type: > > $ ./Bisq --torControlCookieFile='/var/run/tor/control.authcookie' --torControlUseSafeCookieAuth > > I take: "error: Option(s) \[torControlCookieFile\] are unavailable given other options on the command line" > > (((------ I also used these options with refering to directory '/var/run/tor-instances/amnesia/control.authcookie' and '/var/run/tor-instances/debian-tor/control.authcookie' as this autcookie is listed on '/usr/share/tor/tor-service-defaults-torrc-instances' as '/var/run/tor-instances/@@NAME@@/control.authcookie' ------ This was again with no use, unsurprisingly I guess.))) > > b-) I'm a noob, I'm confused. Without a string in directory part, I try again: > > $ ./Bisq --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth > > Same error: > error: Option(s) \[torControlCookieFile\] are unavailable given other options on the command line > > c-) I torify it, Same result. But there is now also a line that reads: 1547727541 WARNING torsocks\[670\]: \[syscall\] Unsupported syscall number 229. Denying the call (in tsocks\_syscall() at syscall.c:488) So I decide to not to use torify > > > d-) Now it seems something missing with using this --torControlCookieFile command, it seems there is something I need to add, so I begin adding other options, first by binding the main torrc file so maybe it can add the missing parts: > > $ ./Bisq --torControlCookieFile='/var/run/tor/control.authcookie' --torControlUseSafeCookieAuth --torrcFile='/usr/share/tor/tor-service-defaults-torrc' > > Same error: error: Option(s) \[torControlCookieFile\] are unavailable given other options on the command line > > > e-) I thought there may be a socks problem and try to reconfigure the socks5's through the whitelisted addresses by Tails (Don't laugh, I really don't know what I'm doing at all, just trying to find blind-sighted, as my knowledge of ANY language of programming is none, zero, empty, null. But my want to use Bisq on Tails is great, and I just want to use Bisq on Tails as an end-user, that's all. Anyways, I do this:) > > $ ./Bisq --torControlCookieFile='/var/run/tor/control.authcookie' --torControlUseSafeCookieAuth --socks5ProxyBtcAddress=127.192.0.1:9050 --socks5ProxyHttpAddress=127.192.0.2:9050 > > (Because on the riseup it says 127.192.0.0/10 are whitelisted as SOCKS5 so I thought this can maybe what this needs.) > > Outcome: Same error. > > \*\*\*3-) Ok, then I start from scratch. Now I randomly try some other options on --help, and then I find when I use --useLocalhostForP2P=True , the program actually starts and GUI also starts! Cool. This was a fine finding. Then my above SOCKS5 attempts made some sense at least. > > However, after running this, the GUI ran, but it could not connect to any node, however I wait. Connection refused > > \---- > > Okay, after this, now I stop writing the trial and errors I did, because despite now I spent many hours on this, and I tried many many things, the outcome has been more or less the same ("connection refused", that is). I combined almost all ./Bisq commands with --useLocalhostForP2P=True , I edited the GUI options, I edited TorControlPort and NodePorts to 9052, and 9051, and some other ports I don't remember but found that could work elsewhere (or on "ferm"), I connected through obfs4bridges to Tails but this time with only those using the port 9443, and tried to restrict all the ports Bisq uses to 9443, and tried combinations of Bisq port commands and GUI network options to work through that port, I tried to find some other Bisq nodes that do not work through the 8333 port, I tried to whitelist the 8333 port on Tails but I couldn't do that, and then I decided that I didn't want to mess with that. Instead from the GUI I tried different transport type bridges, then I added custom bridges, then I even added my local host as a bridge, I checked and unchecked connecting through the Tor from the GUI and; combined all these all above combinations of the combinations of combinations and then recombined them... Connections all refused. No nodes connected. > > Now at some instances in these maybe I succeeded in somethings, because for this one time BTC price updated from 4000 to 3600 but I noticed this too late so I don't know, because I was too focusedon console ant its refusals of connections because it just didn't stop refusing connections at all, at any point. > > And maybe in some cases I just couldn't connect any node because I am already connecting Tails through transport bridges ((obfs3 and obfs4, I am from a restrictive country, even normal bridges are restricted here) so these may also be related with that. > > In sum, this was all I could do as a noob, and the result was the same: failure. I and people like me would really, really like that one of you knowledgeable fellas would add one easy step-to-step guide for using Bisq on Tails, because it's said now it's supported but it seems to be really hard to do, but there has to be some easy way that I just miss because I just don't have enough information. And also I would be glad if you also consider those who can only run onions through transport bridges. > > With appreciation to all your works, and kind regards. ---
**Author:** ![grace](https://bisq.community/letter_avatar/grace/32/5_5575768a8748004e209b776fc1b2916d.png) [@grace](https://bisq.community/u/grace)\ **Post date:** [March 15, 2019, 7:34am UTC](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908/36 "2019-03-15T07:34:14Z")
Hi @freimair, thanks for the update. Unfortunately this doesn’t solve my problem, which was not Tails-related to start. As per above, I am already using a workaround very similar to the one discussed in issue 2278. My problem, which I suspect affects several posters in this thread (also Github issue 2474) and is not Tails-specific, is about Bisq’s failure to bootstrap correctly under degraded network conditions due to an inability to handshake reliably with seed nodes. I have some new information about the issue and will open a new topic shortly, to avoid thread hijacking. [Previous page](https://bisq.community/t/stuck-on-3-4-hidden-service-published-v9-3/6908.md?page=1)