If you are on a cPanel server that was recently migrated to DirectAdmin and experiencing any oddities, this post is to help you understand what has changed, what is expected, and how to work with it.

Mostly we hear from customers who used the “Login to cPanel” link at portal.mxroute.com, and now notice it missing. If you had your cPanel user/pass from signup, this would still function at the same URL that was previously used for cPanel (https://{oldservername}:2083). If you don’t know your cPanel username/password, you can log in at portal.mxroute.com, click on the product name around the middle of the page (will be named “DACPANELTRANSITION”), and use this guide to set a new DA password:

Reset DirectAdmin Password

After that, around the bottom of that same page where you clicked “Change Password” you will see a “Login to DirectAdmin” button. We have some documentation for using DirectAdmin here: https://mxroute.com/docs-category/directadmin/

You may notice some of your email clients reindexing emails. This should be normal, and should clear up on it’s own. If you had email filters set in cPanel, you can configure these via Roundcube (link in DirectAdmin). Hopefully this transition wasn’t too bumpy, but was necessary to bring you out of an aging server that wasn’t handling it’s workload well, while simultaneously bringing you into the new product iteration that we believe you will find much better.

Other things of note:

  • It’s possible that some Roundcube contacts didn’t convert.
  • Filters you had configured in cPanel could not be imported. They can be configured via Roundcube in Settings > Filters.
  • The old webmail URL still works (https://{servername}:2096)
  • POP3 checks may act weird for one sync, and then it’s done.
  • If for some reason your custom mail/webmail subdomains are suddenly not showing a working SSL certificate, use this guide: https://mxroutehelp.com/index.php/2019/08/25/custom-webmail-pop-imap-smtp-domain/
  • If your outdated copy of Outlook suddenly isn’t working with SSL, you’ve had an unknown expiration date for a while and I want to note that this would have happened any day now with or without a migration. Old versions of email software are generally not capable of secure SSL connections. If it can’t connect securely, you should use non-SSL. It is generally considered a security flaw when the server allows it to claim it has a secure connection when it is incapable of an actual one.
  • Folders that were subfolders of INBOX may now be one level higher. So /INBOX/Sent may now be /Sent.

As a reminder, these ports were and are still available:

IMAP SSL: 993
IMAP Non-SSL: 143
POP3 SSL: 995
POP3 Non-SSL: 110
SMTP SSL: 465
SMTP Non-SSL/STARTTLS: 25, 587, 2525

We apologize if this is a severe inconvenience. By consolidating our product into one iteration, we’re laying the foundation for incredible improvements to the product. Our goal was always to continually improve the product and bring you along for the ride, never charging you more but always providing better service. There may be some minor hiccups as we cross major milestones like this one, but we’ll do our best to smooth it out and make it as painless as possible.