V0.5.3ppc-beta internal server error


#1

Hello,

Today I upgraded to Peercoin-QT v0.5.3ppc-beta

When i initiate RPC request I’m getting 500 Internal Server Error
This worked on older version and is working on 7 other coin wallets.
Wallet is connected on nodes and is up to date.

Advice?


#2

[quote=“Crypto-Games, post:1, topic:3871”]Hello,

Today I upgraded to Peercoin-QT v0.5.3ppc-beta

When i initiate RPC request I’m getting 500 Internal Server Error
This worked on older version and is working on 7 other coin wallets.
Wallet is connected on nodes and is up to date.

Advice?[/quote]

Hi, I need more information. How are you running the daemon? Which OS are you using and your ppcoin.conf file.


#3

Windows server 2012 R2 standard

deamon=1
server=1
rpcallowip=ourIP
rpcport=OURPORT1
port=OURPORT2
rpcthreads=100
rpcuser=ppcoinrpc
rpcpassword=OURpassword
noirc=1
rpctimeout=30


#4

you mistyped “daemon”

do you see the process running in the task manager?
I assume you don’t.
After correcting the mistyping, you should see it running.


#5

[quote=“Crypto-Games, post:3, topic:3871”]Windows server 2012 R2 standard

deamon=1
server=1
rpcallowip=ourIP
rpcport=OURPORT1
port=OURPORT2
rpcthreads=100
rpcuser=ppcoinrpc
rpcpassword=OURpassword
noirc=1
rpctimeout=30[/quote]

You can remove “deamon” line all together. That is not needed. “server=1” is what allows you to use RPC with QT client.


#6

removed daemon=1
Process is visible in task manager, but error is the same


#7

You should provide us more info.

“500 Internal Server Error” is an http error code https://en.wikipedia.org/wiki/List_of_HTTP_status_codes.
So that is not coming from the RPC server.

It seems that you are using some kind of http proxy.
Are you sure that one connects to the correct rpc port?
What happens if you telnet the rpc port?


#8

what does getinfo and getpeerinfo in console return

it’s possible that you have to redownload the blockchain, i used to get similar error as well when upgrading late.


#9

Ok solved it.
Uninstalled, deleted AppData\Roaming\PPCoin folder and synced again.

Thanks for helping!


#10

Having the same issues again. It was working for a week, not it’s not

Uninstalled/installed, download whole blockchain again. Wallet is synced.

Wallet is getting error: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers of the issue. (code -2)

{ "version" : "v0.5.3ppc-beta", "protocolversion" : 60006, "walletversion" : 60000, "balance" : x, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 234653, "moneysupply" : 23142447.64406600, "connections" : 8, "proxy" : "", "ip" : "MYIP", "difficulty" : 405306951.90868342, "testnet" : false, "keypoololdest" : 1458557576, "keypoolsize" : 101, "paytxfee" : 0.00000000, "errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers of the issue." }

getpeerinfo:

[ { "addr" : "178.32.217.85:9901", "services" : "00000001", "lastsend" : 1462194539, "lastrecv" : 1462194510, "conntime" : 1462194508, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.0/Peerunity:0.2.1(v0.2.1)/", "inbound" : false, "releasetime" : 0, "height" : 234653, "banscore" : 0 }, { "addr" : "104.197.72.254:9901", "services" : "00000001", "lastsend" : 1462194662, "lastrecv" : 1462194511, "conntime" : 1462194509, "version" : 60004, "subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.2(v0.1.2-RC3-14-gd0cbc83-dirty)/", "inbound" : false, "releasetime" : 0, "height" : 233911, "banscore" : 0 }, { "addr" : "93.113.101.229:9901", "services" : "00000001", "lastsend" : 1462194515, "lastrecv" : 1462194531, "conntime" : 1462194515, "version" : 60004, "subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.3(v0.1.3-RC1-2-gb53729b)/", "inbound" : false, "releasetime" : 0, "height" : 233911, "banscore" : 0 }, { "addr" : "98.208.92.222:9901", "services" : "00000001", "lastsend" : 1462194662, "lastrecv" : 1462194538, "conntime" : 1462194516, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.0/Peerunity:0.2.0(v0.2.0)/", "inbound" : false, "releasetime" : 0, "height" : 234653, "banscore" : 0 }, { "addr" : "85.25.207.141:9901", "services" : "00000001", "lastsend" : 1462194726, "lastrecv" : 1462194726, "conntime" : 1462194516, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 234666, "banscore" : 0 }, { "addr" : "178.254.40.41:9901", "services" : "00000001", "lastsend" : 1462194562, "lastrecv" : 1462194662, "conntime" : 1462194523, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.0/Peerunity:0.2.0(v0.2.0)/", "inbound" : false, "releasetime" : 0, "height" : 234666, "banscore" : 0 }, { "addr" : "163.172.19.96:9901", "services" : "00000001", "lastsend" : 1462194527, "lastrecv" : 1462194544, "conntime" : 1462194523, "version" : 60005, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.1(v0.5.1ppc.rc2-beta)/", "inbound" : false, "releasetime" : 0, "height" : 226462, "banscore" : 0 }, { "addr" : "98.194.236.177:9901", "services" : "00000001", "lastsend" : 1462194536, "lastrecv" : 1462194537, "conntime" : 1462194535, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.2(v0.5.2ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 234653, "banscore" : 0 } ]

repairwallet returns same thing:

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers of the issue. (code -2)

actually everything i try, returns this error…


#11

You have these issues due to bad connectivity to other nodes on the correct chain. Network connectivity will improve as more nodes update their software and get on the correct chain. On https://bitinfocharts.com/ppcoin/nodes-active/ you can get IP addresses for Peercoin 0.5.3 and Peerunity 0.2.1 nodes. Add ten of them to ppcoin.conf, with addnode= in front of the IP, to get good network connectivity. Now delete the local blockchain before you start the client. After this you should not have any issues.


#12

Thank you, this solved it!


#13

After few days, problems are again here.

Syncying stopped at 234612

getpeerinfo:

[ { "addr" : "176.9.16.102:9901", "services" : "00000001", "lastsend" : 1462460536, "lastrecv" : 1462460529, "conntime" : 1462460229, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "176.9.50.227:9901", "services" : "00000001", "lastsend" : 1462460437, "lastrecv" : 1462460529, "conntime" : 1462460229, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "82.192.64.136:9901", "services" : "00000001", "lastsend" : 1462460841, "lastrecv" : 1462460529, "conntime" : 1462460229, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "85.25.207.141:9901", "services" : "00000001", "lastsend" : 1462460841, "lastrecv" : 1462460623, "conntime" : 1462460230, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "85.25.217.233:9901", "services" : "00000001", "lastsend" : 1462460235, "lastrecv" : 1462460531, "conntime" : 1462460230, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.2(v0.5.2ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "212.83.172.152:9901", "services" : "00000001", "lastsend" : 1462460537, "lastrecv" : 1462460841, "conntime" : 1462460231, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-10-g69b31e4-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "62.210.110.211:9901", "services" : "00000001", "lastsend" : 1462460260, "lastrecv" : 1462460672, "conntime" : 1462460232, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 }, { "addr" : "107.170.43.92:9901", "services" : "00000001", "lastsend" : 1462460500, "lastrecv" : 1462460535, "conntime" : 1462460235, "version" : 60006, "subver" : "/Satoshi:0.6.3/Peercoin:0.5.3(v0.5.3ppc-beta)/", "inbound" : false, "releasetime" : 0, "height" : 235187, "banscore" : 0 } ]

getinfo

{
"version" : "v0.5.3ppc-beta",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : x,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 234612,
"moneysupply" : 23142153.03457200,
"connections" : 8,
"proxy" : "",
"ip" : "xxxx",
"difficulty" : 405306951.90868342,
"testnet" : false,
"keypoololdest" : 1458642216,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
}[/code]


config file:
[code]server=1
rpcallowip=ourip
rpcport=ourport
port=ourport
rpcthreads=100
rpcuser=ppcoinrpc
rpcpassword=somepassword
noirc=1
rpctimeout=30
addnode=176.9.16.102
addnode=176.9.50.227
addnode=85.25.207.141
addnode=85.25.217.233
addnode=82.192.64.136
addnode=212.83.172.152
addnode=62.210.110.211
addnode=107.170.43.92
addnode=107.170.209.76
addnode=192.95.56.199
addnode=95.154.69.211
addnode=94.143.245.5

repairwallet

{ "wallet check passed" : true }

Downloaded whole blockchain again, still stucked.

This beta wallet is giving us a lot of issues, please fix asap


#14

all currently available windows builds have this problem with syncing past block 234612, the only workaround today is to run 64bit linux or macosx version or compile from source on windows.

i’ll try to set up windows build machine tomorrow.


#15

[quote=“backpacker69, post:14, topic:3871”]all currently available windows builds have this problem with syncing past block 234612, the only workaround today is to run 64bit linux or macosx version or compile from source on windows.

i’ll try to set up windows build machine tomorrow.[/quote]
any update?


#16

https://rbfi.io/dl.php?key=/Sdph/ppcoind.zip
sha1 checksum 6eb16dde0ed2f30944e550f453bb297ecc577790

that should work for you, if you are using command line version.

and here’s the ppcoin-qt:

https://rbfi.io/dl.php?key=/Qlwa/ppcoin-qt.zip

sha256 7942747e8d301d4d0ad72e6e3eca7f96b265898ecbb28be16ea6027fc29f2436


#17

[quote=“backpacker69, post:16, topic:3871”]https://rbfi.io/dl.php?key=/Sdph/ppcoind.zip
sha1 checksum 6eb16dde0ed2f30944e550f453bb297ecc577790

that should work for you, if you are using command line version.

and here’s the ppcoin-qt:

https://rbfi.io/dl.php?key=/Qlwa/ppcoin-qt.zip

sha256 7942747e8d301d4d0ad72e6e3eca7f96b265898ecbb28be16ea6027fc29f2436[/quote]
We’ll not risk with this sollution and we’ll wait till final wallet fix.
If this will not be fixed soon, we’ll be forced to remove peercoin from our supported coins.


#18

does peerunity version 0.2.2 work for you?


#19

no, it has to be qt


#20

https://sourceforge.net/projects/ppcoin/files/0.5.4/ppcoin-0.5.4-win32-setup.exe/download