AgoraLive (OP)
|
|
February 22, 2015, 12:29:22 PM |
|
I have a script which is working when I access the bitcoin-qt.exe from localhost. I have allowrpc= set to the external server but for some reason it is not working?
The same script is running with a few ALTCoins without any issues, so it is not an IP, script error (as far as I know)?
Any ideas? Oh the script is php, is that's and issue...
|
|
|
|
|
|
The Bitcoin network protocol was designed to be extremely flexible. It can be used to create timed transactions, escrow transactions, multi-signature transactions, etc. The current features of the client only hint at what will be possible in the future.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
Pieter Wuille
Legendary
Offline
Activity: 1072
Merit: 1174
|
|
February 22, 2015, 05:20:50 PM |
|
Hard to say without seeing the script...
|
I do Bitcoin stuff.
|
|
|
AgoraLive (OP)
|
|
February 23, 2015, 06:13:01 PM |
|
Well require_once 'jsonRPCClient.php'; $bitcoin = new jsonRPCClient(' http://user:password@127.0.0.1:8332/'); echo "<pre>\n"; print_r($bitcoin->getinfo()); echo "</pre>"; Now this runs perfect localhost, but dosen't work when I run from external server. YES I have rpcallowip=xxx.xxx.xxx.xxx set correct because other coins are working from external source.
|
|
|
|
Bitware
|
|
February 24, 2015, 04:52:21 AM |
|
Look at router and firewall settings.
|
|
|
|
gmaxwell
Staff
Legendary
Offline
Activity: 4172
Merit: 8419
|
|
February 24, 2015, 05:59:33 AM |
|
YES I have rpcallowip=xxx.xxx.xxx.xxx set correct because other coins are working from external source.
You probably don't. Read your debug.log.
|
|
|
|
AgoraLive (OP)
|
|
February 24, 2015, 07:19:14 PM |
|
Look at router and firewall settings.
Why should this be an issue with bitcoin, when litecoin and doge is running perfect with same script? Other ports naturally, but script is identical
|
|
|
|
AgoraLive (OP)
|
|
February 24, 2015, 07:20:35 PM |
|
YES I have rpcallowip=xxx.xxx.xxx.xxx set correct because other coins are working from external source.
You probably don't. Read your debug.log. What should I be looking for?
|
|
|
|
cassini
Member
Offline
Activity: 112
Merit: 10
|
|
February 25, 2015, 12:02:11 AM |
|
You probably don't. Read your debug.log.
What should I be looking for? Any line that contains "RPC". Unfortunately not all types of RPC errors show up in debug.log, though. First of all try curl locally on the same machine you run bitcoin-qt to get more detailed error messages (some Linux distros and Mac OS contain curl already, otherwise download from http://curl.haxx.se/). curl --data-binary '{"jsonrpc": "1.0", "id":"mycurltest", "method": "getinfo", "params": [] }' -u <yourRPCusername>:<yourRPCpassword> 127.0.0.1:8332 BTW, what does your bitcoin.conf look like?
|
|
|
|
AgoraLive (OP)
|
|
February 25, 2015, 07:25:18 PM |
|
rpcuser=username rpcpassword=password rpcallowip=::/0 rpcport=8332 server=1
rpcallowip=::/0 - ONLY TO OPEN ALL FOR TESTING....
Even with specific IP it dosen't work (Again other coins does NOT have issues)
|
|
|
|
cr1776
Legendary
Offline
Activity: 4032
Merit: 1301
|
|
February 25, 2015, 08:08:07 PM |
|
Are you sure this format is correct? It does not look good to me: rpcallowip=::/0 You could try something like: rpcallowip=* or (for better security), something like if you are testing it from your LAN: 192.168.0.0/24 (depending on the addresses). Or you could just whitelist your IP. What did curl show - as cassini suggested above? rpcuser=username rpcpassword=password rpcallowip=::/0 rpcport=8332 server=1
rpcallowip=::/0 - ONLY TO OPEN ALL FOR TESTING....
Even with specific IP it dosen't work (Again other coins does NOT have issues)
|
|
|
|
AgoraLive (OP)
|
|
February 25, 2015, 08:18:50 PM |
|
Are you sure this format is correct? It does not look good to me: rpcallowip=::/0 You could try something like: rpcallowip=* or (for better security), something like if you are testing it from your LAN: 192.168.0.0/24 (depending on the addresses). Or you could just whitelist your IP. What did curl show - as cassini suggested above? rpcuser=username rpcpassword=password rpcallowip=::/0 rpcport=8332 server=1
rpcallowip=::/0 - ONLY TO OPEN ALL FOR TESTING....
Even with specific IP it dosen't work (Again other coins does NOT have issues)
according to the bitcoin changelog (v 0.10.0) then ip:* is no longer supported and should be ::/0 Accessing from localhost is not a problem I have not tried CURL yet
|
|
|
|
AgoraLive (OP)
|
|
February 25, 2015, 08:28:26 PM |
|
Might not understand curl but:
curl: (6) Could not resolve host: 1.0, curl: (6) Could not resolve host: id curl: (6) Could not resolve host: method curl: (6) Could not resolve host: getinfo, curl: (6) Could not resolve host: params curl: (3) [globbing] bad range specification in column 2 curl: (3) [globbing] unmatched close brace/bracket in column 1 {"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
|
|
|
|
AgoraLive (OP)
|
|
February 25, 2015, 08:44:47 PM |
|
OH GOD SO STUPID!!!!!!!!!! I forgot to open the port BITWARE <---- THANK YOU
|
|
|
|
cr1776
Legendary
Offline
Activity: 4032
Merit: 1301
|
|
February 25, 2015, 09:16:47 PM |
|
OH GOD SO STUPID!!!!!!!!!! I forgot to open the port BITWARE <---- THANK YOUGlad you got it! (Didn't know if you were running 0.9.x or 0.10.0)
|
|
|
|
Bitware
|
|
February 26, 2015, 02:09:03 PM |
|
OH GOD SO STUPID!!!!!!!!!! I forgot to open the port BITWARE <---- THANK YOUYou are most welcome.
|
|
|
|
|