--- Log opened Thu May 07 00:00:14 2020
00:37 < waxwing> tlo1337, you are failing to connect to Core, as the message says
00:37 < waxwing> aren't you the one who had the issue with a new IP address before on the LAN?
00:43 -!- jon-r__ [~jon-r@104.129.29.26] has quit [Ping timeout: 240 seconds]
00:44 -!- jon-r [~jon-r@104.129.29.26] has quit [Ping timeout: 264 seconds]
00:50 -!- jon-r_ [~jon-r@167.160.174.114] has joined #joinmarket
00:50 -!- jon-r [~jon-r@167.160.174.114] has joined #joinmarket
00:56 -!- Netsplit *.net <-> *.split quits: mr_burdell
00:59 -!- M1 [~Michail@michail.com] has quit [Ping timeout: 246 seconds]
01:00 < tlo1337> right, but my node is running okay and all caught up on blocks so not sure why it would say that
01:01 -!- Netsplit over, joins: mr_burdell
01:01 < tlo1337> yes but that's not an issue anymore i've adjusted that since then
01:01 -!- M1 [~Michail@michail.com] has joined #joinmarket
01:07 -!- CaraDeLevi [c8c3a2f2@gateway/web/cgi-irc/kiwiirc.com/ip.200.195.162.242] has joined #joinmarket
01:09 -!- CaraDeLevi [c8c3a2f2@gateway/web/cgi-irc/kiwiirc.com/ip.200.195.162.242] has quit [Client Quit]
01:10 < waxwing> try connecting to the Core node outside joinmarket, using `bitcoin-cli` and the same rpc credentials.
01:54 < tlo1337> okay, but sorry, im not sure how to do that exactly. i can see that my Core node is running okay though through MyNode's GUI...
01:56 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Read error: Connection reset by peer]
02:10 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
02:44 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 246 seconds]
02:48 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket
03:27 < waxwing> tlo1337, essentially, you need to have it so your rpc configuration works. this depends on: the settings in bitcoin.conf in your bitcoind instance (not only credentials, but also rpcbind and rpcallowip, possibly), the settings in your local joinmarket.cfg (the right rpc credentials, the right host/ip)
03:28 < waxwing> my suggestion is to have a bitcoin installation locally (no need for a blockchain) and use the bitcoin-cli tool provided to check that you actually can connect to bitcoin core over rpc.
03:28 < waxwing> because if you cannot, joinmarket cannot work.
03:29 < waxwing> obviously all this is far easier if joinmarket and bitcoin are on the same machine, but it's far from impossible with a remote Core instance. you just have to get it right.
03:30 < waxwing> (it also depends on any firewall settings that might exist, but that's a lot less likely to be an issue here; anyway, whatever settings there are, you have to check that you can make an rpc call)
03:31 < waxwing> if i had to guess from what you said before, it seems far more likely to be an IP address issue than anything else, since that's what happened to you before.
03:54 < waxwing> AlexCato so picking up the earlier conversation again, the way I understand it: options.txfee (for Taker) was being used only as an initial estimator value, which in turn was only used to warn the user about high fees, but after #328 it can be used to override the tx_fees config, meaning the calculation for that warning will be wrong.
03:55 < waxwing>  #569 came out of tests of #536 but i think i will help kristapsk to change it as per above ^ . there is still a change needed in #536 but the root cause was not related.
04:05 < waxwing> so see this: https://github.com/JoinMarket-Org/joinmarket-clientserver/pull/569#issuecomment-625186355 kristapsk AlexCato
04:08 < waxwing> sorry #383 not #328
04:27 < kristapsk> waxwing, will look at it little bit later
04:50 -!- jonatack_ [~jon@37.164.233.66] has joined #joinmarket
04:54 -!- jonatack [~jon@37.173.38.62] has quit [Ping timeout: 264 seconds]
08:38 -!- stoner19_ is now known as stoner19
08:58 < tlo1337> waxwing okay so since it's not on the same machine i have to ssh into it. so now i have the bitcoin-cli available now but what would you like me to check with it? you mentioned this depends on the settings in bitcoin.conf and joinmarket.cfg, so you'd just like me to check the settings to ensure they have the same rpc creds and host/ip?
09:00 < tlo1337> actually i can also access the bitcoin-cli via the GUI interface as well
09:12 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
09:18 < tlo1337> okay i am in both config files. im sure joinmarket.cfg is correct with the right rpc creds, but what should the file look like for the bitcoin config in regards to rpcbind and rpcallowip?
09:33 -!- emoneyabc [55948986@s55948986.adsl.online.nl] has joined #joinmarket
09:34 -!- emoneyabc [55948986@s55948986.adsl.online.nl] has quit [Remote host closed the connection]
09:38 < waxwing> tlo1337, i don't know, i guess this somehow might already be set up with the node configuration for mynode but: you need to have rpcallowip allow your local machine explicitly, and rpcbind also ... but the fundamental question is, with a local (your computer, that you use) Bitcoin Core installation (not the one on mynode, and it needn't have the blockchain), can you use the bitcoin-cli tool and do any rpc call like `getblockchaininfo` 
09:38 < waxwing> successfully
09:38 < waxwing> but i mean generally your question at this point is not abotu joinmarket it is about bitcoin.
09:46 < tlo1337> hmm okay so maybe this is it, can i share with you the rpcbind and rpcallowip info via PM? im thinking i dont have rpcbind and rpcallowip allowing my local machine explicity
09:49 < tlo1337> wrt the fundamental question though, yes i can i just have to use a terminal to ssh into admin@(mynode IP address). then i was just able to use bitcoin-cli getblockchaininfo
10:01 -!- jonatack_ [~jon@37.164.233.66] has quit [Quit: jonatack_]
10:01 -!- jonatack [~jon@37.164.233.66] has joined #joinmarket
10:03 < waxwing> if you ssh in and do it there, it isn't testing whether you can do it from your local machine, though
10:58 < tlo1337> oh okay i see. so how could i do it from my local machine?
11:02 < tlo1337> and i guess you're saying this is more important than making sure the rpcbind and rpcallowip info is correct? because that's a possible issue as well im just not exactly sure yet
11:30 < waxwing> tlo1337, i'm mostly saying this is not a joinmarket problem, until you can rpc from your local machine to your node; iow #bitcoin might be a good place to ask
11:37 < DSRelBot> [DS/AlexCato] tlo1337, use this command on your machine which runs joinmarket to build a SSH tunnel to your bitcoin node, so that it can directly access it: "ssh username@ip-address -NfL 8332:localhost:8332"
11:37 < DSRelBot> [DS/AlexCato] this will forward the RPC port 8332, which is used to connect from joinmarket to bitcoin core
11:38 < DSRelBot> [DS/AlexCato] then your joinmarket node will behave like it was a local bitcoin core installation
11:41 -!- nothingmuch [~nothingmu@unaffiliated/nothingmuch] has quit [Quit: ZNC - http://znc.in]
11:42 < DSRelBot> [DS/AlexCato] that last sentence is ambiguous: what i meant to say is, that from your joinmarket installation's point of view, it seems like bitcoin core is installed locally (=standard case)
11:44 < tlo1337> okay thanks ill try that out!... understood, thank you
11:45 < tlo1337> and just to be clear, at the beginning of that command, it's ssh username, not admin correct? because usually when i ssh into my node it's ssh admin@ip-adress
11:47 < DSRelBot> [DS/AlexCato] whatever your username is of course :) it's the standard SSH command, just appended by the -NfL (...) thing
11:59 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection]
12:06 < nixbitcoin> While we're on the topic of bitcoind rpc ports, do you know of a way to reserve 8332 for the bitcoin user/service so a malicious user/service can't outrace bitcoind to listen on 8332 for RPC credentials?
12:08 < DSRelBot> [DS/AlexCato] no idea, never really thought about that. If there's a malicious software locally on my machine, you're in a very dark place already anyways
12:09 < DSRelBot> [DS/AlexCato] and in the case of joinmarket, it doesnt even matter; the private keys are in joinmarket, not bitcoin core (core only sees watch-only addresses)
12:14 < nixbitcoin> malicious software on machine: there's a lot one can do though to mitigate the threats from malicious software. We have discretionary access control, AppArmor, containers, etc. Just this problem seems to get so little attention.
13:29 -!- nixbitcoin is now known as nixbitcoindev
13:45 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Remote host closed the connection]
13:45 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has joined #joinmarket
14:32 -!- deafboy [quasselcor@cicolina.org] has quit [Quit: deafboy]
14:32 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
14:33 -!- deafboy [quasselcor@cicolina.org] has quit [Client Quit]
14:36 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket
15:02 -!- EvanitoC [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has joined #joinmarket
15:02 -!- Evanito [~Evanito@cpe-76-87-174-228.socal.res.rr.com] has quit [Ping timeout: 260 seconds]
16:09 -!- asymptotically [~asymptoti@gateway/tor-sasl/asymptotically] has quit [Quit: Leaving]
16:51 -!- jonatack_ [~jon@37.165.219.151] has joined #joinmarket
16:52 < tlo1337> DSRelBot i understood what you were saying, ty, but when i use that command it asks me for a password and none of the passwords im trying that usually work for accessing my node are working. after a certain amount of guesses it says, permission denied (publickey, password)
16:54 -!- jonatack [~jon@37.164.233.66] has quit [Ping timeout: 260 seconds]
17:11 -!- jonatack_ [~jon@37.165.219.151] has quit [Quit: jonatack_]
17:11 -!- jonatack [~jon@213.152.180.5] has joined #joinmarket
17:38 -!- HackRelay [~jmrelayha@p5DE4A2C0.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
17:38 -!- DSRelBot [~DSRelBot@p5DE4A2C0.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
17:50 -!- DSRelBot [~DSRelBot@p5DE4A431.dip0.t-ipconnect.de] has joined #joinmarket
17:51 -!- HackRelay [~jmrelayha@p5DE4A431.dip0.t-ipconnect.de] has joined #joinmarket
17:56 < tlo1337> should i be putting an extended pubkey followed by a password or something? that seems like a lot though..
17:58 -!- jonatack [~jon@213.152.180.5] has quit [Ping timeout: 246 seconds]
18:59 < belcher_> tlo1337 the ssh password should be the same one you use to login normally(?)
19:47 < tlo1337> i thought my username would be "mynode" because that's the rpc username that i used to configure jm with as well, but it seems that it's "admin" which is what i normally use when ssh-ing into my node. i tried that instead in the command recently and i wasn't sure if it worked or not, but i think it did because now when i enter that command again i get back: bind [127.0.0.1]:8332: Address already in use
19:47 < tlo1337> channel_setup_fwd_listener_tcpip: cannot listen to port: 8332
19:47 < tlo1337> Could not request local forwarding.
19:58 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket
--- Log closed Fri May 08 00:00:19 2020