Bitcoin Forum
November 10, 2024, 05:14:57 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [iquidus Explorer] Not connect. Help  (Read 2055 times)
dockingtriple (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 05, 2015, 09:18:14 AM
 #1

Just compiled iquidus/explorer, but can't connect to chain.

Check console for errors: Blocks
Check console for error: Connections.

Coin Daemon work properly and sync.

Just changed this is setting.json: (with same info stored in daemon .conf file launched with listen=1 server=1 daemon=1 rpcuser= password= and port= ).

  // wallet settings
  "wallet": {
    "host": "localhost",
    "port": 9332,
    "user": "darkcoinrpc",
    "pass": "123gfjk3R3pCCVjHtbRde2s5kzdf233sa"
  },


Is there any other parameters needed to change to connect to daemon chain?

Everything is properly set-up: Mongo-Node-daemon-Cronjobs etc. Dunno why can't connect explorer to coin chain.
dockingtriple (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 06, 2015, 12:11:28 PM
 #2

EDIT:

GET /ext/getlasttxs/10/0.00000001?_=1449403734335 200 12ms - 11b
{ [Error: socket hang up] code: 'ECONNRESET' }

Doesn't sync. dunno why.
psionin
Sr. Member
****
Offline Offline

Activity: 465
Merit: 254


View Profile
December 06, 2015, 12:41:58 PM
 #3

Where is your Mongo DB located? After installation, it defaults to only allowing local connections.

Code:
# Listen to local interface only. Comment out to listen on all interfaces.
bind_ip = 127.0.0.1
dockingtriple (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 06, 2015, 12:52:43 PM
 #4

Where is your Mongo DB located? After installation, it defaults to only allowing local connections.

Code:
# Listen to local interface only. Comment out to listen on all interfaces.
bind_ip = 127.0.0.1


Thanks for your answer. Mongodb work properly,since i'm able to check 127.0.0.1:port

Everything setted up properly: Latest mongo,node,coind,cronjobs etc.

When i run npm start from explorer directory,i get always those error messages:

GET /themes/Cyborg/bootstrap.min.css 304 4ms
GET /vendor/jqplot/jquery.jqplot.css 304 4ms
GET /stylesheets/style.css 304 0ms
GET /vendor/jqplot/jquery.jqplot.min.js 304 1ms
GET /vendor/jqplot/plugins/jqplot.dateAxisRenderer.min.js 304 1ms
GET /vendor/jqplot/plugins/jqplot.ohlcRenderer.min.js 304 1ms
GET /vendor/jqplot/plugins/jqplot.highlighter.min.js 304 0ms
GET /vendor/jqplot/plugins/jqplot.pieRenderer.min.js 304 1ms
GET /vendor/jqplot/plugins/jqplot.barRenderer.min.js 304 1ms
GET /vendor/jqplot/plugins/jqplot.categoryAxisRenderer.min.js 304 1ms
GET /javascripts/chart.js 304 1ms
GET /images/logo.png 304 4ms
GET /ext/getlasttxs/10/0.00000001?_=1449405268380 200 3ms - 11b
{ [Error: socket hang up] code: 'ECONNRESET' }
GET /api/getdifficulty 200 60253ms - 39b
{ [Error: socket hang up] code: 'ECONNRESET' }
GET /api/getnetworkhashps 200 60965ms - 39b
{ [Error: socket hang up] code: 'ECONNRESET' }


Is there something missing in changing settings.json file? or something else?
psionin
Sr. Member
****
Offline Offline

Activity: 465
Merit: 254


View Profile
December 06, 2015, 01:13:09 PM
 #5


Everything setted up properly: Latest mongo,node,coind,cronjobs etc.



The cronjob should only be set up last, once everything is working properly and after the initial wallet->mongo synchronization. (Otherwise it could cause issues.)

Have you tried running the sync.js script?

Code:
sudo node scripts/sync.js index update

Have the collections been created in Mongo DB?

It should show something like this when viewed in Mongo Management Studio.



However, I think the script can only be run after the "npm start" launches the server properly, without the ECONNRESET error, so it could be related to the settings. Can you post your "database settings" section?
dockingtriple (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 06, 2015, 01:47:37 PM
Last edit: December 06, 2015, 07:33:17 PM by dockingtriple
 #6


Everything setted up properly: Latest mongo,node,coind,cronjobs etc.



The cronjob should only be set up last, once everything is working properly and after the initial wallet->mongo synchronization. (Otherwise it could cause issues.)

Have you tried running the sync.js script?

Code:
sudo node scripts/sync.js index update

Have the collections been created in Mongo DB?

It should show something like this when viewed in Mongo Management Studio.

http://i63.tinypic.com/6yzfpc.png

However, I think the script can only be run after the "npm start" launches the server properly, without the ECONNRESET error, so it could be related to the settings. Can you post your "database settings" section?

Solved.
Current node.js version stuck.
Installed a previous ones and it worked.

psionin
Sr. Member
****
Offline Offline

Activity: 465
Merit: 254


View Profile
December 07, 2015, 05:30:13 AM
 #7


Solved.
Current node.js version stuck.
Installed a previous ones and it worked.



Glad to hear it!
helloword2013
Sr. Member
****
Offline Offline

Activity: 333
Merit: 250


View Profile
January 25, 2016, 09:13:51 PM
 #8

I find the website couldn't display blocks and couldn't display the action "processing" after run the block explorer some days.
the same problem also :
http://explorer.gambitcrypto.com/
https://blockchain.vanillacoin.net/
http://explorer.infernopool.com/
why?
webvn2k
Sr. Member
****
Offline Offline

Activity: 335
Merit: 250



View Profile
June 21, 2017, 01:22:24 AM
 #9

i try config iquidus Explorer on window 7
1- run wallet - get info from config file C:\Users\<user>\AppData\Roaming\Coin
and config https://github.com/iquidus/explorer
mongo run ok- checked robomongo
iquidus connect wallet ok
however, i see mongo not sync iquidus and mongo emty
i run npm i see error 


please help me
jgle
Member
**
Offline Offline

Activity: 85
Merit: 10


View Profile
April 13, 2018, 09:10:54 AM
 #10

I have the same problem with you. How do you solve this problem?
Krestien
Jr. Member
*
Offline Offline

Activity: 99
Merit: 2


View Profile
May 06, 2018, 10:12:17 PM
 #11

I have the same problem with you. How do you solve this problem?
Do what the error is saying - try a more current nodejs version  Wink
In the screen 4.4.x is used, latest version is 10!

_____ DSTRA (https://dstra.io) ▬ ● ▬ FROM COMMUNITY, COMES UNITY ▬ ● ▬ DSTRA (https://dstra.io) _____
Mambocoin
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
November 02, 2018, 03:05:14 AM
 #12

I'm getting the same issue, someone has the fix for it?
ScoobyCoin
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
January 12, 2019, 06:16:46 PM
 #13

We were having a similar issue.
It kept saying it was already running.

npm start should be running in another window before running the index

Fixed it with this:
rm tmp/index.pid 

Then re-indexed it with this:

cd home/username/explorer
sudo node scripts/sync.js index update

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!