Closed TheZLabs closed 1 year ago
solution found here https://t.me/PiNodechat
Follow this And now you have officially flagged your account
why?
should not be messing with config files this was reiterated by CT
So because I changed my config file to make it work, my account would be flagged? Not sure I understand that. Maybe CT should respond to one of the many many related Open tickets? They won’t do that but they’ll flag my account? 🤔On Wed, Jan 4, 2023 at 6:24 PM chipmoon27 @.***> wrote: should not be messing with config files this was reiterated by CT
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
So because I changed my config file to make it work, my account would be flagged? Not sure I understand that. Maybe CT should respond to one of the many many related Open tickets? They won’t do that but they’ll flag my account? 🤔On Wed, Jan 4, 2023 at 6:24 PM chipmoon27 @.> wrote: should not be messing with config files this was reiterated by CT —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
Fwiw, I totally agree. The CT is out of touch with the reality of the node glitches. My HD crashed but I managed to rescue most all the files from the pi folders. I updated win10 on an old gen 2 i5 laptop, installed pi with a fresh login but copied all my existing files over to new hd, loaded up docker and got nothing but a spinning circle “waiting a minute” to load but never did. After leaving it over night I shutdown, found same info as what you posted about the json file on another site, made the edits, rebooted and bingo, node is back up and actually running much better now. It’s up to date with the blocks where as before the hd crash, it was usually always catching up.
So because I changed my config file to make it work, my account would be flagged? Not sure I understand that. Maybe CT should respond to one of the many many related Open tickets? They won’t do that but they’ll flag my account? 🤔On Wed, Jan 4, 2023 at 6:24 PM chipmoon27 @.**> wrote: should not be messing with config files this was reiterated by CT —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.**>
Fwiw, I totally agree. The CT is out of touch with the reality of the node glitches. My HD crashed but I managed to rescue most all the files from the pi folders. I updated win10 on an old gen 2 i5 laptop, installed pi with a fresh login but copied all my existing files over to new hd, loaded up docker and got nothing but a spinning circle “waiting a minute” to load but never did. After leaving it over night I shutdown, found same info as what you posted about the json file on another site, made the edits, rebooted and bingo, node is back up and actually running much better now. It’s up to date with the blocks where as before the hd crash, it was usually always catching up.
So you followed the same steps in changing the user-preferences.json file and also had it work? I'm honestly not sure why this isn't a documented fix being relayed by CT to node users having issues. I get that it's a test net but we all want to see how it works too lol.
this can be wrongly used and is not accepted to post on here, you should remove post as it will do more harm than good.
what happens when you break the operators json how will you fix it?
Ya, same “corrections” in the json. Had to dig through some searches and found it in a foreign language post somewhere. First time failed but then found followup post with the “horizon” part and it seemed that did the trick.
All ports are verified open to the outside for inbound connections via YouGetSignal, port check fails. Node does not connect. Says it may take up to one minute. Container does not download. Certificate errors all through the log.
Looks like there are other issues with the setup too: