elective-stereophonic
elective-stereophonic
Could not verify signature (server side) singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Author Topic: Could not verify signature (server side)  (Read 1184 times)

Tosch110

  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Could not verify signature (server side)
« on: November 11, 2015, 03:33:50 pm »

When trying out using dividends in the SuperNET-Lite Client, the error "Could not verify signature (server side)." seems to be a bug I cannot solve right now because I am not exactly sure why I get the error:

errorCode: 1
errorDescription: "Could not verify signature (server side).

Anybody an idea what the reason might be to get this error? Thanks in advance!

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: Could not verify signature (server side)
« Reply #1 on: November 11, 2015, 04:57:15 pm »

While the return mentions "server side" that error actually occurs in the client.
Best to watch the network console in chrome developer tools to see the 'real' server response.
Most probably a case where the client sends transaction data as for instance an Integer to the server but the server gives back a String on which it then chokes.

If you run your own server locally that section is normally by-passed in the client.
Logged
HEAT: DEX | SDK | HOME

Tosch110

  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Re: Could not verify signature (server side)
« Reply #2 on: November 11, 2015, 11:47:32 pm »

While the return mentions "server side" that error actually occurs in the client.
Best to watch the network console in chrome developer tools to see the 'real' server response.
Most probably a case where the client sends transaction data as for instance an Integer to the server but the server gives back a String on which it then chokes.

If you run your own server locally that section is normally by-passed in the client.

I am running my own server locally...
 

elective-stereophonic
elective-stereophonic
assembly
assembly