Howdy, Stranger!

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


BAGEVM - Germany KVM VPS | Double Bandwidth Starting at $3.21 | AMD Ryzen 7950X | DDR5 - Page 2
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.

BAGEVM - Germany KVM VPS | Double Bandwidth Starting at $3.21 | AMD Ryzen 7950X | DDR5

2

Comments

  • bagebage Member, Patron Provider

    @hong511320 said:
    Invoice 4169 for double bandwidth, thanks

    Its already doubled.
    If you have any other questions, please contact us

  • minglemingle Member

    Invoice 3928 for double bandwidth, thanks

  • bagebage Member, Patron Provider

    @mingle said:
    Invoice 3928 for double bandwidth, thanks

    Its already doubled.
    If you have any other questions, please contact us

    Thanked by 1mingle
  • Invoice 4433 for double bandwidth, thanks

  • bagebage Member, Patron Provider

    @bananaspeed said:
    Invoice 4433 for double bandwidth, thanks

    Its already doubled.
    If you have any other questions, please contact us

  • TheLinuxBugTheLinuxBug Member
    edited August 31

    You know, I haven't posted on this forum for a while now, however, I just had the most bullshit filled experience with this host so I am willing to make an exception and post.

    I decided to try this host out on a whim, for the most part the setup experience was good, however, what is not disclosed and completely unacceptable for a VPS host is all outbound connections on port 22 are blocked. That's right, you can't SSH to any other server that uses port 22 from the server, they literally block port 22 outbound.

    When ticketed, they told me they would not unblock the port, because basically they can't be bothered to maintain their network at all, so instead they decided they will just block the most commonly used and needed port from being able to be used.

    Upon confronting them about this, instead of working with me as a customer, they decided to terminate and refund my service immediately, without returning the additional transactions fees they charged me for the service, so essentially scamming me for $0.91 they didn't return.

    I have never had such a scammy, scummy experience with a host here and I have even signed-up with summer hosts here that have run off with my money.

    My advice would be to avoid this host at all cost as they don't seem to know how to run a network, lack any reasonable customer service and will essentially scam you for money on a refund.

    My 2 cents.

    Cheers!

    Thanked by 1lanefu
  • bagebage Member, Patron Provider

    @TheLinuxBug said:
    You know, I haven't posted on this forum for a while now, however, I just had the most bullshit filled experience with this host so I am willing to make an exception and post.

    I decided to try this host out on a whim, for the most part the setup experience was good, however, what is not disclosed and completely unacceptable for a VPS host is all outbound connections on port 22 are blocked. That's right, you can't SSH to any other server that uses port 22 from the server, they literally block port 22 outbound.

    When ticketed, they told me they would not unblock the port, because basically they can't be bothered to maintain their network at all, so instead they decided they will just block the most commonly used and needed port from being able to be used.

    Upon confronting them about this, instead of working with me as a customer, they decided to terminate and refund my service immediately, without returning the additional transactions fees they charged me for the service, so essentially scamming me for $0.91 they didn't return.

    I have never had such a scammy, scummy experience with a host here and I have even signed-up with summer hosts here that have run off with my money.

    My advice would be to avoid this host at all cost as they don't seem to know how to run a network, lack any reasonable customer service and will essentially scam you for money on a refund.

    My 2 cents.

    Cheers!

    Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

  • TheLinuxBugTheLinuxBug Member
    edited August 31

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

  • bagebage Member, Patron Provider

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    If you feel that our service experience is very bad, we can only say sorry for not opening port 22 for you, but it is Paypal's setting to charge a handling fee for all receipts and refunds, and we also declare that we do not bear this part of the fee. At the same time, we have also seen your dispute, and we also think that you are not a good customer, thank you.

  • @bage said: If you feel that our service experience is very bad, we can only say sorry for not opening port 22 for you, but it is Paypal's setting to charge a handling fee for all receipts and refunds, and we also declare that we do not bear this part of the fee. At the same time, we have also seen your dispute, and we also think that you are not a good customer, thank you.

    You are providing me no service but took my money, it doesn't matter that you want to charge a fee, if you refund someone, you refund the whole amount.

    Also, I truly advise you to review the terms you agreed to at Paypal regarding charging fees for using their service that are more than your other merchants. While I may be a bad customer in your eyes, I have just given you $20.00 worth of advice which I suggest you take seriously before it costs you more than just my dispute.

    I advise you also revise your approach to customer service, if this is how you continue, I have a feeling this will become a repeat issue for you.

    Cheers!

    Thanked by 1lanefu
  • @bage said:

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    If you feel that our service experience is very bad, we can only say sorry for not opening port 22 for you, but it is Paypal's setting to charge a handling fee for all receipts and refunds, and we also declare that we do not bear this part of the fee. At the same time, we have also seen your dispute, and we also think that you are not a good customer, thank you.

    Why apologize for not opening port 22? Why not clarify why this 'rule' isn't detailed on your website or post? The port is the default and still widely used, although some prefer to use other ports.

  • bagebage Member, Patron Provider

    @Maelstrom36 said:

    @bage said:

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    @TheLinuxBug said:

    @bage said: Hello
    We will not bear any payment and refund fees at this time. The current fee of Pyapl is 4%+0.49
    you can find at Paypal site.

    Maybe not at this time, but once the Paypal dispute is completed, I have this odd feeling you will be obligated to return my money.

    Especially seeing as it is against Paypal terms of service to place a transaction fee on using their payment gateway when there is not an equal fee applied to your other merchants.

    I also love how you re-enforce my point about your poor customer service.

    Cheers!

    If you feel that our service experience is very bad, we can only say sorry for not opening port 22 for you, but it is Paypal's setting to charge a handling fee for all receipts and refunds, and we also declare that we do not bear this part of the fee. At the same time, we have also seen your dispute, and we also think that you are not a good customer, thank you.

    Why apologize for not opening port 22? Why not clarify why this 'rule' isn't detailed on your website or post? The port is the default and still widely used, although some prefer to use other ports.

    We have responded in our website ticket because there will be many unclear 22 port scans that cause many uncertain complaints, but he wanted to refund in his reply, so we did not give her further explanation and refunded her directly.

  • bagebage Member, Patron Provider

    @TheLinuxBug said:

    @bage said: If you feel that our service experience is very bad, we can only say sorry for not opening port 22 for you, but it is Paypal's setting to charge a handling fee for all receipts and refunds, and we also declare that we do not bear this part of the fee. At the same time, we have also seen your dispute, and we also think that you are not a good customer, thank you.

    You are providing me no service but took my money, it doesn't matter that you want to charge a fee, if you refund someone, you refund the whole amount.

    Also, I truly advise you to review the terms you agreed to at Paypal regarding charging fees for using their service that are more than your other merchants. While I may be a bad customer in your eyes, I have just given you $20.00 worth of advice which I suggest you take seriously before it costs you more than just my dispute.

    I advise you also revise your approach to customer service, if this is how you continue, I have a feeling this will become a repeat issue for you.

    Cheers!

    We will not argue with you, we will mark the handling fee issue in all POSTs. If you do not need to pay the handling fee, please choose other payment methods.

  • lanefulanefu Member

    Amazing. Blocking outbound 22 is insane, but I guess there's enough customers out there don't need to ssh for...ssh, git, SFTP, rsync, borgbackup, etc that this is practical for the provider?

  • bagebage Member, Patron Provider

    @lanefu said:
    Amazing. Blocking outbound 22 is insane, but I guess there's enough customers out there don't need to ssh for...ssh, git, SFTP, rsync, borgbackup, etc that this is practical for the provider?

    Statement: We do not prohibit inbound ssh port 22, but prohibit connecting to other IP port 22 within the instance. We do not block any inbound port 22.
    At the same time, our port 22 can be released. The above person wants to refund, so no further communication was conducted.

  • @bage said:

    @lanefu said:
    Amazing. Blocking outbound 22 is insane, but I guess there's enough customers out there don't need to ssh for...ssh, git, SFTP, rsync, borgbackup, etc that this is practical for the provider?

    Statement: We do not prohibit inbound ssh port 22, but prohibit connecting to other IP port 22 within the instance. We do not block any inbound port 22.
    At the same time, our port 22 can be released. The above person wants to refund, so no further communication was conducted.

    Can you explain why you're blocking port 22? Port 25 I understand, but outgoing 22 is bonkers.

  • MumblyMumbly Member
    edited August 31

    @bage said: The above person wants to refund, so no further communication was conducted.

    He said the exact opposite - that you were the one who broke the contract without further communication about the issue.

    @TheLinuxBug said: When ticketed, they told me they would not unblock the port, because basically they can't be bothered to maintain their network at all, so instead they decided they will just block the most commonly used and needed port from being able to be used.

    Upon confronting them about this, instead of working with me as a customer, they decided to terminate and refund my service immediately, without returning the additional transactions fees ...

  • bagebage Member, Patron Provider

    @Cameron said:

    @bage said:

    @lanefu said:
    Amazing. Blocking outbound 22 is insane, but I guess there's enough customers out there don't need to ssh for...ssh, git, SFTP, rsync, borgbackup, etc that this is practical for the provider?

    Statement: We do not prohibit inbound ssh port 22, but prohibit connecting to other IP port 22 within the instance. We do not block any inbound port 22.
    At the same time, our port 22 can be released. The above person wants to refund, so no further communication was conducted.

    Can you explain why you're blocking port 22? Port 25 I understand, but outgoing 22 is bonkers.

    Because we have encountered customers from let who use our network to send outbound 22 port blasting and scanning, we have received many abuse, so we block outbound port 22 by default.
    At the same time, when there are abuse, it will cause trouble to the IP owner, and the IP quality will also decline

  • bagebage Member, Patron Provider
    edited August 31

    @Mumbly said:

    @bage said: The above person wants to refund, so no further communication was conducted.

    He said the exact opposite - that you were the one who broke the contract without further communication about the issue.

    @TheLinuxBug said: When ticketed, they told me they would not unblock the port, because basically they can't be bothered to maintain their network at all, so instead they decided they will just block the most commonly used and needed port from being able to be used.

    Upon confronting them about this, instead of working with me as a customer, they decided to terminate and refund my service immediately, without returning the additional transactions fees ...

    Since he wants a refund, we will not make any efforts to retain him.

  • MumblyMumbly Member
    edited August 31

    @bage said: we will not make any efforts to retain him

    This is getting worse and worse....
    Remove at least the client’s personal data (real name) if you already feel the need to post the ticket publicly.

  • bagebage Member, Patron Provider

    @Mumbly said:

    @bage said: we will not make any efforts to retain him

    This is getting worse and worse....
    Remove at least the client’s personal data (real name) if you already feel the need to post the ticket publicly.

    Sorry, I didn't notice he had his name attached to it at the bottom, I was only paying attention to the left side. We deleted it.

  • TheLinuxBugTheLinuxBug Member
    edited August 31

    So you expose my personal information in public after you go ahead and issue the rest of the refund?

    You know, just wow. I was gonna leave it there but that's just another example of your poor skills running a business and at customer service.. not to mention a lack of ethics / morals.

    I stand by what was said in my ticket, so no shame there, but I don't know how sharing this helped you at all, other than to expose my personal information?

    My advice would be to avoid this host at all cost as they don't seem to know how to run a business, a network, lack any reasonable customer service and will essentially TRY to scam you for money on a refund if you don't point out they will lose the dispute in public. Then they will expose your personal information on a public forum.

    I don't even know what more to say... it doesn't get much worse than this...

    Thanked by 1Cameron
  • bagebage Member, Patron Provider

    @TheLinuxBug said:
    So you expose my personal information in public after you go ahead and issue the rest of the refund?

    You know, just wow. I was gonna leave it there but that's just another example of your poor skills running a business and at customer service.. not to mention a lack of ethics / morals.

    I stand by what was said in my ticket, so no shame there, but I don't know how sharing this helped you at all, other than to expose my personal information?

    My advice would be to avoid this host at all cost as they don't seem to know how to run a business, a network, lack any reasonable customer service and will essentially TRY to scam you for money on a refund if you don't point out they will lose the dispute in public. Then they will expose your personal information on a public forum.

    I don't even know what more to say... it doesn't get much worse than this...

    We did not publish your information, we just sent the original content of the ticket, but we did not notice that you overwrote your name at the bottom of the ticket content.

  • SilvestSilvest Member
    edited August 31

    @TheLinuxBug Well it's not uncommon to not refund transaction fee's.

    @bage

    In your post you do mention

    Port 25: Blocked! Strictly no bulk or unsolicited mailing.
    

    Why not add outbound port 22 to the list as well?
    You should educate your (future) clients before hand instead of letting them find out the hard way

  • how about dcma sir?

  • TheLinuxBugTheLinuxBug Member
    edited August 31

    @bage said: We did not publish your information, we just sent the original content of the ticket, but we did not notice that you overwrote your name at the bottom of the ticket content.

    So let me get this straight, it's my fault you took a screen shot of the ticket and then posted it here without editing out my personal information?

    Are you mentally handicapped? I am starting to become concerned you are not well, as common sense and logic seem to fail you.

    You posted the image here with my information in it and while you think you were quick, there were people who copied that image before you changed it, because someone sent me a copy of it. YOU exposed my personal information here in public. YOU did it, it wasn't magic. I didn't come to where you are and force you to post it.

    @Silvest said: @TheLinuxBug Well it's not uncommon to not refund transaction fee's.

    Have you seen how long I have been on this forum? I have more than 60 different VPS / Hosting services concurrently and I have NEVER encountered a case where the merchant couldn't supply the product they sold and then tried not to return my money because they have placed fees on the transaction (which the merchant isn't even following Paypal's terms of service, which requires all merchants services on your site to have the same processing fees, you can't charge more to use Paypal than other merchants).

    I am sorry, though, if you have let some other providers rip you off in the past and accepted it. If you truly feel that it is okay for a company you are doing business with to not supply you a product but also take your money, then that's on you.

    My 2 cents.

    Cheers!

    Thanked by 1fendix
  • bagebage Member, Patron Provider

    @horasjey said:
    how about dcma sir?

    Sorry, We not Allowd.

  • bagebage Member, Patron Provider

    @bage

    In your post you do mention

    Port 25: Blocked! Strictly no bulk or unsolicited mailing.
    

    Why not add outbound port 22 to the list as well?
    You should educate your (future) clients before hand instead of letting them find out the hard way

    Thank you, we did not block outbound port 22 when we released the offer, but until the abuse appeared, we had to urgently add a new firewall to block the port, and we will clarify all the rules later.

  • The promotion code entered has expired

  • bagebage Member, Patron Provider

    @bananaspeed said:
    The promotion code entered has expired

    Thank you for your attention. Yes, the offer ends on 09/01/2024. You can wait for our next promotion.

Sign In or Register to comment.