07:41:35 <monero_user> Hello. I have been running a monero node behind TOR for about 1 month now. It set up a  (private) RPC onion service which works well. However I have not been able to set up a working p2p onion service. 
07:41:53 <monero_user> I have read https://monerodocs.org/running-node/open-node-tor-onion/  and https://github.com/monero-project/monero/blob/master/docs/ANONYMITY_NETWORKS.md
07:42:23 <monero_user> but my node does not get incoming connecitons 
07:43:20 <monero_user> in the bitmonero.conf I added: 
07:43:28 <monero_user> 1) tx-proxy=tor,localhost:9050,10
07:43:37 <monero_user> 2) anonymous-inbound = _myonionaddress_.onion:18083,0.0.0.0:18083,10
07:43:44 <moneromooo> I assume your tor server is running ?
07:44:13 <moneromooo> Sometimes it takes a while to get incoming. Did you setup that a month ago too or more recently ?
07:44:44 <monero_user> more recently but I did test connectivity using: https://www.ditatompel.com/monero/remote-node
07:44:53 <monero_user> this website reports that it can't connect
07:46:09 <monero_user> The onion service (TOR-wise) is set up correctly: if I shut down monerod and just start a webserver at port 18083, the web page is reachable via TOR. So the TOR-side of things is set up correctly.
07:46:57 <monero_user> I have wrote this forum post in the Whonix forum, but so far without much success: http://forums.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/t/monero-full-node-with-incoming-onion-service-inside-whonix-workstation/13512
07:49:31 <moneromooo> Looks similar to my setup, I used 127.0.0.1 instead of 0.0.0.0 though.
07:49:42 <moneromooo> (in --anonymous-inbound)
07:49:47 <monero_user> are you using Whonix as well?
07:49:49 <moneromooo> And I have incoming on tor atm.
07:49:53 <moneromooo> No.
07:50:08 <monero_user> in Whonix the incoming connection comes from another VM (Whonix Gateway) not from 127.0.0.1
07:50:18 <moneromooo> Oh right.
07:53:01 <monero_user> from time to time I get the following message in monerod:
07:53:06 <monero_user> Unable to send transaction(s) to tor - no suitable outbound connections at height 2595090
08:02:07 <monero_user> moneromooo: in the anonymous-inbout command, what local port do you use? The same defined by the p2p-bind-port command? Or another one?
08:02:39 <moneromooo> I followed ANONYMITY_NETWORKS.md.
08:05:07 <monero_user> would you mind sharing your working bitmonero.conf ? (omitting sensitive data, like your onion address of course)?
08:05:40 <moneromooo> I have none. I told you the difference I had, and you made a good point about why that difference is.
08:06:35 <moneromooo> I also have s/10$/25/ but that isn't relevant AFAIK.
08:06:58 <moneromooo> My command line is:
08:08:12 <moneromooo> ./monerod --no-igd --no-zmq --in-peers 1024 --anonymous-inbound FOO.onion:18083,127.0.0.1:18083,25 --tx-proxy tor,127.0.0.1:9050,10 --rpc-restricted-bind-port 18089
08:08:19 <moneromooo> (with irrelevant stuff omitted)
08:09:04 <moneromooo> My hidden service address is public anyway, it's a seed node.
08:10:53 <monero_user> moneromooo: thanks! Do I understand correctly that you did not specify values for p2p-bind-ip and p2p-bind-port ?
08:25:00 <moneromooo> Correct.
08:28:05 <monero_user> moneromooo: thanks a lot. I think I am starting to understand.
08:28:30 <monero_user> the 'status' command reports 0(in), howerver I suspect this 'status' command only shows clearnet connections.
08:28:51 <monero_user> instead 'print_cn | grep Tor' gives me a number of (in) and (out) Tor connections
08:36:59 <moneromooo> Could be a bug in status. If you confirm it's borked (make sure it's not a restricted RPC thing for example), you can file a bug on github.
08:38:54 <moneromooo> It does look like I'm seeing the same thing, connection count is buzzing about, but it does look like status only shows clearnet, yes.
08:50:01 <monero_user> maybe it should not be considered a bug, but as a limited fature. 'status' should display clearnet and TOR and i2p separetely.
09:14:49 <Guest98> hello
09:15:40 <Guest98> on 1 april i paste here  "multisig_account.cpp:117:81: error: no member named 'MULTISIG_MAX_SIGNERS' in namespace 'config'
09:15:41 <Guest98>     CHECK_AND_ASSERT_THROW_MES(signers.size() >= 2 && signers.size() <= config::MULTISIG_MAX_SIGNERS,
09:15:41 <Guest98>                                                                         ~~~~~~~~^
09:15:42 <Guest98>  /misc_log_ex.h:175:60: note: expanded from macro 'CHECK_AND_ASSERT_THROW_MES'
09:15:42 <Guest98> #define CHECK_AND_ASSERT_THROW_MES(expr, message) do {if(!(expr)) ASSERT_MES_AND_THROW(message);} while(0)
09:15:43 <Guest98>                                                            ^~~~
09:15:44 <Guest98> if (inputs > 0)  "
09:15:47 <Guest98> same after 4 days
09:15:55 <Guest98> just git clone nothing else
10:08:22 <Guest98> anyone her?
10:10:06 <moneromooo> I told the author of the multisig code, they might have a look when they're around.
10:10:27 <moneromooo> I assume it's a merge problem when more than one patch is merged at a time.
10:14:19 <Guest98> code is added without testing?
10:14:35 <Guest98> monero is very serius business
10:15:23 <moneromooo> What is testimg ?
10:17:35 <Guest98> why the guy that added multisig code didnt try to compile
10:21:24 <moneromooo> You'd need to download the code to a computer. Takes at least 10 minutes.
10:22:06 <Guest98> i did exactly that
10:22:09 <moneromooo> And to teach them to compile. Like, have a termainal and all ? And type "make" ? Those guys are used to mouse, not keyboards.
10:22:33 <moneromooo> Anyway, in case you're actually wondering:
10:22:54 <moneromooo> Coders make patches. Those usually compile.
10:23:12 <moneromooo> Maintainers merge patches, typically many at once in the list that got reviewed.
10:23:50 <moneromooo> Patches aren't always fully compatible, which leads to those issues. A typical problem might be that something got moved in a patch and another patch was expecting it in the original place.
10:24:02 <moneromooo> These things are typically fairly easy to resolve.
10:24:23 <moneromooo> Maintainers could build what they merge, but we're *very* short of maintainer time.
10:25:04 <moneromooo> Maintainers are also in a position where they could alter what they merge, so we don't (I hope) OK anyone who wants to do that job.
10:25:15 <moneromooo> So it's a fine line.
10:25:38 <moneromooo> It's free software, and it's got the usual benefits and limitations of free software.
10:28:01 <Guest98> luigi1111 is the maintainer
10:28:18 <Guest98> he has deep knowledge of crypto generally
10:28:43 <Guest98> strange that he didnt catch that wrong patch
10:29:04 <moneromooo> That's because you did not understand what I wrote.
10:29:45 <moneromooo> Knowledge of crypto would not help there fwiw.
10:32:14 <Guest98> yes your answers are not straight are like hieroglyphics
10:32:34 <Guest98> decoding is needed...
10:32:45 <moneromooo> Ah, you can start from "Anyway, in case you're actually wondering", I was being sarcastic before :D
10:48:02 <Guest98> now we wait for luigi to update ok?
10:54:53 <moneromooo> The author I assume, then luigi can merge that fix.
10:55:53 <moneromooo> Actually, I'll look at it now, maybe I can fix if it doens't need understanding the ms code.
10:58:30 <moneromooo> And it's already built that part. Builds fine from latest master. Either it's fixed already or you're doing something wrong.
10:58:40 <moneromooo> What's the commit hash you're building ?
15:02:16 <luigi1111w> good job moneromooo