Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS connection Fail . #14

Closed
xiaomingloveqinger opened this issue Mar 29, 2018 · 3 comments
Closed

TLS connection Fail . #14

xiaomingloveqinger opened this issue Mar 29, 2018 · 3 comments
Assignees

Comments

@xiaomingloveqinger
Copy link
Contributor

when i am starting a Node . here is the output .

./node 
2018/03/29 13:05:48.505221 [INFO ] GID 1, 1. BlockChain init
2018/03/29 13:05:48.532955 [INFO ] GID 1, 2. Start the P2P networks
2018/03/29 13:05:48.844393 [INFO ] GID 1, IPv4:  192.168.31.36
2018/03/29 13:05:48.844477 [INFO ] GID 1, Init node ID to 0xef05d4bafc5fc934
2018/03/29 13:05:48.847343 [TRACE] GID 1, WaitForSyncFinish() node.go:331 BlockHeight is  0
2018/03/29 13:05:48.847418 [INFO ] GID 1, [ 1 0 0 ]
2018/03/29 13:05:48.847473 [TRACE] GID 1, WaitForSyncFinish() node.go:337 others height is  []
2018/03/29 13:05:48.849739 [TRACE] GID 1, NewPowService() pow.go:385 pow Service Init succeed
2018/03/29 13:05:48.849827 [INFO ] GID 1, 3. --Start the RPC service
2018/03/29 13:05:54.850387 [TRACE] GID 36, func1() main.go:44 BlockHeight =  0
2018/03/29 13:05:54.850695 [TRACE] GID 36, DumpState() blockchain.go:1011 bc.BestChain= 8d7014f2f941caa1972c8033b2f0a860ec8d4938b12bae2c62512852a558f405
2018/03/29 13:05:54.850784 [INFO ] GID 35, nbr heigh--> [] 0
2018/03/29 13:05:54.850828 [INFO ] GID 35, needSync:  false
2018/03/29 13:05:54.850848 [TRACE] GID 36, DumpState() blockchain.go:1020 bc.Root= 8d7014f2f941caa1972c8033b2f0a860ec8d4938b12bae2c62512852a558f405
2018/03/29 13:05:54.850899 [INFO ] GID 36, [ 1 0 0 ]

2018/03/29 13:05:54.852472 [ERROR] GID 41, non TLS connect failed: dial tcp 127.0.0.1:30338: getsockopt: connection refused

2018/03/29 13:06:00.849714 [INFO ] GID 35, nbr heigh--> [] 0
2018/03/29 13:06:00.850264 [ERROR] GID 42, non TLS connect failed:  dial tcp 127.0.0.1:30338: getsockopt: connection refused
2018/03/29 13:06:00.851726 [TRACE] GID 36, func1() main.go:44 BlockHeight =  0
2018/03/29 13:06:00.851764 [INFO ] GID 35, needSync:  false
2018/03/29 13:06:00.851816 [TRACE] GID 36, DumpState() blockchain.go:1011 bc.BestChain= 8d7014f2f941caa1972c8033b2f0a860ec8d4938b12bae2c62512852a558f405
2018/03/29 13:06:00.851913 [TRACE] GID 36, DumpState() blockchain.go:1020 bc.Root= 8d7014f2f941caa1972c8033b2f0a860ec8d4938b12bae2c62512852a558f405
2018/03/29 13:06:00.851979 [INFO ] GID 36, [ 1 0 0 ]

Do I need to get some certificate to run a node ? is there a way to Bypass that ?

@yushunan
Copy link
Collaborator

You can use TestNet mode ,deploy at least 2 nodes,one of them config to mining node ,the other one config seed list use address of the mining node,then they can synchronized with each other

@xiaomingloveqinger
Copy link
Contributor Author

xiaomingloveqinger commented Mar 29, 2018

thanks , will try it .

@mmate91
Copy link

mmate91 commented Apr 30, 2018

You can use TestNet mode ,deploy at least 2 nodes,one of them config to mining node ,the other one config seed list use address of the mining node,then they can synchronized with each other

This solved the problem. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants