 Show Posts
|
|
Pages: [1]
|
Suddenly, I have a problem to open my wallet on mac high sierra today. It quits unexpectedly during 'loading block index...', but yesterday everything used to work. Does anyone have the same problem?
This could be caused by closing the wallet incorrectly/unexpectedly. You can fix it by re-syncing the blockchain from scratch. Here are the instructions: 1. Stop/shutdown your wallet client if it is running. 2. Go to Win: %appdata%/solaris/ OR Mac: ~/Library/Application Support/Solaris/ Command+shift+g put: ~/Library/Application Support/Solaris then click GO 3. Delete all files and folders EXCEPT backups, folder, wallet.dat, solaris.conf and masternode.conf (DO NOT DELETE backups folder, wallet.dat, solaris.conf and masternode.conf) 4. Start your wallet client and let it sync again. Thank you so much for your advice. Everything works fine again. |
|
|
|
|
Suddenly, I have a problem to open my wallet on mac high sierra today. It quits unexpectedly during 'loading block index...', but yesterday everything used to work. Does anyone have the same problem?
|
|
|
|
Did you try to resync the Blockchain and also try the comand:
masternode start all
in the Console ?
Which lines are in your masternode.conf & solaris.conf ?
I have running 10 MNīs without Problems.
Yes, I tried it several times. It seems that the provided set up guide is outdated or the problem is only affecting new masternodes. I use the same schema for these two files as it provided in the guide: ALIAS VPS_IP:60020 PRIVATE_KEY TRANSACTION_ID INDEX_ID - masternode.conf And solaris.conf: rpcallowip=127.0.0.1 rpcuser=ANY_LONG_USERNAME rpcpassword=ANY_LONG_PASSWORD staking=0 server=1 listen=1 port=60020 masternodeaddr=VPS_IP:60020 externalip=VPS_IP:60020 masternodeprivkey=PRIVATE_KEY No for running a Masternode the setup guide works; i have donwloaded fresh wallets and setup new MNīs. Comands: masternode genkey masternode outputs You have changed in .conf files ? Sorry for my questions but i try to troubleshot to solve your problems. When it also not works then i dont know what happens. Maybe change your VPS Hoster ... im Hosting -> https://www.vps.agWindows Server the smallest Package and have no Problems with Masternodes. I used these commands, generated a new private key and updated files locally and on VPS. Currently, the VPS wallet is reindexing blocks. Previously I changed VPS to time4vps as I also thought that the problem is with a previous hoster. upd. Somehow, it started to work. Now I can see that 'active' time is ticking. Thanks a lot for all contributors who help me to solve the problem. I hope it works now. |
|
|
|
Did you try to resync the Blockchain and also try the comand:
masternode start all
in the Console ?
Which lines are in your masternode.conf & solaris.conf ?
I have running 10 MNīs without Problems.
Yes, I tried it several times. It seems that the provided set up guide is outdated or the problem is only affecting new masternodes. I use the same schema for these two files as it provided in the guide: ALIAS VPS_IP:60020 PRIVATE_KEY TRANSACTION_ID INDEX_ID - masternode.conf And solaris.conf: rpcallowip=127.0.0.1 rpcuser=ANY_LONG_USERNAME rpcpassword=ANY_LONG_PASSWORD staking=0 server=1 listen=1 port=60020 masternodeaddr=VPS_IP:60020 externalip=VPS_IP:60020 masternodeprivkey=PRIVATE_KEY |
|
|
|
Also no luck setting up masternode. Failed to start masternode.....
I can see in the masternode list that there are currently 4 attempts to set up a masternode, and it seems that all of them have the same problem: SazezmFPk4XTMy38PVrRqULx39rwDHwWwy SMPJDU6FwovcsikqrbyTyYwPnhyzaddNTD ShRw7vBvnag9nwyhYRKDauVmmtBkePuNwL SQekALqn8J1yAm17sQkLC5hCkdLYaNhSxS |
|
|
|
Ok. My Cryptobridge coins are back.
Is wallet working now on Cryptobridge? What is about other exchanges? Does anybody know when maintaince will finish with Solaris wallet? What is going on with txbit.io exchange? In which phase is it? I believe Kucoin exchange is working now and someone did say that CryptoBridge is back as well. Not sure about Coinexchange though. The Solaris wallet is all fixed now so no more maintenance. There has not been any more updates on the txbit exchange as the dev team have been working hard to get the wallet issues fix asap which they have now done so hopefully they are now back working on the txbit exchange. Remember txbit won't be launched until later this year so we still have a while to wait for this. Also like to point out, that now is a great time to set up a masternode as there are a lot less online now at just 635 as I write this going by the masternodesonline stats. We can earn 3 to 4 MN rewards daily right now so take advantage of this while it lasts as people are most likely still updating their MN's. I'm trying to set up a masternode using the provided guide, but it doesn't work. |
|
|
|
I tried to remove info from the solaris.conf file in the local wallet, and from the file masternode.conf in the VPS wallet, as you suggested. After I tried to start the alias in the local wallet, the wallet showed me an error message.
Can you post a screenshot of the error message (make sure to remove/change any private key etc if that shows up in the error message). It produces the next error message when I try to restart the alias: Alias: *** Failed to start masternode. Error: Invalid IP address ********, masternode=******************************************** The initial problem was: Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? Did you restart the wallets after you got rid of the info?. Also are you starting the master node via the console?. Yes, I tried to restart the wallet, and insert the command in the command line, but I had that message. I also believe it shouldn't work this way as it contradicts with the official guide, isn't it? Anyway, thank you for your advice. I had the same issue as you when I closed the Local Wallet I had that happen last year, I can't check my VPS wallet because access is blocked here but looking at my local wallet I definately don't have anything in Solaris.conf file (even tho that guide tells you to). I also don't have anything in any of my other masternodes of other coins in the same but different named.conf file. I only ever had info in the solaris file if I was just using the local wallet but I quickly moved over to VPS wallet. I'm pretty sure people do have their masternodes running with info in the solaris file but like I said I couldnt get it working that way. Since staking has come out they say to put staking=1 in the solaris.conf file for just staking as well but again I'm staking here with no problems at all with nothing in the .conf file. So in the local wallet does it say pre-enabled when you start it and then move over to enabled after 30mins or so?. Hope you get it sorted soon. Thanks for the detailed explanation, the status 'enabled' all the time, when I start the masternode and after 30 minutes until I close my local wallet and reopen it later, then the status changes to 'missing'. Now I'm trying to empty the solaris.conf in my local wallet again to check one more time. |
|
|
|
I tried to remove info from the solaris.conf file in the local wallet, and from the file masternode.conf in the VPS wallet, as you suggested. After I tried to start the alias in the local wallet, the wallet showed me an error message.
Can you post a screenshot of the error message (make sure to remove/change any private key etc if that shows up in the error message). It produces the next error message when I try to restart the alias: Alias: *** Failed to start masternode. Error: Invalid IP address ********, masternode=******************************************** The initial problem was: Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? Did you restart the wallets after you got rid of the info?. Also are you starting the master node via the console?. Yes, I tried to restart the wallet, and insert the command in the command line, but I had that message. I also believe it shouldn't work this way as it contradicts with the official guide, isn't it? Anyway, thank you for your advice. |
|
|
|
I tried to remove info from the solaris.conf file in the local wallet, and from the file masternode.conf in the VPS wallet, as you suggested. After I tried to start the alias in the local wallet, the wallet showed me an error message.
Can you post a screenshot of the error message (make sure to remove/change any private key etc if that shows up in the error message). It produces the next error message when I try to restart the alias: Alias: *** Failed to start masternode. Error: Invalid IP address ********, masternode=******************************************** The initial problem was: Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? You have to set your info on solaris.conf and on masternode.conf file as write on guide and after run command startmasternode all false on your local wallet and wait with wallet open at least 1 hour I was trying to wait for more than 3 hours without closing the local wallet, and it was enabled all the time, after that I closed my laptop and now I have the same issue, the masternode is missing, active time is 0, protocol is -1 and the last seen time is !1970-01-01. If there is a chance that somebody from the developers' team reading this message, could you please give me some suggestions. |
|
|
|
I tried to remove info from the solaris.conf file in the local wallet, and from the file masternode.conf in the VPS wallet, as you suggested. After I tried to start the alias in the local wallet, the wallet showed me an error message.
Can you post a screenshot of the error message (make sure to remove/change any private key etc if that shows up in the error message). It produces the next error message when I try to restart the alias: Alias: *** Failed to start masternode. Error: Invalid IP address ********, masternode=******************************************** The initial problem was: Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? |
|
|
|
Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? It sounds like you have masternode info in your solaris.conf file of your local wallet so when that closes it shuts down the masternode, The local wallet should have info in masternode.conf file and NOT solaris.conf and the VPS wallet should have info in Solaris.conf and NOT masternode.conf. I tried to remove info from the solaris.conf file in the local wallet, and from the file masternode.conf in the VPS wallet, as you suggested. After I tried to start the alias in the local wallet, the wallet showed me an error message. |
|
|
|
Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? It sounds like you have masternode info in your solaris.conf file of your local wallet so when that closes it shuts down the masternode, The local wallet should have info in masternode.conf file and NOT solaris.conf and the VPS wallet should have info in Solaris.conf and NOT masternode.conf. Thank you for your response, but it's mentioned in the official guide that both files should be copied in the VPS wallet: "Copy the contents from the masternode.conf file on your machine and paste them into the Terminal (right click on mouse). Make sure the line you added is also there. Exit the file by pressing CTRL+X. Press Y to confirm and hit Enter to save. Now type: nano /root/.solaris/solaris.conf Copy the contents from your local solaris.conf file and paste them into the terminal. Exit and Save the file by pressing CTRL+X, Y and Enter." https://docs.google.com/document/d/1Z3h_qA7N3-KMA1ECxyfDbBO-_lG7Hkrp_8Iy0s2iUMI/edit# |
|
|
|
Hi Solaris community, I'm trying to set up a masternode on VPS http://time4vps.eu/ by following the latest guide, and everything looks fine in the local and VPS wallets (it's enabled, protocol 70717, the command getinfo on VPS shows that the block is the lastest one), but the active time is always 0 in my local wallet. After I close my wallet for few hours and open it again, the masternode has the status 'missing', even if the masternode still works correctly on VPS (I checked it with the command getinfo). I tried to reindex, but the active time is always zero and after few hours with closed local wallet it is 'missing' again. Any suggestions how to fix this issue? |
|
|
|
|
