Results 1 to 10 of 10

Thread: BlueVM troubles

  1. #1

    BlueVM troubles

    I bought a BLUE4 from BlueVM on December 30th, and after some initial issues with processes I was running getting terminated, I was happy with the service.

    Yesterday, I noticed there was something wrong with my system, it seemed like my processes were getting terminated again, and I tried to SSH in. I couldn't get a connection, and after rebooting the VPS nothing was accessible. Pings timing out, SSH/web port timing out, etc. I contacted support to help resolve the issue:

    "Hello, all network connections are timing out for me to this instance. I've verified iptables has no rules enabled, but not sure what else to check.


    I received a response within 30 minutes, which was impressive. Unfortunately I wasn't impressed with what I read:

    I assigned a new IP, I tested that IP and it pings.
    If you require further support, please let us know.
    Best Regards,

    Assigned a new IP?? OK, I suppose I can update my DNS entries to point to the new IP. Except it still doesn't work, I have the exact same issues. In attempting to troubleshoot I'm having trouble connecting to another VPS of mine through a different provider, and a traceroute puts the blame at my ISP. I chalk it up to ISP issues and say as much in a response, although request that the IP be set back to what it was.

    I went to sleep and woke in the morning to no response from BlueVM. I'm now able to connect to my other VPS, but can't connect to the BlueVM instance. I verify that my working VPS cannot reach it and that cannot reach it and send this information to support. I send screenshots and traceroute output. I e-mail a Customer Review saying my VPS has been unreachable for almost 24 hours now. I send an e-mail to [email protected] explaining the situation.

    As of right now it's been over 24 hours and I still have heard nothing but the initial contact when they gave me a different IP. I am still unable to connect to the instance.

    If you're considering buying a VPS from BlueVM I would strongly advise going with a different provider. I've used many VPS providers in the past and have never had such a terrible experience. I'm not even 1 month into the contract and the instance has been down for over 24 hours with no word from anybody. I've provided plenty of evidence and gone through multiple channels to try and get ahold of somebody and haven't even received as much as a status update. Oh, and their server uptime page is a default "It Works" page ( and their IRC server ( is parked at NameCheap. Real professional guys.
      0 Not allowed!

  2. #2
    Join Date
    Mar 2003
    Their reply doesn't explain much.

    Wondering why they assigned you a new ip?
    Specially 4 You
    JoneSolutions.Com ( Jones.Solutions ) is on the net 24/7 providing stable and reliable web hosting solutions and services since 2001
      0 Not allowed!

  3. #3
    I was a little surprised when I received that response as well!!

    Oh, I forgot to add, I've completely rebuilt the VM in desperation and still can't connect.
      0 Not allowed!

  4. #4
    After no response and no resolution I cancelled the service. 3 minutes after cancellation I get a response to my original ticket:


    You have already canceled your service.

    Do you still need assistance with this?"

    You've got to be kidding me. Avoid like the plague.
      0 Not allowed!

  5. #5
    Join Date
    Jan 2012
    Glasgow, Scotland
    That's the common to fix issues for bluevm, it seems their upstream (colocrossing?) is null routing your IP.
    HostUS - Premium Hosting Made Affordable
    EIGHT Worldwide locations spanning USA, Europe & Asia Pacific
    Own ASN, Own Network, Own IP's - AS7489 & AS25926
      0 Not allowed!

  6. #6
    Okay. As it happens, that's my reply to your ticket. I checked your IP, and it wasn't routing, dropping off a hop before the node you were on. It happens randomly, and the easiest and fastest fix for YOU (the client) is to assign a new, working IP. I tested the IP after I assigned it and it was pinging. Second, the page is down for the moment while we finish with moving the last of the old HyperVM nodes to Feathur. My best estimate on that is next month, as it turned out that it wasn't going to be as easy as we thought. Finally, is NOT owned by BlueVM. It is its own IRC network. While it may be owned by 2 staff members of BlueVM, it is NOT owned by BlueVM. EDIT: Also, the domain has been renewed and is working again.
    If you're still having issues with your server, reply to the ticket and send me the Ticket # in a PM, and I'll take a closer look for you.
    Last edited by Magiobiwan; 01-23-2014 at 12:17 PM.
      0 Not allowed!

  7. #7
    That's great, thank you for explaining it. It would've been nice if you could've explained it to begin with though, right? And then you ignored my follow-up replies. The new IP may have very well been pinging for you, but it wasn't for me or the rest of the Internet as far as I could tell, and I included traceroutes and screenshots from 3 different connections to illustrate that point. The only message I ever received from you was the two sentences I quoted above. Is that good customer service?

    If your uptime page was up I might've had more insight into what was going on with the service I paid for. If you used a working IRC server I could've contacted you there. I ended up sending 3 replies to the ticket to you, 1 new ticket in Customer Reviews, and a direct e-mail to [email protected].

    Justin contacted me today and was very polite, he also didn't feed me a load of excuses which I appreciate, and offered a month credit. I consider the original issue resolved and appreciate him making good on the downtime and lack of communication from customer service.

    However, yes, I'm still having issues with my server. I see it in Services but it no longer shows up in the Feathur management interface. I responded to the original ticket that Justin replied in, the one quoted above (#209102), a few hours ago but I have not yet heard back.

    Edit: sorry, Justin contacted me yesterday, I just got around to it this morning.
    Last edited by blowstamp; 01-23-2014 at 12:32 PM. Reason: clarify timeline of events
      0 Not allowed!

  8. #8
    I've replied to your ticket again (the original one). I'll talk with Justin about putting at LEAST a parking page for the Uptime page while it's down, or setting up the new uptime page with just the nodes on Feathur.
      0 Not allowed!

  9. #9
    Thank you. I have replied to the ticket again as well, I see the instance in Feathur but am still unable to connect from my ISP, my other VPS, or
      0 Not allowed!

  10. #10
    OK, I finally figured it out. In the ticket you said you set the IP back to what it was before, which I appreciate, but Feathur was still showing a different IP. I was trying to connect to the IP Feathur was showing, but I'm now able to connect via the IP you gave me in the ticket. Thanks for that.

    One thing that's a little odd, when I rebuild the VPS in Feathur the new root password I provide doesn't work in the resulting instance. I have to go into the console and change it manually. No big deal, but worth mentioning.

    Otherwise everything seems resolved, thank you for taking care of it.
      0 Not allowed!

Similar Threads

  1. Using BlueVm reseller but need help!!
    By FluidWeb in forum Reseller Hosting
    Replies: 8
    Last Post: 12-27-2013, 01:53 AM
  2. Virus Troubles... Spyware TROUBLES
    By sapper in forum Hosting Security and Technology
    Replies: 2
    Last Post: 06-06-2004, 11:55 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts