VPS 18
#1
Hi!
I won VPS 6. and my another VPS 18 is going to be terminated, So i stopped it so i remember it that it going to be terminated.
I stopped it like yesterday.
Today morning IT WAS RUNNING. Who started itt I have no mail of login to cp.
This has happened 3rd time i changed password 2 times.
       My Post Count:
[Image: img.php?userid=20087&vps2]




#2
Maybe the VPS has already been given to someone else? If you check other VPS 18 threads looks as though there has been a mismatching of logins that has been corrected VERY recently. Could be the terminated VPS was then assigned to someone else.
#3
I'd guess the node or a service critical to OVZ was rebooted, but I can't be sure.
#4
@deanhills

There has been no login information mismatch in the case you mention and the OP of the case requested a service cancellation in the end. The problem was an entirely different: SolusVM has given a already used IP address to a second server. This means that an attempt to connect to the IP will connect to the first server that has the IP and not the second. So all changes on the second server have no effect on the first server, obviously. You misunderstood something.


@Abdul Sami

It is highly possible that it was started automatically. This could have been as @Ignis mentioned because the OpenVZ node might have been rebooted or a OpenVZ component was restarted. This usually also boots offline VMs by default.

The other possiblity is low but could also happen. Some providers actually utilize programs to monitor the status of the containers and start them when they're turned off. I had a VPS with a provider some time ago that had only IPv6 and they did such a thing. I shut it down like 5 days in a row and it was always online the next day. I opened a ticket and they explained me why it is as it is.

Pointless to me though. If I shutdown a server I probably have my reasons. So no respect for the customer here.
#5
(2017-12-07, 8:40:42 pm)Hidden Refuge Wrote: @deanhills

There has been no login information mismatch in the case you mention and the OP of the case requested a service cancellation in the end.  The problem was an entirely different: SolusVM has given a already used IP address to a second server. This means that an attempt to connect to the IP will connect to the first server that has the IP and not the second. So all changes on the second server have no effect on the first server, obviously. You misunderstood something.

Thanks for sorting it out @HR.  I think I understood the basic fact about the IP that belongs to another VPS and translated it into the consequences for login.  The IP belongs to another VPS, so if the VPS owner who queried it tried to login with that IP the root password would not match.  But yes you're right of course, it wasn't a mismatch - it was what it said it was, the VPS SolusVM fetched an old IP for the new VPS.  

I'm a bit perplexed though.  How is this technically possible?  Once the SolusVM Admin Panel has allocated an IP that IP vanishes from the Admin Panel for the next VPS that is created - even if it did happen the conflict would have to show up in the listing of the VPSs - like does SolusVM allow the listing to show more than one user for the same IP?  Or does SolusVM work different to Virtualizor.  For me what would make greater sense is that perhaps the person who created the VPS used the content of the PM of the previous VPS as a template for informing the member of the next VPS of the login details, and maybe just forgot to replace the IP in the PM with the new IP.  That would make more sense to me.  But then again my Admin experience is more with Virtualizor.  Maybe SolusVM works different?
#6
@deanhills

VPSs that are created automatically through WHMCS or in the reseller panel of SolusVM get an IP address assigned automatically from a IP address pool that is available. You cannot control which IP it gets. SolusVM has a flaw in this system that the old developers couldn't fix and the new one can't also as it seems. For some reason it picks already used IP addresses out of the IP pool.

It has absolutely nothing to do with PMs and information of VPS owners. VPS 18s are always fresh created through the reseller panel.
#7
(2017-12-08, 6:16:43 am)Hidden Refuge Wrote: @deanhills

VPSs that are created automatically through WHMCS or in the reseller panel of SolusVM get an IP address assigned automatically from a IP address pool that is available. You cannot control which IP it gets. SolusVM has a flaw in this system that the old developers couldn't fix and the new one can't also as it seems. For some reason it picks already used IP addresses out of the IP pool.

It has absolutely nothing to do with PMs and information of VPS owners. VPS 18s are always fresh created through the reseller panel.

Got it thanks @HR.  Must be very frustrating when one can't control the allocation of the IPs.  The Virtualizor IPs work well.  I'm sure there must be Solus VM features that may be better than Virtualizor, but at least with this one aspect I'm glad what I see is what I get. I know exactly what IPs are available.   I'd hate not to be able to control the pool of IPs.




Users browsing this thread: 1 Guest(s)

Switch to mobile version

Sponsors: Ftpit - ZXPlay - GalaxyHostPlus - Verelox- HostUS - Host4Fun - Evolution-Host - NodeBlade - HostDare - VPSMost


BitCoin donations: 1DQxbstaTb5SWk6QC2gFeQUTFR64JX4cEo