Title: Help setting up JSON with PHP - 0.1 reward! Post by: joeyjoe on August 22, 2011, 11:17:10 PM Im trying to use the daemon running on my pc with PHP on my webserver.
I have setup the config file to what i think it needs to be, and added some sample php code to connect to my pc with the correct username and password. I have configured port forwarding to forward the entire 8330 - 8339 range to my pc. I have tested the port using an online scanner and it is open. But when i run the sample code, i get no connection. The error when i load the php file is: Quote Fatal error: Uncaught exception 'Exception' with message 'Incorrect response id (request id: 1, response id: )' in /home/joeyjoec/public_html/bitcoinpaypal/jsonRPCClient.php:152 Stack trace: #0 [internal function]: jsonRPCClient->__call('getinfo', Array) #1 /home/joeyjoec/public_html/bitcoinpaypal/index.php(7): jsonRPCClient->getinfo() #2 {main} thrown in /home/joeyjoec/public_html/bitcoinpaypal/jsonRPCClient.php on line 152 my config file is: Quote # bitcoin.conf configuration file. Lines beginning with # are comments. # Network-related settings: # Run on the test network instead of the real bitcoin network. #testnet=1 # Connect via a socks4 proxy #proxy=127.0.0.1:9050 # Use as many addnode= settings as you like to connect to specific peers #addnode=69.164.218.197 #addnode=10.0.0.2:8333 # … or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333 # Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to # find other peers. #noirc=1 # Maximum number of inbound+outbound connections. #maxconnections= # JSON-RPC options (for controlling a running Bitcoin/bitcoind process) # server=1 tells Bitcoin to accept JSON-RPC commands. server=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=joeyjoe rpcpassword=securepassword # How many seconds bitcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. rpctimeout=30 # By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): rpcallowip=109.75.171.120 rpcallowip=127.0.0.1 # Listen for RPC connections on this TCP port: rpcport=8332 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind # running on another host using this option: rpcconnect=127.0.0.1 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate # with Bitcoin -server or bitcoind #rpcssl=1 # OpenSSL settings used when rpcssl=1 rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH rpcsslcertificatechainfile=server.cert rpcsslprivatekeyfile=server.pem # Miscellaneous options # Set gen=1 to attempt to generate bitcoins gen=0 # Use SSE instructions to try to generate bitcoins faster. For muliple core processors. #4way=1 # Pre-generate this many public/private key pairs, so wallet backups will be valid for # both prior transactions and several dozen future transactions. keypool=100 # Pay an optional transaction fee every time you send bitcoins. Transactions with fees # are more likely than free transactions to be included in generated blocks, so may # be validated sooner. paytxfee=0.00 # Allow direct connections for the ‘pay via IP address’ feature. #allowreceivebyip=1 # User interface options # Start Bitcoin minimized #min=1 # Minimize to the system tray #minimizetotray=1 0.1 bitcoin to who ever gets this working for me |