• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Search results

  1. J

    Dash Core v18.0.1 Released

    VULTR does not permit to downgrade. So if we upgrade from 4GB to 8 GB there is no going back, and the cost remains high.
  2. J

    masternode visible (ninja) : NO

    Apologise for the late answer. Thanks, yes now it works. May I suggest to add the location of the SHA256SUMS.asc to the https://docs.dash.org/en/stable/masternodes/maintenance.html#manual-update
  3. J

    masternode visible (ninja) : NO

    Hello, I just upgraded from 16 to 17. When I check with dashman status it says masternode visible (ninja) : NO It's the only red flag. On ninja https://www.dashninja.pl/ it appears as if the port is closed. And if I did not upgrade (Still showing 16.0) I upgraded using ~/dashman/dashman sync...
  4. J

    v0.16 Support - FAQ and Known Issues

    Thanks. To make this very simple for anyone reading this (or myself in future). After you have cleared whatever was cousing the POSE then go to the Dash Masternode Tool and press the Update Service button. And then Send Update Transaction. And then wait.
  5. J

    v0.16 Support - FAQ and Known Issues

    So one problem was that -maxconnections was set to 64. I changed that by changing the dashd.conf and setting it to 128. I am still getting a warning: Warning: -masternode option is deprecated and ignored, specifying -masternodeblsprivkey is enough to start this node as a masternode. But I...
  6. J

    v0.16 Support - FAQ and Known Issues

    Hi, I tried to update using dashman, using ~/dashman/dashman sync update -y but got a POSE BANNED error on the DashMasternodeTool. Then when I run ~/dashman/dashman status I get: dashd version : 0.16.0.1 dashd up-to-date : YES dashd running : YES...
Back
Top