I don’t know if editing torrc could break the app, but I know that there is torrc file in the data directory at Bisq/btc_mainnet/tor.
You can find it under those locations:
I think it will be overwritten at startup if you edit that. But you can edit it in the code base and run from source. On Github a Chinese reported that it worked for him. I don’t think it can break anything in Bisq editing the file.
thanks for your reply , but i don’t know where to edit the code ,
thank for your reply , yeah , i know there is a torrc file , i tryed to edit it , but it will be overwritten at startup , so i mean if it can be edit and run the new config file would be solve the problem , i try to edit it when it running , and find the kill -SIGHUP PID still does not working , i don’t know is there any sense with kill -SIGHUP command , i install the bisq with dpkg -i xxx.deb , if i build from source , i don’t konw where to edit the code , and if if ok from build from source , thanks !
Just run from source with the edited tor file. I mean the tor file need to be edited in the source code path:
/jtorproxy/src/main/resources/torrc
Having trouble trying to connect via obfs4 bridges.
Iv managed to build the source code on ubuntu VM easily enough following the build guide @ https://github.com/bisq-network/exchange/blob/master/doc/build.md
& editing the above mentioned /jtorproxy/src/main/resources/torrc file in the source.
My goal was to get obfs4 bridges working first as i wouldnt mind this option myself & then later try https proxy option on top later.
Im not in china, just trying to test/help out.
obfs4 bridge is probably not working because of incorrect torrc file.
I also dont see obfs4proxy running as a process on my system either.
Thought id just post here first if something is obviously incorrect with the posted torrc below, the torrc manpage has not helped except to confuse me.
bisq is just stuck at the start trying to initialise.
This is the torrc generated after building @ /home/bisq2/.local/share/Bisq/btc_mainnet/tor/torrc
https://paste.fedoraproject.org/paste/puiF~PYqptiHha08BUrLKQ
& bisq loglevel all
https://paste.fedoraproject.org/paste/-RTJL8lWx8NMIX8yvfxEtw
Just noticed this issue on github. Ill have a read!
The torrc file is taken from the tor zip and then appended with some local paths. So the attempt to just change the file in src code does not work unfortunately unless you change the zip file (I looked into it a few days ago and saw that it requires a different approach described in the GH issue).
I think plugable transports are not supported in the current tor library, but there is a tor library (https://github.com/JesusMcCloud/netlayer) from the contributor who helped in the beginning with the tor lib which has plugable transports support. It is not adopted yet to our API and not tested. Any dev is welcome to work on that. I think it is not too much effort, but I am occupied with other tasks, so I cannot work on that any time soon.
I just added a GH issue for it: https://github.com/bisq-network/exchange/issues/971