You are viewing a single comment's thread from:
RE: NEM-tools: Automated restart of delegated harvesting
Great tool! Unfortunately, I put the wrong email address (typo) and can't register the same key for the correct email address. Any solution? Tnx!
it seems like there are all subscriptions confirmed. so the owner of the e-mail address you provided confirmed your request. this confuses me a bit :D ... I would have expected that your subscription could never have been confirmed if you put in the wrong e-mail address
can you give me your delegated public key or delegated address? then I can manually delete your subscription
Strange! I subscribed by ...@gmai.com. So far I haven't received any confirmation email.
Public Key: 28ef041e4a723de74b82d892b7e9c581e3604c61eb6f910a4e83e78b3428ff4f
Thanks!
well it seems like there is no record in the database for this address. can you try to register again and tell me whether it worked?
using the delegated public key you stated above should work
It's working now! I already got a notification that harvesting was restarted. However, there might be a problem with the confirmation email:
https://nem-services.herokuapp.com/
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sun Jan 07 22:04:48 UTC 2018
There was an unexpected error (type=Internal Server Error, status=500).
No message available
well I see some error messages in the logs. did you click multiple times on the link to confirm the subscription?
the 2nd time you click on the confirmation-link there will be an error because the token isn't valid any longer.
yes there is no error mapping implemented as I didn't expect it to be necessary.
I will think about giving the user a better feedback if he/she has already confirmed the mail address
I think that I have the last question :). So when I open the web wallet I see status INACTIVE. I know that there is a warning that this status might not represent the actual status, so the question is how to check the reality? I use HW wallet to log-in, if that depends. I found out that if I log-out and then log-in right after the status already change to INACTIVE.
it seems like there is some small bug in the nanowallet regarding this topic:
https://github.com/NemProject/NanoWallet/issues/395
but you should also make sure, that you put in the node which you received via mail for checking about your status ;-)