Finally v11.0 Released.!: Page 4 - Enhance Control Panel

Finally v11.0 Released.!

Adam

We have a solution to the dkim issue, there will be a release in 24-48 hours after which you should be safe to update with no risk of dkim being disabled on any of your websites.

kyzoeadmin

Adam Thanks for the update we schedule a updat 48hrs after the release of this version

MediaServe

Adam What about us folks who already updated?

slimx

Adam Hey has this been done or ?

alenguav

DracoBlue Thanks!
I will schedule upgrades for this weekend

fabio

Have you had problems with Smarhost when emails are sent via the site's localhost? After the update the emails are sent but they skip the globally configured smarthost.

xyzulu

fabio Resave the smarthost settings after updating append to 3.0.2 ?

fabio

Yes, but now it works. I had to deactivate, save, refresh the page and then reactivate. But all the submissions have changed... now they go as username@server-hello, ignoring the FROM.

mendozal

I upgraded directly to 3.0.2, and I needed to:

Disable/Enable Smarthost. After the upgrade, enhance was sending emails directly.
Reapply HELO for the email role (+ adding helo for the application role that now can send emails).
(+ the DKIM situation that we all know)

ecknz

Has anyone else encountered these?

When moving sites PHP extensions enabled, Ioncube, and Redis options do not stay enabled if they are set.
SSL certs do not transfer and need to be reissued including mail.
If there is a backup error there is no notification
Backup of emails fail if not on the same server.

AdamM

I know bug 1 and reported it a few months ago. It has not been fixed.

It seems that Enhance has more and more bugs. Maybe it's time to stop with new features and fix old bugs that have been going on for months.

xyzulu

AdamM It seems that Enhance has more and more bugs. Maybe it's time to stop with new features and fix old bugs that have been going on for months.

I think this version was always going to be painful.. since it was a number of major changes in one hit. Still, there are some smaller bugs that would be great to see addressed (many are small dev tasks), but I am still wanting to see control panel replication asap.

AdamM

xyzulu Of course I'm not criticizing. It would simply be useful to fix bugs that have been present for months.

DracoBlue

AdamM I agree, detected errors should be fixed at a fairly quick pace, while development should also move forward. For example, Plesk, which I used, also had a lot of errors from update to update, but these errors were fixed within a few days and an update was released.

tstrand

Update again on the srs_milter.service issue.
Turns out that if you have servers in the cluster that only runs for example DB/NS/backup roles the srs_milter.service error message will continue to spam and slowly eat up your diskspace.

I guess it should be save to disable that service on those servers?

systemctl stop srs_milter.service
systemctl disable srs_milter.service

xyzulu

tstrand srs_milter.service error message will continue to spam and slowly eat up your diskspace.

I haven't see that happen if you have your panel updated to v11 and append 3.0.2
Is that your config and you are still seeing this issue?

Adam

tstrand I guess it should be save to disable that service on those servers?

systemctl stop srs_milter.service
systemctl disable srs_milter.service

Yes. We will also make this service exit more gracefully where the email role isn't installed.

There is an appcd + core update coming in the next 2 hours with minor fixes including the DKIM-on-update issue.

tstrand

xyzulu
Yes, I'm running v11 with appcd 3.0.2

xyzulu

Interesting.. I will check a few more of my servers.. none of my servers run any email roles, some only ns/backup. Are you seeing these in syslog ?

Edit: I checked.. I am seeing them as well.. just not affecting my disk space that much.

restart counter is at 211261

😛

Vortex

Adam awesome 👌 finally time to update to 11.0

8Dweb

Adam Will this help with those of us who updated? We updated at 6am yesterday (30th). The DKIM issue is a problem in that release.

Frankly, I have no extra capacity to try to script something to overcome this issue. If we have to do all DKIM updates manually, my team and resellers will be perturbed.

« Previous Page Next Page »