New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck on ¾ Hidden Service Published V9.3 #2327

Closed
aubits opened this Issue Jan 28, 2019 · 6 comments

Comments

Projects
None yet
4 participants
@aubits
Copy link

aubits commented Jan 28, 2019

Running Bisq 0.9.3 on two of my machines 18.04 and 18.10 are stuck on the 3/4 Hidden Services at load. One of them has two offers open.
I will attach a log file for your perusal.
Please advise

@ManfredKarrer

This comment has been minimized.

Copy link
Member

ManfredKarrer commented Jan 28, 2019

Can u restart and check if it works. If not open the network settings and delete the tor files (if not done vai app make sure to NOT delete the hiddenservice folder!)

@aubits

This comment has been minimized.

Copy link
Author

aubits commented Jan 28, 2019

Deleted all files in TOR folder except the Hidden Services Folder. Now both machines are running Bisq and advertising offers again.
Thanks Manfred.

@HarryMacfinned

This comment has been minimized.

Copy link

HarryMacfinned commented Jan 29, 2019

Its happens sometimes that some Tor file(s) got corrupted.
It seems however strange that this could happen on two neighbour machines at the same moment (?)

@aubits ,
are your machines behind a static IP or a dynamic IP ?

@aubits

This comment has been minimized.

Copy link
Author

aubits commented Jan 29, 2019

Dynamic IP. I thought it curious too. Followed Manfred's instructions and restored on the next load.

@HarryMacfinned

This comment has been minimized.

Copy link

HarryMacfinned commented Jan 29, 2019

The scenario I imagine is that you got a dynamic IP which, for one reason or another, is blacklisted by the Tor network.
So in fact there are no corrupted Tor file(s), but however it's necessary to reinitialize the Tor files.

Nothing sure however.

@ripcurlx ripcurlx added the re:Tor label Jan 30, 2019

@ripcurlx

This comment has been minimized.

Copy link
Member

ripcurlx commented Jan 30, 2019

Closing as complete. Feel free to reopen if the issue occurs again.

@ripcurlx ripcurlx closed this Jan 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment