> Daemon: allow socks5 proxy configuration with –proxy flag (#7326, #7616)

OMG <3

ty peeps

oh jeese... my spam :P

Baaan

I'm having trouble getting monerod to sync. What do I need to provide to help troubleshoot? I'm currently ~3900 blocks away.

remanifest: Can you describe the problem?

(Maybe there'll be an answer by the time I get back from a walk.)

apotheon: I launch monerod, and it binds to the localhost's TOR at 127.0.0.1:18081. Next, I see a bunch of messages about new top block candidates (Sync data returned a new top block candidate: 2506696 -> 2510647 [Your node is 3951 blocks (5.5 days) behind]). In the middle of that, I'm seeing various hosts are blocked. However, the node appears to not sync.

After some time, I see something like this: There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack, or your computer's time is off. Or it could be just sheer bad luck.

hm, no idea, then

hopefully someone else has some useful input

is monero network slow right now? trying to sync daemon and its taking forever

hmm

Maybe this is the same problem remanifest is having.

ive been syncing to HDD so I know that's generally going to be slow, but the rate has substantially changed over the course of the past 2 days

basically went 7,6,5,4,3,2 days to completion, im now on the last 4% (3 months behind) and it all of a sudden jumped up to 6 days last night and has been crawling since

. . . or maybe Guest57 just got to the part where the updates slow down because there aren't any more . . . err, checkpoints, or whatever they're called.

The term slipped my mind.

pre-computed block verification points

maybe -- thought they would have been spread homogenously throughout the process, but maybe they're stacked up in the last 4%

im new to monero obviously, since im downloading the whole blockchain

oh he left

update to the just released 0.17.3.0

should have new checkpoints

I just tried with v0.17.3.0-release, same issue for me.

remanifest: have you specified tor socks5 proxy connection details correctly?