★ JUST.HOSTING ★ 18 VPS LOCATIONS ★ LONDON / FRANKFURT / ZURICH / TORONTO / NYC ★ UP TO 40% OFF ★

Comments

• usedacid Member

  January 23

  GLWS

  Thanked by 1antonpa
• JohnFilch123 Member

  January 23

  No 🇷🇺 Novosibirsk (OVB1), Russia on the list of locations.

  Thanked by 1oloke
• antonpa Member, Patron Provider

  January 28

  @JohnFilch123 said:
  No 🇷🇺 Novosibirsk (OVB1), Russia on the list of locations.

  Hello!
  What do you mean?
• gemini_geek Member

  January 28

  hi, can you tell the actual server location for hel 1 and hel 2 , i want a server closer to hetzner helsinki , which one i should choose ?
• JohnFilch123 Member

  January 28

  @antonpa said: What do you mean?

  When I open a link, OVB1 is not on the list but in this thread it is.
• jusnion Member

  January 28

  Price is getting higher?
• forest Member

  January 28

  @JohnFilch123 said:

  @antonpa said: What do you mean?

  When I open a link, OVB1 is not on the list but in this thread it is.

  I see it. It's right under Poland. You can also reduce the clutter by selecting "cheap" at the top, which will only show promo deals. They list Kazan (KAZ1), Moscow (MOW2), Novosibirsk (OVB1), and St. Petersburg (LED1).
• forest Member

  January 29 edited January 29

  Just a small warning for those considering this provider: Their live chat support is a bot which, while under normal circumstances it not a big deal, can be an issue because it very confidently hallucinates policies that do not exist.

  For example (and this is entirely on me), it assured me that I could purchase extra RAM incrementally for existing services. It went on to assert that I would be able to pay the price difference at any time to upgrade. I went with 1 GB RAM under the impression that I could upgrade it when I needed it, only to be told (by a human) that the bot was wrong and that the only solution would be to upgrade to a much, much more expensive tariff, literally increasing the price by over 4x when all I needed was a mere half gigabyte of RAM.

  Of course, the blame is entirely mine for believing the bot, but it's still a good idea to keep in mind that the helpful AI bots may be hallucinating policies and making aggressive suggestions (for example, encouraging me to try to claim a "loyalty discount" which I am almost certain does not exist). Thankfully, they were willing in the end to make an exception and are allowing me to upgrade the RAM of each of my servers.

  With that said, I still like JustHost. I have three services with them and I plan to get two more relatively soon. The CPU steal can be a bit high on the promo plans and the routing is not always the best, but it's otherwise quite solid with responsive support, very enticing discounts for long-term purchases, and a huge variety of locations with great prices. It is absolutely a wonderful value for the money.

  To @antonpa, it would be nice if you could adjust the prompt for the bot so that it references and links to actual policies rather than making assertions about non-existent policies. That would probably save a lot of future headache.

  Also, please stop selling individual IPv6 addresses. The price that you charge for each additional IPv6 means that you are valuing a single /64, which most providers give free of charge with the service, at $377,581,792,758,742,385 USD per month (~2 cents per IPv6 per month). If you want to draw more people in to make a little extra dough, consider offering a free routed /64 than charging for individual IPv6 addresses. I guarantee that will bring in more money through new customers than you can get by squeezing out a few cents from people who need more than a single /128.

  Thanked by 1rpqu
• JohnFilch123 Member

  January 29

  @forest said: I see it. It's right under Poland. You can also reduce the clutter by selecting "cheap" at the top

  Strange. I still do not see any RU locations. I have got Stockholm under Poland. Switching between All Popular and Premium does not show any RU location either.
• forest Member

  January 29 edited January 29

  @JohnFilch123 said:

  @forest said: I see it. It's right under Poland. You can also reduce the clutter by selecting "cheap" at the top

  Strange. I still do not see any RU locations. I have got Stockholm under Poland. Switching between All Popular and Premium does not show any RU location either.

  Try using https://justhost.ru/, which is what I always use.

  There should be an additional "Cheap" in addition to All, Popular, and Premium. It doesn't show for you?

  Thanked by 1JohnFilch123
• JohnFilch123 Member

  January 29

  @forest said: Try using https://justhost.ru/, which is what I always use.

  Funny, this one works and it is cheaper than even using a discount code. Thanks

  Thanked by 1oloke
• Hotchkiss Member

  January 30 edited January 30

  I wanted to share a recent experience with JustHost that may help others make more informed decisions, especially if you're planning to purchase longer-term VPS or hosting plans.
  A few days ago, my VPS service was suddenly disabled without any prior warning or temporary suspension. The stated reason was that my server was allegedly used (by someone else) to forward spam emails via port 25.（I never sending spam.）

  As soon as I became aware of the issue (through the abuse notification),
  I immediately:

  Submitted delisting/removal requests to the relevant spam reporting organizations (Spamhaus)

  Contacted JustHost support
  Clearly stated that I promise to avoid any mail-related activity going forward, JustHost chose to permanently disable the service rather than apply a temporary block, port restriction, clean reinstall, or any intermediate measure.
  This strict zero-tolerance approach (which appears consistent with their published Anti-Spam Policy stating immediate suspension/termination for any spam-related complaints) meant:
  No opportunity for recovery or mitigation in my case
  Abrupt termination even when the abuse was clearly not initiated by me (likely due to someone exploiting an unsecured service or vulnerability)

  While I understand providers must protect their IP reputation and network from blacklisting, this experience highlighted how quickly and irreversibly a service can be terminated — even for users who respond promptly and were not the source of the problem.
  If you're considering JustHost for anything long-term or mission-critical:
  Be extra cautious with security hardening (especially ports like 25, 465, 587, and any potentially exploitable services)
  Avoid running or exposing any mail-related software unless absolutely necessary
  Have a solid backup and migration plan ready, because recovery options after suspension seem very limited.
  Consider providers with more graduated abuse handling (e.g., temporary port blocks, warnings before full termination)
  This is not intended to attack the company — they have the right to enforce strict policies — but simply a heads-up so others can weigh the risks, particularly for paid periods of several months or years.
  If anyone has had similar (or different) experiences with JustHost's abuse handling, feel free to share. It would help the community get a fuller picture.
  Stay safe and secure out there.

  

  
• forest Member

  January 31 edited January 31

  @Hotchkiss said: The stated reason was that my server was allegedly used (by someone else) to forward spam emails via port 25.（I never sending spam.）

  @Hotchkiss said: Abrupt termination even when the abuse was clearly not initiated by me (likely due to someone exploiting an unsecured service or vulnerability)

  So your server was hacked, and your account was terminated for that? That seems more like a reason to learn how to harden your server than to judge JustHost for their reaction.

  For future reference, if you can't secure your systems, at the very least keep this in /etc/nftables.conf (assuming you run SSH and a web server on standard ports):

  #!/usr/sbin/nft -f
  
  flush ruleset
  
  table inet filter {
      chain input {
          type filter hook input priority filter; policy drop;
          iif lo accept
          ct state { established, related } accept
          ct state new tcp dport { 22, 80, 443 } accept
          icmp type echo-request accept
          icmpv6 type { echo-request, nd-neighbor-solicit, nd-router-advert, nd-neighbor-advert } accept
      }
  
      chain output {
          type filter hook output priority filter; policy accept;
          ct state new tcp dport { 25, 587, 465, 2525 } reject
      }
  
      chain forward {
          type filter hook forward priority filter; policy drop;
      }
  }
  

  And then run systemctl enable --now nftables.service and it will block outgoing mail ports and only allow incoming connections on TCP ports 22, 80, and 443.
• Hotchkiss Member

  January 31

  @forest said:

  @Hotchkiss said: The stated reason was that my server was allegedly used (by someone else) to forward spam emails via port 25.（I never sending spam.）

  @Hotchkiss said: Abrupt termination even when the abuse was clearly not initiated by me (likely due to someone exploiting an unsecured service or vulnerability)

  So your server was hacked, and your account was terminated for that? That seems more like a reason to learn how to harden your server than to judge JustHost for their reaction.

  For future reference, if you can't secure your systems, at the very least keep this in /etc/nftables.conf (assuming you run SSH and a web server on standard ports):

  #!/usr/sbin/nft -f
  
  flush ruleset
  
  table inet filter {
      chain input {
          type filter hook input priority filter; policy drop;
          iif lo accept
          ct state { established, related } accept
          ct state new tcp dport { 22, 80, 443 } accept
          icmp type echo-request accept
          icmpv6 type { echo-request, nd-neighbor-solicit, nd-router-advert, nd-neighbor-advert } accept
      }
  
      chain output {
          type filter hook output priority filter; policy accept;
          ct state new tcp dport { 25, 587, 465, 2525 } reject
      }
  
      chain forward {
          type filter hook forward priority filter; policy drop;
      }
  }
  

  And then run systemctl enable --now nftables.service and it will block outgoing mail ports and only allow incoming connections on TCP ports 22, 80, and 443.

  The server was not hacked. It was likely exploited by other users on the same local network (or LAN/shared VPS node) who abused Poste.io's port 25 to send spam.
  Thank you very much for sharing the nftable config.
• forest Member

  January 31

  @Hotchkiss said: The server was not hacked. It was likely exploited by other users on the same local network (or LAN/shared VPS node) who abused Poste.io's port 25 to send spam.

  That shouldn't be possible. If it came from your public IP, then it would have had to come from something within your server, whether intentionally or not.

  I have been in a situation where a provider got their whole /24 blacklisted and, seeing my IP on the blacklist (as they assigned me an IP in that subnet), they assumed I was also spamming, but that doesn't sound like what is happening here.
• malikshi Member

  January 31

  they're increased 15%,, dang... @antonpa old users affected too?
• xaos Member

  February 23

  Any more promos for this?
• Beanzy Member

  March 10

  Does it feel like the price is even higher than that of big companies?
• emaiI Member

  March 10

  @forest said:

  @Hotchkiss said: The server was not hacked. It was likely exploited by other users on the same local network (or LAN/shared VPS node) who abused Poste.io's port 25 to send spam.

  That shouldn't be possible. If it came from your public IP, then it would have had to come from something within your server, whether intentionally or not.

  I have been in a situation where a provider got their whole /24 blacklisted and, seeing my IP on the blacklist (as they assigned me an IP in that subnet), they assumed I was also spamming, but that doesn't sound like what is happening here.

  Some hosts let you assign whatever IP you want (from their subnet) without paying, sure unlikely it happened but just saying
• axeljump Barred

  April 29

  This is a scam company. Please read about my experience—you absolutely must steer clear!
  https://lowendtalk.com/discussion/216739/scam-alert-justhost-ru-fabricates-fake-refund-evidence-avoid-at-all-costs/p1?new=1