Appcd 4.0.0 - 23rd July 2024: Page 2 - Enhance Control Panel

Appcd 4.0.0 - 23rd July 2024

xyzulu

4.0.1 is out now..

PDudeP

Just updated all servers to 4.0.1.
About 3 minutes.

Everything seems perfectly fine.

Thanks Enhance Team!

AdamM

So, it seems that it was also my fault. I was using Ubuntu 23.10 on a server with mail.
I did the upgrade to 24.04 and appcd 4.0.1 and it looks like everything is working. Thanks also to Adam for his help!!!

8Dweb

Updated to appcd 4.01 - no issues.

cosmoshosting

Thanks for your hard work, update went well.
Disk space reduction is a welcome improvement.

Isaia-Arknet_PTY_LTD

AdamM

Have you found the answer to your question? And if so, what have you done to clean the space out 🙂

I am sure others want to know 🙂

george

All good! No issues...

mah1952

Upgraded to latest version. All good and No issues.

DracoBlue

The update was quick and trouble-free, I deleted the enhance container images directory, which freed up a lot of space. I think it's getting better in terms of optimization 🙂

Krikke

Smooth update here too. Apart from a mistake I made in nginx vhost config that only propagated when services restarted after the update, which brought down my websites. Quick debug & fix thanks to Adam. I'll revisit my process around editing vhost configs.

MediaServe

A client has reported that Composer isn't available now in his websites. I'll have to figure out the correct way to install Composer to make it fully available to websites. Since the primary partition now reflects the OS installed stuff, it should be basic to install, but I'm curious if anyone else has seen this?

Adam

MediaServe

There will be another appcd update to address this shortly. In the meantime you can do this:

https://getcomposer.org/download/

Copy the .phar to /usr/bin.

PDudeP

Adam I updated to 4.0.2 on one server, but only then I realized there's this note: "If updating from 4.0.0 or 4.0.1 please run rm /usr/bin/composer before updating."

Should I do it now, after the update?

lxix

Updated to the latest version and I had two minor problems since: DKIM got disabled for roughly half of the websites and the file /usr/bin/wp (i assume it was created during the update) reported as "RH-Sharpe's Rootkit" by opsshield's rkhunter. Otherwise all good.

MarkD

lxix After updating to 4.0.1 we had alerts from opsshield for all the servers about the same rootkit "RH-Sharpe's Rootkit" - I am assuming this is a false positive 😬

Adam

/usr/bin/wp is a symlink to /usr/bin/wp-cli which in turn is downloaded directly from wp-cli.org. It seems this isn't uncommon:

https://blog.derakkilgo.com/2020/01/18/warning-rh-sharpes-rootkit/

lxix DKIM got disabled for roughly half of the websites

This update didn't touch email so shouldn't have affected dkim.

xyzulu @Adam I thought the ability to update openlitespeed and mariadb/mysql was scheduled for this month? I can't see that on the roadmap now.. did I miss something? I'm assuming that it would be an Enhance update, not appcd

It's not been scheduled for a particular release yet.

PDudeP Adam I updated to 4.0.2 on one server, but only then I realized there's this note: "If updating from 4.0.0 or 4.0.1 please run rm /usr/bin/composer before updating."

Should I do it now, after the update?

Do:

rm /usr/bin/composer
apt install --reinstall appcd

xyzulu

@Adam I thought the ability to update openlitespeed and mariadb/mysql was scheduled for this month? I can't see that on the roadmap now.. did I miss something? I'm assuming that it would be an Enhance update, not appcd

grradmin

MarkD
This alert is a false positive. Running the following command will whitelist this specific case and avoid reporting it again:
echo "RTKT_FILE_WHITELIST=/usr/bin/wp" >> /etc/rkhunter.conf

PDudeP

@Adam done. Thanks

PDudeP

I just noticed that on Websites > Email > Email Accounts > Email client setting , instead of mail.example.domain in the server name, I have the actual server name.

I'm sure it wasn't like this.

Can you guys check it this is also happening with you?
I just want to know is this is related with these latest updates.

Adam

PDudeP

This isn't related to the update. The behaviour has always been the same - if a server hostname domain is defined, this will be shown. If not, the customer will be shown mail.customerdomain instead.

The solution is to remove the server hostname website - you can add the A record to the parent domain instead so that the hostname still resolves.

« Previous Page Next Page »