Bitcoin Forum
May 05, 2024, 11:47:37 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: CryptoNote - cannot connect to server via host terminal  (Read 90 times)
falky64 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 10, 2018, 04:35:29 AM
Last edit: February 12, 2018, 06:06:58 AM by falky64
 #1

Hello,

I try to start my daemon to initiate the handshake for the blockchain but I get this error, even though if i setup the same daemon file to run on a virtual machine it works fine... This blockchain was created out of "Cryptonote".

2018-Feb-10 14:54:10.066449 ERROR   Failed to init: genesis block mismatch. Probably you set --testnet flag with data dir with non-test blockchain or another network.
2018-Feb-10 14:54:10.066581 ERROR   Failed to initialize blockchain storage
2018-Feb-10 14:54:10.066690 ERROR   Failed to initialize core

***conversation closed********
1714909657
Hero Member
*
Offline Offline

Posts: 1714909657

View Profile Personal Message (Offline)

Ignore
1714909657
Reply with quote  #2

1714909657
Report to moderator
1714909657
Hero Member
*
Offline Offline

Posts: 1714909657

View Profile Personal Message (Offline)

Ignore
1714909657
Reply with quote  #2

1714909657
Report to moderator
1714909657
Hero Member
*
Offline Offline

Posts: 1714909657

View Profile Personal Message (Offline)

Ignore
1714909657
Reply with quote  #2

1714909657
Report to moderator
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714909657
Hero Member
*
Offline Offline

Posts: 1714909657

View Profile Personal Message (Offline)

Ignore
1714909657
Reply with quote  #2

1714909657
Report to moderator
falky64 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 10, 2018, 08:11:00 AM
 #2

I have rebuilt the cryptonote "build" folder again, the genesis tx address I have saved in the config folder and then rebuilt again, but still receive this error. i have no idea what's going on.
odolvlobo
Legendary
*
Offline Offline

Activity: 4298
Merit: 3214



View Profile
February 10, 2018, 09:51:11 AM
 #3

This is a Bitcoin forum. You will probably get better results in a CryptoNote forum, such as https://forum.cryptonote.org/

Join an anti-signature campaign: Click ignore on the members of signature campaigns.
PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
F2b
Hero Member
*****
Offline Offline

Activity: 2078
Merit: 863


View Profile
February 10, 2018, 11:03:28 AM
 #4

There's often bugs and errors with cryptonote fork, especially when you doesn't really know what you're doing (like me a couple of months ago).
Could you give a more detailed explanation of what you did? Step by step.
Have you tried to delete everything from your computer, re-clone it from github and re-build everything? If yes, are you sure you didn't forget the blockchain (hidden) folder (different location depending on your OS)?
falky64 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 10, 2018, 11:16:51 AM
 #5

I tried signing up to the cryptonote forum but they have a bug where they don't send you a verification link in an email lol so i am stuck on here atm sorry.

I have completely deleted everything, then rebuild all through "Ubuntu", I can get the seed nodes running the blockchain on my external server, which I uploaded all my script to and ran the daemon from both servers to complete a handshake, and they run perfectly, I can setup a wallet and mine but only through the ssh connection terminal. If I try to start my blockchain daemon from my home computer, even with the other seed nodes running on a different computer, it gives me this same result. The reason i want to have it running as well on my computer is so i can start mining as mining off the server caused a "killed" response after a while because im using up to much CPU. I thought once you have the binaries, they connect automatically once you start the daemon but seems they do not connect to the seed nodes or something gets in the way.
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!