I put a note in helpdesk and tech in telegram for several days but believe this is a real issue. I mentioned the other day when I downloaded the nanowallet version 2.0.14, I could no longer harvest my local node. I tried everything. I just updated my nis to 95. Everything runs fine on the nis. I can run all postman and nodejs code against it. But when opening the new nanowallet and set the node to my local IP the system waits a few minutes and reassigns the node outside my network. When running delegated and entering my local node it says “error unlocking account, invalid protocol.” Because everything worked before the nanowallet upgrade, and it has the same symptoms on new nis I believe there is a bug in the nanowallet. Where to I submit a bug report, or does someone have an answer? This is a serious issue for my project development because I am working on security items and want to call my local nis for all endpoints on my network separating my application from the internet except via the local nis.
@BloodyRookie This (“error unlocking account, invalid protocol”) is error from NIS? If you know this error, how to fix this?
no, looks more like a Nano Wallet problem to me.
@Quantum_Mechanics do you know what is the reason?
Error message looks like this:
“Error at unlocking account, reason: invalid protocol : undefined”
I can start harvesting by setting the harvest node to my external internet IP address. The nis starts harvesting. But if I try to set my node to my external IP the same problem shows, it gives the error then assigns the node to an external node on the list.
well that looks like your NIS is not set up correctly or some firewall is blocking something. Hard to tell.
We tested with me harvesting via NCC on his node and it works, so it must be a Nano Wallet issue i guess.
Turns out is was a windows update problem. Windows removed IV6 from the NIS computer for some reason which took it off the LAN. Need to reconfigure the network and re expose NIS to the LAN.
Turns out not a solution. I have the computers on the network and I can communicate through external IP from machine to machine but when using local LAN the wallet cannot see the NIS and gives the error. I know the network is open because I can run all postman requests on my client and it pulls the server via the local IP.