16:44:29 <gingeropolous> hrm, perhaps change "refresh" to "scan"
16:46:14 <selsta> where exactly?
18:38:25 <gingeropolous> dunno. just thought the wordage might help the whole "ermargerd i sync the blockchain twice"
18:38:53 <gingeropolous> maybe ppl will understanding "scan" better than "refresh"
18:43:51 <moneromooo> Or "Oops, download the correct chain this time".
18:44:58 <selsta> the GUI does not use the word refresh
20:01:04 <gingeropolous> i should use the gui more.
20:46:08 <monerobull[m]> What's the "failed to get hight" error?
20:46:20 <monerobull[m]> when sending (all)
20:46:32 <monerobull[m]> i fixed it by sending about half to the same wallet first, waiting 20 min and sending again xD
20:46:52 <selsta> which wallet mode are you using?
20:49:56 <monerobull[m]> advanced
20:50:02 <monerobull[m]> with my ownremote node
20:50:05 <monerobull[m]>  * with my own remote node
20:50:23 <selsta> is the remote node updated?
20:50:26 <monerobull[m]> trying to consolidate too many outputs on restricted rpc?
20:50:34 <monerobull[m]> selsta: of course
20:51:09 <selsta> yes there is a limit with restricted rpc, but the error is weird
20:51:15 <selsta> can you make a screenshot next time?
20:52:01 <monerobull[m]> sure but thats all it said
20:52:11 <monerobull[m]> maybe "correct hight" but not sure
20:52:17 <monerobull[m]> using a ledger btw
21:00:10 <selsta> did it happen multiple times?
21:02:01 <monerobull[m]> yeah
21:02:33 <monerobull[m]> send (all) to my own wallet -> continue on ledger -> loads quite a bit -> fails
21:03:24 <selsta> daemon logs are probably required to find out why it fails
21:03:52 <selsta> moneromooo: any idea why m_node_rpc_proxy.get_height(height) can fail?
21:04:30 <monerobull[m]> my node seems kinda fucked too
21:04:30 * monerobull[m] uploaded an image: (20KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/RTTYXhVHwoLPHBjwNFZKIkrb/grafik.png >
21:05:59 <selsta> does starting with `DNS_PUBLIC="tcp://9.9.9.9" ./monerod`
21:06:07 <selsta> make the DNS issues go away?
21:07:08 <gonbatfire[m]> Hello! If I enable P2Pool mining on GUI, will it keep mining in the background whenever I boot my PC?
21:07:08 <gonbatfire[m]> Or do I need open GUI each time I start my PC
21:07:35 <monerobull[m]> selsta: ill try that tomorrow
21:07:48 <selsta> gonbatfire[m]: it will not start automatically when booting your PC
21:09:21 <gonbatfire[m]> Oh, I was hoping to keep it simple for my GF getting into mining haha
21:09:42 <moneromooo> Well, it accesses network. So all networky reasons apply.
21:11:07 <gonbatfire[m]> Could I set GUI as a service that runs in the background? In windows
21:11:12 <moneromooo> Apart from that, mismatched versions, bad port, peer is busy till you time out...
21:13:02 <selsta> monerobull[m]: hmm, since the ledger will take a while to construct the transaction it might have timed out
21:13:37 <monerobull[m]> selsta: how much time does it have?
21:13:45 <selsta> how long did it take until that error showed up?
21:14:10 <selsta> gonbatfire[m]: there is no service for it currently, using dedicated mining software might make more sense
21:15:16 <monerobull[m]> selsta: definitely a few minutes
21:15:49 <gonbatfire[m]> selsta: Okay! Good ol' xmrig it is then
21:15:58 <gonbatfire[m]> * Okay! Good ol' xmrig it is then, thanks
21:15:59 <monerobull[m]> it has to be something about too many inputs. had something similar with my p2pool wallet but that was without ledger
21:17:36 <selsta> yes, it likely took too long to construct that tx and some timeout was reached. and with the p2pool wallet you requested too many outs for a restricted node
21:17:41 <selsta> that would be my guess currently
21:18:39 <monerobull[m]> yeah makes sense. im kind of a poweruser so should affect 99%
21:18:48 <monerobull[m]> s/should/shouldnt/