Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter muslimcodeid

    (@muslimcodeid)

    Hi Support,

    Finally I managed to solve this issue.
    with change the rcpbind ip with my btc core node server IP.
    fyi,i also already change the rpc password

    Thanks for your help in advance

    Thread Starter muslimcodeid

    (@muslimcodeid)

    Hi Support,

    Thanks for your reply.

    What you explained above i totally agree and its same like my analysis.
    I already make sure that from my webhosting,outgoing connection to 8332 is open but now i am still waiting an answer from my vps (btc core server) porivder to check whether they block this port or not,because from the vps firewall itself i already allow or open the port 8332(8333 also).

    here my bitcoin.conf,look like

    server=1
    rpcallowip=127.0.0.1/8
    rpcallowip=198.54.114.yyy/24
    rpcport=8332
    rpcbind=127.0.0.1
    rpcbind=198.54.114.yyy
    walletnotify=curl -s https://cryptominer-shop.com/wallets/api3/notify/BTC/wallet/%s >/dev/null
    blocknotify=curl -s https://cryptominer-shop.com/wallets/api3/notify/BTC/block/%s >/dev/null
    rpcauth=rpcuser:50c2cf373adbef15efe6eddf7a8b0f89$a1c5dd66dad3515ac074c5599da93db9ac19cfa0cdf40a665ea286547cd92126

    there is one thing thats make me confuse,if you can see above(netstat result)
    there is port 8332 and 8333 open,but if i put 8332 as rpcport on my bitcoin.conf, i able to telnet port 8333 but not 8332, but if i put rpcport:8333 i am not able to ping both of the port

    any advice

    Thanks in advance

Viewing 2 replies - 1 through 2 (of 2 total)