Is Hosthatch.com currently operating normally?

Comments

• ralf Member

  May 16

  @bxk6rbd said:
  I fixed it myself

  Wow! You are a LITERAL SUPERSTAR!

  but I don't entirely agree with @hosthatch 's statement:

  Oh.

  ping getway : NETWORK UNREACHABLE
  ip a : enp1s0 completely disabled
  cat /etc/network/interfaces : Fxxk, no "enp1s0", only "ens3", dhcp

  After changing "ens3" to "enp1s0" in /etc/network/interfaces and restarting the VPS, the network was restored.

  Is this the first time your kernel has ever been upgraded?

  But then a new question arose: Who modified the system settings that caused the network to become unavailable?

  Let me guess - you have your system configured to automatically update. Given the level of aptitude shown so far, you don't even know this is set up.

  I did a simple check, and my VPS showed no signs of hacking, no missing files, no login records from unknown locations, and none of the simple running services had any recent security vulnerabilities. If it wasn't a problem with my VPS, then the deeper question is: why did the system's network card change from "ens3" to "enp1s0"?

  Your kernel was updated.

  In conclusion: this very unpleasant experience was entirely avoidable.

  You're right. You acknowledge that the VPS works, and it was entirely a configuration error on the operating system that you chose to install on it.

  The entire experience could have been avoided if you hadn't contacted support for help in managing an UNMANAGED service.

  If their ticket system clearly stated "The relevant VPS is a Promo model and receives low-priority service support" when posting the request, or if Ivan T added a sentence when replying to me about changing the root password: "Because your machine is a Promo machine, it receives low-priority service support. Also, our Singapore data center is currently operating normally, and no other users have reported network problems. Therefore, we suggest you check your network after changing your password," the increasingly unpleasant waiting could have been avoided!

  Or you could have used a braincell, and down all of the above actions without even raising a support ticket. If you buy an unmanaged server, you are expected to know how to use it.

  What upset me even more was @hosthatch 's earlier reply. He must have seen the two follow-up tickets I sent later, in which I clearly stated:

  Asking for support that shouldn't have been needed?

  "I feel like Ivan T is deliberately ignoring me!

  I thought you acknowledged that you had a low-priority support and it was user-error. I'm sure your tickets were deliberately ignored to deal with actual issues that required support.

  As a long-time customer who has used your services for over 10 years, I am extremely disappointed!"

  And you still haven't learned how to admin a server in all those 10 years.

  My feeling was correct; it was indeed a deliberate disregard! I have 4 VPSs with your company, only this one is a promo, and it was ordered three years ago. It's impossible for me to remember your restrictions on promo machines! And as a service provider, you should realize that your ticketing system and control panel completely lack any necessary explanation regarding service downgrading for promo machines!

  Probably. The machine was working fine, as you eventually confirmed.

  You wouldn't even bother to give me, your long-time customer of 10 years, a single reminder!

  Reminder of what? That it's an unmanaged service?

  Thanked by 3webcraft forest PineappleM
• JabJab Member

  May 16

  @ralf he already dead, no more shooting please.

  Thanked by 2ralf forest
• COLBYLICIOUS Member

  May 16

  I am late to the party, TL;DR someone?

  Thanked by 1wrox
• behuk Member

  May 16 edited May 16

  @COLBYLICIOUS said:
  I am late to the party, TL;DR someone?

  Customer's unmanaged and promo-priced server broke during a software upgrade applied by the customer. Customer filed a support ticket. Support were slow because the issue was out of scope (and due to promo pricing = lower support priority), and customer is upset.

  Thanked by 4COLBYLICIOUS forest PineappleM nick_
• dsh Member

  May 22

  I have a few promo storage servers with them in LA, Chicago, and London.

  Very occasionally, a server’s network just stops responding. Restarting the network service has always fixed it.

  So I put together this script in case anyone else finds it useful. I run it as a cron job every minute.

  #!/bin/bash
  
  URL1="https://www.google.com"
  URL2="https://www.bing.com"
  
  echo "$(date): checking network"
  
  if ! curl -s --retry 3 --retry-delay 2 --max-time 5 "$URL1" > /dev/null && \
     ! curl -s --retry 3 --retry-delay 2 --max-time 5 "$URL2" > /dev/null; then
      echo "$(date): both checks failed, restarting network"
      systemctl restart networking
      curl -d "Network restarted on $(hostname) at $(date)" https://ntfy.sh/{your channel}
  fi
  

  So far, the script has restarted the network 5 times across 6 servers over the past year.
• forest Member

  May 22

  @dsh said:
  I have a few promo storage servers with them in LA, Chicago, and London.

  Very occasionally, a server’s network just stops responding. Restarting the network service has always fixed it.

  So I put together this script in case anyone else finds it useful. I run it as a cron job every minute.

  #!/bin/bash
  
  URL1="https://www.google.com"
  URL2="https://www.bing.com"
  
  echo "$(date): checking network"
  
  if ! curl -s --retry 3 --retry-delay 2 --max-time 5 "$URL1" > /dev/null && \
     ! curl -s --retry 3 --retry-delay 2 --max-time 5 "$URL2" > /dev/null; then
      echo "$(date): both checks failed, restarting network"
      systemctl restart networking
      curl -d "Network restarted on $(hostname) at $(date)" https://ntfy.sh/{your channel}
  fi
  

  So far, the script has restarted the network 5 times across 6 servers over the past year.

  Wouldn't it be better to use ping? That will test both DNS lookups and reachability and is simpler than HTTPS.