Multichain-Explorer RPC failed: ('http_protocol_error', 0, 'got a bad status line', None)

Question

Hello, i'm developing blockchain for my final project.
and i've kinda problem about multichain-explorer that I deployed on a server.

I've done any tutorial for multichain-explorer installation on https://github.com/MultiChain/multichain-explorer
But i have an error about RPC connection.
The status on multichain-explorer webpages shows 'No Connection' (red labeled)
and the bottom of the web shows an error '('http protocol error', 0, 'got a bad status line', None)'
The console also keep showing this error: 

RPC failed: ('http_protocol_error', 0, 'got a bad status line', None)
catch_up_rpc: abort
Opened /home/cryptnode/.multichain/chain1/blocks/blk00000.dat
203.189.120.14 - - [20/Aug/2018 08:15:22] "GET /MultiChain%20chain1/recent?random=0.54325423451574368 HTTP/1.1" 200 110
RPC failed: ('http_protocol_error', 0, 'got a bad status line', None)
catch_up_rpc: abort
Opened /home/cryptnode/.multichain/chain1/blocks/blk00000.dat
203.189.120.14 - - [20/Aug/2018 08:15:27] "GET /MultiChain%20chain1/recent?random=0.75434146783456789 HTTP/1.1" 200 110
RPC failed: ('http_protocol_error', 0, 'got a bad status line', None)
catch_up_rpc: abort
Opened /home/cryptnode/.multichain/chain1/blocks/blk00000.dat
203.189.120.14 - - [20/Aug/2018 08:15:32] "GET /MultiChain%20chain1/recent?random=0.2345346278964646 HTTP/1.1" 200 110
RPC failed: ('http_protocol_error', 0, 'got a bad status line', None)
catch_up_rpc: abort
Opened /home/cryptnode/.multichain/chain1/blocks/blk00000.dat
203.189.120.14 - - [20/Aug/2018 08:15:37] "GET /MultiChain%20chain1/recent?random=0.2351678468493025 HTTP/1.1" 200 110

Can someone help me, please ?
thanks alot.

Answer 1

There are many possible reasons why the RPC connection could be configured wrongly. Please ensure everything is set up in the Explorer configuration as documented.

Comments

i have proxy configured in my network. is that affect anything to the blockchain I created ?

---

It doesn't affect the blockchain node directly but if all traffic is routed through the proxy, this could affect the traffic content and its source IP address.