Paul

We are working on domain management, but it's a big task and we didn't want it to prevent us from releasing other smaller items. We'll continue pushing out regular updates, and include the domain management system as soon as it's ready. We'll reach out to all of you for testing once we get to that point.

Sounds good, and I'm curious why MXroute is refusing to send for the root domain. Thanks for filling us in if you get answers from them!

If email at those sub-domains work, but not the root domain, and both instances you were using MXroute, I think we can assume that the connection details are correct. I think we can also assume that it's likely MXroute is rejecting the email. Do they provide logs in their panel? Some do, like Mailgun. You can do a simple test by signing up for a free Mailgun account - https://www.mailgun.com, they allow something like 12k emails/month for free. Your Blesta settings would be something like: Delivery Method: SMTP SMTP Security: TLS SMTP Host: smtp.mailgun.org SMTP Port: 587 SMTP User: Your user, usually something like postmaster@mg.yourdomain.com SMTP Pass: Your password If it works, then you've narrowed it down to an issue with MXroute, and can use it as evidence in your ticket with them. Or, you can just continue to use Mailgun.

Make sure your uploads directory exists and is defined under Settings > System > General: Uploads Directory. Some tips: - The uploads directory should be above your document root or public_html directory so that it's not accessible directly via the web. - A common path to the uploads directory would be something like: **/home/user/uploads/** - Make sure the uploads directory is writable by your web server and cron users. 755 permissions are usually sufficient, but you may need to set it to 777 - Inside the uploads directory, you should have a directory called 1 (for the company ID), and system. - Plugins typically create their own directories within your company ID directory, but you may need to create them manually. These are the directories you should have under uploads: └── uploads ├── 1 │ ├── download_files │ ├── invoices │ ├── mass_mailer_files │ └── support_manager_files └── system

Are you using PHP Mail or SMTP? (Settings > Company > Emails > Mail Settings) If using PHP, I'd suggest trying SMTP. Possible reasons could be a bad mail server configuration, DKIM/SPF records that are not friendly. Do you have access to your mail server logs? If so, what does that show?

I'm not able to reproduce. Did you do a fresh install or upgrade? Do you have any custom extensions? What version of PHP is it?

Blesta version 4.1.0-b1 (BETA 1) is now available. You can download it from right here (Client Area Login Required). This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1. For older releases see all Change Logs.

A new Yandex gateway (alpha) is available for testing. This is a Russian payment gateway for accepting the RUB currency. To install, download the attached yandex.zip, unzip and upload the "yandex" directory to ~/components/gateways/nonmerchant/ and visit Settings > Company > Payment Gateways to install and configure. yandex.zip

https://docs.blesta.com/display/user/cPanel#cPanel-MovingcPanelAccounts

You are right, whoops, I copied the wrong link and didn't even notice. Thanks for the save.

We released a Virtualmin module on our Github, you can get it here https://github.com/blesta/module-tcadmin

We have a build in QA right now, so most likely Monday or Tuesday for a beta 1 release.

Do you use Skrill? If so, you may have received an email from them that says something like: We are updating Skrill for Blesta 4.1 to use the new API endpoint, but if you need to use the new endpoint before you upgrade to 4.1, you can use the attached file. This is currently a test release, so please make sure it works for you before leaving it in place. Backup ~/components/gateways/nonmerchant/skrill/lib/skrill_api.php Upload the attached file, overwriting the one above Test skrill_api.php

I think we had to modify H2O to get it to work with PHP 7. How does dwoo compare? Are there any others you think we should evaluate as well?

I set up an ISPConfig server and have someone working on a module. Once we have something to test, I'll get it to you. Man, I *really* wish ISPConfig had a bash installer. Their install docs take an hour and have you installing individual packages, compiling libraries, updating config files, before you even get to the part where you install ISPConfig. I think more people would use it if the installer handled all of that.

You should tweet that

Where can the source for the module be obtained? Perhaps we should write and release an official ISPConfig module. Would you be willing to help test it?

@Denroc CORE-2417 It may be in 4.1

We are continuing to make other changes, and the importer will be updated in 4.1.

Did you check the module log? Tools > Logs > Module tab. Also, if you are running v4, are you running 4.0.1? There was a bug fixed in 4.0.1 that could solve the issue for you if you're running 4.0.0.

Glad it's working for you. Just FYI for anyone with an urgent license issue where the license was purchased directly from us. Please open a ticket. Critical is best for a license issue if a re-issue does not solve it. One of only a few reasons Critical is appropriate. If you purchased your license from a reseller, please contact the reseller first. If you contact us, we will need your license key and your email must match what's in the whois for the domain.

Yep, you can forget about umlauts and such. It's the reason we defaulted to the font that we did. But if you don't need those, helvetica works great. It's why we included it.

We updated the WHMCS importer today to resolve some issues for a customer migrating from WHMCS 7.1. The change should be in 4.1, but I'm adding it here on the forums in case anyone has trouble importing and wants to give it a spin. whmcs_migrator.php Download the file, and upload it to ~/plugins/import_manager/components/migrators/whmcs/ overwriting the whmcs_migrator.php file that is there. Run the import with System.debug and error reporting disabled in your ~/config/blesta.php config file, which is the default state.

I've alerted @Jono about this, hopefully he can make the change to the documentation.

Config options are not converted. It gets very complicated. We may have another look at this in the future.