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.

BuyVM Support Not Responding

BuyVM by default blocked STMP ports so my website couldn't get Amazon to send verification emails for users to log in. I asked BuyVM to unblock the ports, and have changed my domain's TXT record according to their first response and let them know to check it. But now it's been more than 48 hours without a response, and without them unblocking the port.

It's a cheap VPS so there might not be so timely resolutions, is there any BuyVM support here that can answer what's the usual time to resolve issues like this with BuyVM?

Comments

  • edited September 2024

    Thank you for contacting LET support. Your awaiting time has been doubled.

    Thanked by 2Carlin0 hsr
  • FranciscoFrancisco Top Host, Host Rep, Veteran
    edited September 2024

    When did you put in a ticket? We have pretty damn close to 24 hour coverage these days with maybe a small gap in the mornings.

    Akash would be on at this point.

    Get me a ticket ID. It’s possible they were wanting my feedback on it and I missed it in my queue.

    Francisco

    Thanked by 1Frameworks
  • @TheGreatOakley said:
    Thank you for contacting LET support. Your awaiting time has been doubled.

    Regards

    Thanked by 3emgh allthemtings sh97
  • visluminvislumin Member
    edited September 2024

    @TheGreatOakley said:
    Thank you for contacting LET support. Your awaiting time has been doubled.

    Nah.

  • @Francisco said:
    When did you put in a ticket? We have pretty damn close to 24 hour coverage these days with maybe a small gap in the mornings.

    Akash would be on at this point.

    Get me a ticket ID. It’s possible they were wanting my feedback on it and I missed it in my queue.

    Francisco

    Hello, Francisco, the ticket ID is #812091, I've been trying to reach the support, thanks.

  • Just use a different SMTP server.

    If you are trying to send mails from your own server, in most cases, it won't even reach the audience if they have accounts in those big players. You will be banned as spamming.

    Most people don't use own mail server for a reason.

  • visluminvislumin Member
    edited September 2024

    @itachikonoha said:
    Just use a different SMTP server.

    If you are trying to send mails from your own server, in most cases, it won't even reach the audience if they have accounts in those big players. You will be banned as spamming.

    Most people don't use own mail server for a reason.

    I said I was using Amazon to send the emails. It's Amazon SES (simple email service), but the standard port is 587 to submit the emails to Amazon SES then Amazon would send it out on their servers. It worked fine locally, now it's been three days and I can't get the website to use Amazon to send verification emails.

    let transporter = nodemailer.createTransport({
    host: "email-smtp.us-west-1.amazonaws.com", // Amazon SES SMTP host
    port: 587, // Port (587 for TLS)
    secure: false,
    auth: {
    user: process.env.SES_SMTP_USERNAME,
    pass: process.env.SES_SMTP_PASSWORD,
    },
    tls: {
    rejectUnauthorized: false,
    },
    });

    I probably could use some other methods. But BuyVM said on this forum many years ago they would unblock the ports, didn't expect this to take so long.

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @vislumin said: Hello, Francisco, the ticket ID is #812091, I've been trying to reach the support, thanks.

    >

    Hello,

    You sure? You opened your ticket on Saturday. Leo responded later in the day with the verification. We haven't heard from you since the 7th to see if you added it.

    Go ahead and reply to the ticket and we'll get you sorted, but as of now we've heard nada.

    Francisco

    Thanked by 1yoursunny
  • @vislumin said:

    @itachikonoha said:
    Just use a different SMTP server.

    If you are trying to send mails from your own server, in most cases, it won't even reach the audience if they have accounts in those big players. You will be banned as spamming.

    Most people don't use own mail server for a reason.

    I said I was using Amazon to send the emails. It's Amazon SES (simple email service), but the standard port is 587 to submit the emails to Amazon SES then Amazon would send it out on their servers. It worked fine locally, now it's been three days and I can't get the website to use Amazon to send verification emails.

    let transporter = nodemailer.createTransport({
    host: "email-smtp.us-west-1.amazonaws.com", // Amazon SES SMTP host
    port: 587, // Port (587 for TLS)
    secure: false,
    auth: {
    user: process.env.SES_SMTP_USERNAME,
    pass: process.env.SES_SMTP_PASSWORD,
    },
    tls: {
    rejectUnauthorized: false,
    },
    });

    I probably could use some other methods. But BuyVM said on this forum many years ago they would unblock the ports, didn't expect this to take so long.

    What I don't understand is.... why you need to open the port 25 on your server when you are sending mails through amazon ses.

    You are porbably hitting the rate limits. Can you connect to the Amazon SES endpoint from the terminal successfully?

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @itachikonoha said: What I don't understand is.... why you need to open the port 25 on your server when you are sending mails through amazon ses.

    We aren't stateful in our port blocks. We simply do a hard drop of 'any traffic sourcing from port 25/587/465/2525, regardless of direction, is dropped'

    Francisco

  • @Francisco said:

    @vislumin said: Hello, Francisco, the ticket ID is #812091, I've been trying to reach the support, thanks.

    >

    Hello,

    You sure? You opened your ticket on Saturday. Leo responded later in the day with the verification. We haven't heard from you since the 7th to see if you added it.

    Go ahead and reply to the ticket and we'll get you sorted, but as of now we've heard nada.

    Francisco

    Oh, my bad. I sent the 'TXT update completed' info etc back when I saw the reply in my email box. Didn't know it's an un-monitored email. Glad I came here, thank you. I will send the reply on BuyVM portal now.

  • FranciscoFrancisco Top Host, Host Rep, Veteran
    edited September 2024

    @vislumin said:
    Oh, my bad. I sent the 'TXT update completed' info etc back when I saw the reply in my email box. Didn't know it's an un-monitored email. Glad I came here, thank you. I will send the reply on BuyVM portal now.

    Thanks friend.

    Francisco

Sign In or Register to comment.