Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Banned by xhosts web hosting for typing 'sudo' command once

24567

Comments

  • wadhahwadhah Member, Host Rep
    edited March 2025

    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    Thanked by 2gbzret4d Frameworks
  • @Chellii said: I'm not that person! I definitely not run any kind of VPN service!

    That's totally something someone who runs a VPN service would say.

    Thanked by 3wadhah WSWD imok
  • xaocxaoc Member

    @wadhah said:
    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    What the fuck?

  • Their service -> their rules
    You violated -> just accept it
    C'mon, be a man!

  • @shallownorthdakota said:

    @Chellii said: I'm not that person! I definitely not run any kind of VPN service!

    That's totally something someone who runs a VPN service would say.

    well, I cannot proof anything about that, even the ticket and customer service not accuse me about that, some LETs just mix the wrong person from other posts.

  • @wadhah said:
    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    Am I just be labeled?

  • @Chellii said:
    This was my first time buying a web hosting service.

    When I used the SSH function in xhosts, the terminal showed:

    /usr/local/bin/composer2
    
    Please do not use 'sudo' or leave your home directory.
    
    Have a nice day!
    

    Out of curiosity, I just typed a single word, 'sudo'. I was expecting it would show some kind of forbidden message. But the SSH disconnected immediately and I couldn't reconnect.

    Then I opened a ticket, trying to find out what happened. After I explained what I did, I clarified that I did not use any VPN service. I received a forced refund.

    It's my fault for typing 'sudo' (literally just the word 'sudo', with no other commands following it), but it's ridiculous to ban me and issue a refund for this!

    Couldn't you have built a simple filter instead?

    They said:

    Before your edited command you had stated that you wish to "test what is allowed and is not allowed" as explained in the ticket an account that will be potentially becoming blocked on a regular basis is not feasible for us to spend hours ahead having SSH unblocked. It is easier to refund you now and allow you to switch to a provider more suited to your needs.

    By the way, I didn't try to use or run any scripts or VPN services - they can verify this in the SSH logs. I only tried a few cmd like 'ls','pwd','python -V' and 'sudo'.

    Be aware, everyone! If you accidentally type the wrong command like 'sudo' someday, you'll be immediately banned and given a forced refund.

    Fuck around and find out.
    Get a vps like already suggested here.

    Btw taiwan is a free and independend country.
    Tiananmen Square was a massacre done by the chinese communists.

    Thanked by 1jnd
  • @rostin said:
    Their service -> their rules
    You violated -> just accept it
    C'mon, be a man!

    They did not put any kind of these rule on their websites.

    "sudo onee,banned forever"

  • @Chellii said:

    @rostin said:
    Their service -> their rules
    You violated -> just accept it
    C'mon, be a man!

    They did not put any kind of these rule on their websites.

    "sudo onee,banned forever"

    You got your money back so stop crying.
    There are about 3 million similar hosters why not try them?

  • angstromangstrom Moderator

    @sillycat said:
    I actually wonder how this works. Do they have their own binary that they replace sudo with? Do they schizophrenically scan every users .bash_history every 30 seconds?

    Since one can turn off history in bash with set +o history, I doubt that it's the latter

    Something like the former seems more likely to me (but perhaps a sudo script instead)

  • MumblyMumbly Member
    edited March 2025

    Yeah, as if typing "sudo" would automagically hack the server or something. :D

    If that's even remotely a security threat on a professional webosting server, the host has much bigger problems than someone randomly typing sudo.

  • @Chellii said:

    @rostin said:
    Their service -> their rules
    You violated -> just accept it
    C'mon, be a man!

    They did not put any kind of these rule on their websites.

    "sudo onee,banned forever"

    I think the reason you got banned or refunded is, when they created a ticket and asked you how you planning to use the service, you weren’t clear with your answer or was vague.

    Thanked by 1mandala
  • air4xair4x Member

    Using sudo when running shell commands would be part of one's scripts, tutorials and documentation of programs. Seems it is almost inevitable that people would make a mistake of using it even in jailed shells. But contacting support and saying you were testing what was allowed and not allowed seems like asking for trouble.

    Thanked by 1mandala
  • @barbaros said:

    @Chellii said:

    @rostin said:
    Their service -> their rules
    You violated -> just accept it
    C'mon, be a man!

    They did not put any kind of these rule on their websites.

    "sudo onee,banned forever"

    I think the reason you got banned or refunded is, when they created a ticket and asked you how you planning to use the service, you weren’t clear with your answer or was vague.

    I think they recognize me wrong as other person. They said I was post in LET that "wishing to test what is forbidden",which I did‘t.

  • @air4x said:
    Using sudo when running shell commands would be part of one's scripts, tutorials and documentation of programs. Seems it is almost inevitable that people would make a mistake of using it even in jailed shells. But contacting support and saying you were testing what was allowed and not allowed seems like asking for trouble.

    I think they recognize me wrong as other person. They said I was post in LET that "wishing to test what is forbidden",which I did‘t.

    I do not think 'ls','pwd' is some king trouble testing

  • @Mumbly said:
    Yeah, as if typing "sudo" would automagically hack the server or something. :D

    If that's even remotely a security threat on a professional webosting server, the host has much bigger problems than someone randomly typing sudo.

    it is obvious to assume that xhosts are full professionals when it comes to security.

  • olokeoloke Member, Host Rep

    That's "-1 abuse tolerance"

    Thanked by 1vingohost
  • angstromangstrom Moderator

    @wadhah said:
    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    To be honest, I find that this is a kind of a borderline case, especially if the OP was just innocently experimenting, as he claims. (But naturally, I/we can't tell what the OP's intentions were)

    I imagine that inexpensive lifetime deals in shared hosting is a tricky business and can easily attract all sorts of potential abusers, so I can also understand the provider's perspective here (and especially the need to act quickly)

    In addition, it probably doesn't hurt if potential customers are potentially more aware that they shouldn't use this web hosting to execute sudo via ssh

    In any case, the OP received a refund, so he can also just move on

  • wadhahwadhah Member, Host Rep

    @angstrom said:

    @wadhah said:
    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    To be honest, I find that this is a kind of a borderline case, especially if the OP was just innocently experimenting, as he claims. (But naturally, I/we can't tell what the OP's intentions were)

    I imagine that inexpensive lifetime deals in shared hosting is a tricky business and can easily attract all sorts of potential abusers, so I can also understand the provider's perspective here (and especially the need to act quickly)

    In addition, it probably doesn't hurt if potential customers are potentially more aware that they shouldn't use this web hosting to execute sudo via ssh

    In any case, the OP received a refund, so he can also just move on

    Fair and understandable.

    Thanked by 2angstrom Blembim
  • @oloke said:
    That's "-1 abuse tolerance"

    When I'm curious about what will happened if i type the 'sudo', The only word that not in my mind, it‘s 'abuse'

  • @angstrom said:

    @wadhah said:
    @angstrom can this be moved to offtopic (to avoid search engine indexing)? it is just intended as a blackmail attempt from a clearly in the wrong user

    To be honest, I find that this is a kind of a borderline case, especially if the OP was just innocently experimenting, as he claims. (But naturally, I/we can't tell what the OP's intentions were)

    I imagine that inexpensive lifetime deals in shared hosting is a tricky business and can easily attract all sorts of potential abusers, so I can also understand the provider's perspective here (and especially the need to act quickly)

    In addition, it probably doesn't hurt if potential customers are potentially more aware that they shouldn't use this web hosting to execute sudo via ssh

    In any case, the OP received a refund, so he can also just move on

    Thanks for your reply.

    This my first discussion post in the LET, I'm not asking for additional compensation, just want to share what happened to me. And I think it's Irresponsible for the xhosts. So I post this in the 'Review'. Just want to share more info to others.

  • @xhosts, however, is intolerably silent on the subject of the security of its systems. this is frightening, if not downright discouraging.

    Thanked by 2yoursunny Peppery9
  • After I post in LETs, xhosts ban my account, which even cannot open the tickets page.

    Good work for you

  • kenjing789kenjing789 Member
    edited March 2025

    TLDR: User wrong , xHost right if the story on xHost side is real (xHost was right at start tho)

    https://lowendtalk.com/discussion/comment/4366088/#Comment_4366088

  • suyadi92suyadi92 Member
    edited March 2025

    @Chellii said:
    I do not know your experience.

    But for myself, in these years of usage of linux, it's truly happened few times that I copied the wrong cmd then run.

    ok

    Thanked by 1imok
  • @kenjing789 said:
    TLDR: User wrong , xHost right if the story on xHost side is real (xHost was right at start tho)

    https://lowendtalk.com/discussion/comment/4366088/#Comment_4366088

    Well, I think I cannot proof anymore, I did not post "test what is allowed and is not allowed". Seems there no way for me to proof that.

  • xHostsxHosts Member, Patron Provider

    You connected to SSH and it advises do not use sudo command, we understand it can be done in error and that is not an issue. We asked what you intended to use SSH to gather background information to check your use case would suitable going forward to ensure we are not wasting each others time.

    The replies you gave had been vague that you would not give a clear and straight forward answer, when someone is being vague refuses to give a simple answer that is a red flag.

    When we consider that and other aspects of the account and activity here on let at the exact time you had been responding ticket to another user who also abused SSH, you since edited that reply with an update that you advise you wish to test what is and is not allowed.

    We have had people who became blocked on SSH, discussed the issues and their account block was lifted and they have no issues, when a person is evasive and cannot explain what they intend to do and risk of becoming blocked over and over again it is not worth the time of ongoing tickets over an issue such as this.

    Thanked by 1MetroVPS_NMP
  • angstromangstrom Moderator

    People, just to be clear, there seem to be two different users, the OP of this thread (= @Chellii ) and another user, @letstayfree , who posted https://lowendtalk.com/discussion/comment/4352066/#Comment_4352066

    At the moment, my/our working assumption is that these are two different users

    Thanked by 1nghialele
  • @angstrom said:
    People, just to be clear, there seem to be two different users, the OP of this thread (= @Chellii ) and another user, @letstayfree , who posted https://lowendtalk.com/discussion/comment/4352066/#Comment_4352066

    At the moment, my/our working assumption is that these are two different users

    Thanks for your clarification, I think @xHosts also make a mistake about that.

  • @xHosts said:
    You connected to SSH and it advises do not use sudo command, we understand it can be done in error and that is not an issue. We asked what you intended to use SSH to gather background information to check your use case would suitable going forward to ensure we are not wasting each others time.

    The replies you gave had been vague that you would not give a clear and straight forward answer, when someone is being vague refuses to give a simple answer that is a red flag.

    When we consider that and other aspects of the account and activity here on let at the exact time you had been responding ticket to another user who also abused SSH, you since edited that reply with an update that you advise you wish to test what is and is not allowed.

    We have had people who became blocked on SSH, discussed the issues and their account block was lifted and they have no issues, when a person is evasive and cannot explain what they intend to do and risk of becoming blocked over and over again it is not worth the time of ongoing tickets over an issue such as this.

    'vague' cannot be a reason.

    It's true I was edit my post in that discussion, but as you see, the edition is due to my poor English, not what kind of "test what is allowed and is not allowed". You can check the SSH log, I only use few basic cmd, it cannot be "test what is allowed and is not allowed".

    I did not post anything like that! You cannot just make up things!

    I think you may mix me and 'letstayfree'.

Sign In or Register to comment.