-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin-trustedcoin getblock error #14
Comments
It is this same error that caused the Lightning Network to go in panic for some hours: lightningnetwork/lnd#7002 Please update to the latest trustedcoin release, it is fixed there. |
when trying to update i am getting ERROR 404: Not Found. to be specific this is what it looks like |
Did you change the name fiatjaf to nbd-wtf is the command should be wget https://github.com/nbd-wtf/trustedcoin/releases/download/v 0.5.5/trustedcoin_linux_amd64 |
Ahhh I was getting the same error but I did not confirm that there was the
name change. I was sure I copied and pasted it but perhaps not. I will
try to update again.
…On Thu., Oct. 13, 2022, 4:24 a.m. Yilak, ***@***.***> wrote:
Did you change the name fiatjaf to nbd-wtf is the command should be wget
https://github.com/nbd-wtf/trustedcoin/releases/download/v
0.5.5/trustedcoin_linux_amd64
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO3CKYF3UHRU2VQ3JNISPJLWC7PL7ANCNFSM6AAAAAARC2NZMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Oops, thank you. Changed now. |
Hey just got home, Seen you made the change on your page and I gave it a try. Unfortunately still seeing a 404 Not Found Error. I exit and restart terminal to recreate the issue and got the same thing. Strange it appears to be on your assets page, I tried the last version and am getting the same error. I will keep looking if there is something wrong on my end. |
Take the URL from here and use it: https://github.com/nbd-wtf/trustedcoin/releases/tag/v0.5.6 |
Well my friend that definitely worked and then I received this message when starting lightningd ubuntu@lnbits:~/lnbits-legend$ lightningd |
I tried again with a fresh terminal and received the same message with an added line ubuntu@lnbits:~/lnbits-legend$ lightningd |
I think you have downloaded the wrong file. |
So, the instructions at the README have been updated. If you follow those now it should work. |
Sounds good I will try it this morning.
I did end up trying a brand new VM last night and got the same result.
Let's try this one.
Cheers
…On Sat., Oct. 15, 2022, 3:57 a.m. fiatjaf, ***@***.***> wrote:
So, the instructions at the README have been updated. If you follow those
now it should work.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO3CKYDQXXABSOQ6XIS4BO3WDJ5XFANCNFSM6AAAAAARC2NZMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
hello there, not to be a bother just trying to get this sorted on our end so our LNBits is working So we used your new README and seen right away that the chmod command did not have a matching file name to the wget command. In a new VM not our existing one, We still used the wget command and retrieved the file, it was Red and Not White in colour in our 'plugins ls' We then tried the chmod you have in README and got the error So we used the chmod command with the 'trustedcoin-v0.5.6-linux-arm64.tar.gz' file name and we turned the Red to Green in the 'plugins ls' cd out and started lightningd with this error now showing up with 'Unterminated quoted string' ubuntu@tap4sats:~$ lightningd I have time now that its the weekend to play with it more today. I am going to try using your past asset file names and see what happens. |
Sorry for wasting your time again. You had to untar the package downloaded. The instructions were missing one step. If you follow that now it should work. This time I did test them. Make sure to delete the previous trustedcoin binary you had. |
Well my friend, no luck on this end. tried from a brand new VM and everything works great right until we run lightningd. Here is the whole log for you to see. This time the error is here it is on our end, as you see I verified nothing was in the plugins ls as soon as I started ubuntu@tap4sats: trustedcoin-v0.5.6- 100%[===================>] 4.98M --.-KB/s in 0.1s 2022-10-15 20:58:00 (40.3 MB/s) - ‘trustedcoin-v0.5.6-linux-arm64.tar.gz’ saved [5224152/5224152] ubuntu@tap4sats: ubuntu@tap4sats: |
Please try again. I wrote |
I was going to ask about that when I seen 'arm' a few times on your assets page in your 'the releases page' my bad I should have asked when I first sere it a few days ago. There are a few on there with arm, |
The |
Oh I see, Well I just rtemoved what was in the plugins directory and changed those the wget and tar commands to amd64 and it looks like we are started and syncing. I will let you know if all goes good when it fully syncs, cheers and I thank you for your help. Much appreciated |
Hello all, thanks for the plugin we have been using it with our LNBits server for months now. Just recently it keeps on shutting down on us. We went into our terminal again to start lightningd again and we now see this error as it tries to return blocks
plugin-trustedcoin getblock error: readScript: script witness item is larger than the max allowed size [count 33970, max 11000]
any thoughts to help out would be much appreciated
The text was updated successfully, but these errors were encountered: