BTC Address Generation Not Functional about workbench HOT 10 CLOSED

Closed via https://github.com/rubykube/peatio/issues/1182

from workbench.

@jdowning100 I'm having this issue with Peatio 1-8-stable, all daemons seem to be working, and I can create an address with jsonrpc. Still Peatio is not showing the generated addresses, nor showing any error on the logs.

$ god status
amqp:deposit_coin: up
amqp:deposit_coin_address: up
amqp:market_ticker: up
amqp:matching: up
amqp:order_processor: up
amqp:pusher_market: up
amqp:pusher_member: up
amqp:slave_book: up
amqp:trade_executor: up
amqp:withdraw_coin: up
coins: up
global_state: up
hot_wallets: up
k: up
payment_transaction: up
websocket_api: up
withdraw_audit: up

$ curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnewaddress", "params": [] }' -H 'content-type: text/plain;' http://user:password@localhost:8332
{"result":"37q6EnJdWg7jWFhJQdg4YGoxbWnm4CTqKM","error":null,"id":"curltest"}

from workbench.

By the way, would this issue have to do with whether URL_SCHEME and FORCE_SECURE_CONNECTION are https and 'true' respectively in config/application.yml? Where can I see if the bitcoin daemon is receiving those jsonrpc requests?

from workbench.

Hi !, I installed this code,

I Can Solved your Questions, The problem with bitcoin is, cause the rpc no allow your docker IP, then, you need add the IP to the bitcoin.conf,

example:

printtoconsole=1

server=1
listen=1
daemon=1

rpcallowip=172.18.0.255/0
rpcuser=admin
rpcpassword=changeme

@rraallvv
@jdowning100

from workbench.

@Joan1590 Thanks. Although in my case I think that's not what causes the problem, I can get a new address using curl, both, with BTC and also with ETH via JSONRPC.

from workbench.

@rraallvv the IP for docker is different that your VPS or your Server, you can see the docker log, with that command "docker logs workbench_deposit_coin_address_1"
i see the error 403 in there, I guess that is.

from workbench.

Can you check if the request was made via HTTPS?

I'm suspecting the 403 responce has to do with option config.force_ssl in config/environments/production.rb and the environment var FORCE_SECURE_CONNECTION because in my case it's working with RAILS_ENV=development

from workbench.

The request was made via http, not https

from workbench.

Hmm... thanks, I'll take a closer look to the logs then. I was enable to enable the logger for production too.

from workbench.

Having the same problem. Have you guys solved this??

from workbench.