Possibly wrong tx index or id - check these values in your masternode.conf

Also, it's worth noting for anyone thinking about using that script, that although IPV6 nodes do work it depends on the local wallet support - the VGS wallet does not currently support IPV6 masternodes, so you should be using the -n 4 option to install and if you are setting up multiple nodes there is an extra step.  I'll tweak the documentation I wrote when I get a chance.

I finally got my second node up and running on the same instance as the first, however Florian's script integration doesn't work because he's used the wrong port.  I submitted a PR for him to switch to my implementation, which works and uses the latest logo.

https://github.com/masternodes/vps/pull/105

Well I didn't get any reassurance yet, but after reading a bit more I am even more bullish

So this does seem to exist on the CounterParty (XCP) platform, but with no volume. 

https://xcpdex.com/market/COVALC_XCP

I'm going to poke some people on Twitter to see if I can get either more information regarding getting this on other exchanges, or some reassurance that Bittrex will not delist.

I like the tech, think it is a very promising project and am not put off by devs being slow with the updates, but I am quite worried for my investment in this coin.   

Even adding it to a small exchange like CoinExchange would give investors a bit more confidence.  Good projects with active development will always bounce back from a Bittrex delisting, but this is made harder, and the potential price drop much deeper, if Bittrex is the only exchange where the token is listed.

Totally wrong.  Not too long ago Bittrex delisted BitShares, which has a vibrant community, good tech, a working product, very active development and currently listed at #32 on CMC.

Node Script update - I have tried to set up multiple nodes per instance over IPV6 again (with a different coin) and I think I have it working now.  The issue was actually with my home router/ISP.  I will be attempting the same with VGS when I get enough coins for a second node (~19 days), I'll be doing a major update of the documentation and verifying Florian's integration then.

Restart your main wallet, sometimes it reports missing nodes when they are active.  Don't restart your masternode until you know for sure it's inactive.  You can use the getinfo and masternode status commands on your masternode wallet to help diagnose the problem.

So, you can start masternodes from the CLI or debug window:


However, if your wallet is unable to sync this probably won't work.  Since my last post my main wallet seemed fine but then got stuck at block 41327.  Deleting the blocks and restarting the wallet fixed it:

Vegas guy, we've got wallet issues at MNO:

https://masternodes.online/currencies/VGS/

VPS upgrade - Anyone using the script can use the following commands to upgrade your VPS instance, these are the steps I took:


I then restarted the daemon a couple of times but the blocks were stuck at 41179 so I did the following to resync the chain, to be sure:


This worked, then I waited for the blocks value to go up past 41280.  The version reported should be 2050001.


Then I restarted the node remotely from my main wallet.

Mac wallet for the latest release here, should be added to the core repo soon:

https://github.com/goosewobbler/LasVegasCoin2/releases/tag/v2.5.0.1

I didn't do anything with my wallet files and it all seems to work (not that I noticed any issues with the previous release besides the wrongly reported version), but anyone having issues should follow the instructions above for upgrade.  The wallet files on a Mac are located here:

So this just seems to be the last official release of Florian's Nodemaster?  Which is the exact same thing I posted but an old version and without Las Vegas Coin support; anyone using this script will be better off using the master version at least, and my fork for LasVegasCoin support at least until Florian merges my PR.

Also...I thought this solution wasn't good enough for people who know nothing about linux?  I mean, you do still have to type a couple of commands into a terminal...

Vegas guy, thanks for explaining your thinking here.


The issue I have with this is, "MANY people know NOTHING about linux" contradicts "create a VPS on their linux system".  If you know nothing about linux, why are you attempting to run it?  I don't know anyone actively running linux who knows nothing about it.  Ubuntu is designed to be easy to use but ultimately the people who know absolutely nothing are going to be put off by the following words:  "script", "launch", "VPS", "linux".  

It just seems to me that we are trying to cater for the a very small group of people who are (a) intrigued enough by masternodes to want to set up their own VPS as opposed to using a pool but (b) know nothing about linux.  These people would be better served by a web-based system like https://gincoin.io - no linux involved so everyone who knows nothing about linux, including those who are interested enough to want to try it out, are catered for.
 

So this seems similar to what the GIN guys are trying to do.  I don't own their coin and haven't tried out their system yet, but will give it a go and report back when they support a coin I own.

Thanks for the transaction Vegas Guy.  I still think the project has a lot of potential; if we can work through the technical hitches, get some stable development done and work on the USP of the coin then more people will be attracted to it and we can build a decent-sized community.

However I'm still confused about what exactly you want regarding this node guide/script.  Who is running this server?  Whose machine are we using?  For what purpose are "we" hosting nodes?  Is it a node pool?  For n00bs who don't know how to use Linux to give their coins up to us in return for a managed service?  We need more infrastructure for that.  Or are you simply wanting to test that our node guide works for someone who supposedly knows nothing but still managed to install Ubuntu?  I don't understand.

I can make a brain-dead guide if you like, every click laid out from first screen of ubuntu to a running node.  However, aside from the fact that the guide will be huge and most people won't need it - there are other issues:

• Running a node on a VPS is the easiest option, you increase security and avoid a lot of complication by having a separate wallet for your node on a remote, always on, managed server.
• If you really want a brainless MN setup, you're looking in the wrong place.  N00bs won't even consider installing Ubuntu - that is too complex and risky.  Maybe you want VGS on the Gin platform. https://p.gincoin.io/#!/

Personally I think we should be concentrating on the fundamentals of this coin, the differentiating points - before messing around with nodes, and yes, ROI.  Look at Campus Coin, they haven't even got Masternodes yet and they're building a significant community and a lot of buzz because they have a unique, well thought out idea and plan of execution for bringing that coin to real-world usage not *some time in the future* but NOW.  They're prioritising mobile app development, considering usecases, getting their coin in the hands of their users above everything else, and that's what we should be doing.

Ok, that's good, I'll update the other post.  Did you use the command to stop the daemon after that?  It will still be running the old version in memory if the wallet daemon is not restarted.

If you did, it *would* normally be helpful to verify the version running using the getinfo command - but I believe the wallet is still reporting 2.0.0.3... I was going to take a look at this issue but haven't had time just yet.

Are you using IPV6 addresses?  

If you are, you haven't enabled support on your VPS.  In Vultr this is a checkbox on the server setup page.

My nodes are IPV6 enabled even though configured for IPV4.  If yours are not enabled for IPV6, it might be that we need to be more specific with the update command, like:

IPV4 Nodes

IPV6 Nodes

Let me know if this helps.

I tweaked and cleaned up the node script setup guide and uploaded it to the docs in my fork.

https://github.com/goosewobbler/LasVegasCoin2/blob/master/doc/vps-masternode-setup.md

So this is just a script to automate the setup of one or more masternodes on a server.  I'm not sure what you mean by "setup our own server", do you mean a Masternode pool for LasVegasCoin?

Any masternode or group of nodes has to be hosted on a server somewhere, so for setting up a pool - unless you are personally running an exceptionally beefy machine with a superfast connection, you can't really avoid paying a 3rd party.

Multiple nodes with this script is simply untested by myself.  It should work through IPV6 out of the box, as stated on the script installation text; multiple nodes through IPV4 needs some extra configuration of your VPS.  

Basically when I started with this script I was new to masternodes, using an early Magnet wallet, and couldn't get it working *at the time*.  I got single nodes through IPV4 working, then tried and failed to get IPV6 working for a single node.  Due to having a few nodes to set up very quickly, decided to stick with the known working approach rather than spending any more days fruitlessly messing around with things.

I am a lot more experienced with masternodes now, and in about two weeks I will be setting up my fourth node for two of the coins in my portfolio.  Since it isn't recommended to run more than three nodes per instance and my VPS bill is quite chunky already, I will look at reconfiguring them to use multiple nodes over IPV6 and ensure the instructions for the script covers this case.