Pages:
Author

Topic: Darknet DNET Masternode VPS support MP-Hosting now taking DNET as payment. - page 17. (Read 18855 times)

legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi Paul, I paid for 4 VPS's last night (invoice 645) around 13 hours ago but they aren't setup yet still.
I thought they were provisioned automatically? Usually they are setup much quicker than this...

Hi I'll have a look at the build scrypt
It might of got stuck

Thanks
Paul



Hi
ok the build scrypt has crashed ill get these sorted now for you
sorry about that 

thanks
Paul
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi Paul, I paid for 4 VPS's last night (invoice 645) around 13 hours ago but they aren't setup yet still.
I thought they were provisioned automatically? Usually they are setup much quicker than this...

Hi I'll have a look at the build scrypt
It might of got stuck

Thanks
Paul
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Hi Paul, I paid for 4 VPS's last night (invoice 645) around 13 hours ago but they aren't setup yet still.
I thought they were provisioned automatically? Usually they are setup much quicker than this...
legendary
Activity: 1778
Merit: 1003
NodeMasters
Guys, any reviews on this VPS web host provider http://v-sys.org/services/ddos_protection/remote_site_protection ? Did anybody try it ? I like the idea of DDoS attack prevention, I need safe traffic only.
Hi no not seen them there price is a lot higher then ours !

But they look ok
Also all of my services has ddos protection as standard

Thanks
Paul
member
Activity: 66
Merit: 10
Guys, any reviews on this VPS web host provider http://v-sys.org/services/ddos_protection/remote_site_protection ? Did anybody try it ? I like the idea of DDoS attack prevention, I need safe traffic only.
legendary
Activity: 1638
Merit: 1011
jakiman is back!
My VPS's with subnet 164.132.176.xxx were all in stopped shut down status.
So I had to start the VPS before i could even connect back to them.

Also, some VPS's have changed IP addresses which meant I had to update my masternode.conf and restart wallet etc. Sad

Hi what ips have changed ?

can you please open a support ticket with the information


thanks
Paul


Okay. I'll open a support ticket as it seems I still can't log into that VPS.

Edit: done.
legendary
Activity: 1778
Merit: 1003
NodeMasters
My VPS's with subnet 164.132.176.xxx were all in stopped shut down status.
So I had to start the VPS before i could even connect back to them.

Also, some VPS's have changed IP addresses which meant I had to update my masternode.conf and restart wallet etc. Sad

Hi what ips have changed ?

can you please open a support ticket with the information


thanks
Paul
legendary
Activity: 1638
Merit: 1011
jakiman is back!
My VPS's with subnet 164.132.176.xxx were all in stopped shut down status.
So I had to start the VPS before i could even connect back to them.

Also, some VPS's have changed IP addresses which meant I had to update my masternode.conf and restart wallet etc. Sad
hero member
Activity: 728
Merit: 500
Paul, did one of your server poweroff again?

Quite a number of my masternodes went missing today and I had to restart them:

All with subnet of:
164.132.143.xxx
164.132.151.xxx
164.132.176.xxx

HI
not that i know of
ill check the logs / emails

thanks
Paul


2 of mine went missing with ips

164.132.176

still shows as running. just restarted them
legendary
Activity: 1778
Merit: 1003
NodeMasters
Paul, did one of your server poweroff again?

Quite a number of my masternodes went missing today and I had to restart them:

All with subnet of:
164.132.143.xxx
164.132.151.xxx
164.132.176.xxx

HI
not that i know of
ill check the logs / emails

thanks
Paul
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Paul, did one of your server poweroff again?

Quite a number of my masternodes went missing today and I had to restart them:

All with subnet of:
164.132.143.xxx
164.132.151.xxx
164.132.176.xxx
legendary
Activity: 1778
Merit: 1003
NodeMasters
what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console

well thats what i get for updating the system
LOL
ok i will look at what missing

thanks
Paul



Hi
ok i fixed it now you can start / stop  Etc

thanks
Paul
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Seems the new v1.0.2.1 masternode image has the darknetd already running from get go.
Easiest way is to do following once you login to the new masternode VPS for the first time:
(note that this assumes you have a separate controller wallet where you secured 10K DNET)

Quote
0. Check if wallet is already running & what version (e.g. "version" : 1010001 = 1.1.0.1)
./darknet-cli getinfo

1. Stop darknet (if above command worked & showed a version)
./darknet-cli stop

2. Edit masternode.conf file via command
 nano /root/.darknet/darknet.conf

3. Add/change following lines only:
masternode=1
masternodeprivkey=
rpcuser=
rpcpassword=

4a. Now if wallet version is NOT 1.1.0.1 or you are not sure, run the upgrade script as per below: (if not, skip to next step 4b)
cd
wget http://164.132.143.5/1.1.0.1/darknet-update.sh
sh ./darknet-update.sh
- this will upgrade your wallet then start the wallet/masternode for you.

4b. Start darknet (no need if you used upgrade script above)
./darknetd

5. Wait until blocks sync up to latest block:
./darknet-cli getinfo

6. Check status of your masternode.
./darknet-cli masternode status
- Status should say "Not capable masternode: Hot node, waiting for remote activation." This is expected and normal.

7. Start the matching masternode alias from your controller wallet's debug CLI:
masternode start-alias

8. Check status of your masternode.
./darknet-cli masternode status
- If your txid and pubkey shows up and says "status" : "Masternode successfully started", it's all done!
- Now just wait 24 to 48 hours for your first MN payment!
legendary
Activity: 1778
Merit: 1003
NodeMasters
what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console

well thats what i get for updating the system
LOL
ok i will look at what missing

thanks
Paul
hero member
Activity: 728
Merit: 500
what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console
legendary
Activity: 1778
Merit: 1003
NodeMasters
Thanks Paul Smiley

It worked for the 3 missing nodes.

Cool

glad i could help you out


thanks
 Paul
member
Activity: 85
Merit: 10
Thanks Paul Smiley

It worked for the 3 missing nodes.
legendary
Activity: 1778
Merit: 1003
NodeMasters
when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning

Yes I'd the same problem on some nodes too, restarting solved the problem.

Still 3 of my nodes goes missing, I keep restarting them.

ok
best thing to do is

make sure you are on the latest version 1.0.2.0.1


 
stop darknet by typing

./darknet-cli stop

then

delete everything in the .darknet folder
apart from
darknet.conf
masternode.conf
wallet.dat



then start the damon and let it sync up before you start the masternode.

that has worked on a  masternode that i was having issues




thanks
Paul
member
Activity: 85
Merit: 10
when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning

Yes I'd the same problem on some nodes too, restarting solved the problem.

Still 3 of my nodes goes missing, I keep restarting them.
hero member
Activity: 728
Merit: 500
when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning
Pages:
Jump to: