thanks for the update. I still think it is an permission/ownership issue. it could simply be that the migration plugin packs up all files on the source system keeping the pervious owners and permissions and unpacks them on the new system but does not or cannot adjust the ownership properly.
I have to admit that I am not familiar with these migration plugins, but I guess on top there are different plugins which do approach that in different ways anyway
on top beneath cpanel or any other hosting files and folders could belong to the webserver user (www-data), while on hestia this is always an inidvidual user instead. for php there also can be a difference in the way it’s integrated with the webserver and which functions are allowed to be run by the webserver and which are not.
so here is my suggestion on how to do such a migration:
first, please create a new user instead of using the admin account. as the admin itself is powerful and allowed to use sudo it is not advisable to use that account for hosting your live production stuff. if your wordpress get’s hacked it would be much more likely that an attacker can gain access to the full system and you for sure don’t want that
using the one click installer for deploying a wordpress should be fine, as well as using a third party plugin for the transfer of your theme, plugins and content.
after the initial migration but before updating, I’d recommend to reset the permissions via cli for all files (644) and folders (755) and make sure everything below public_html is owned by username:username (I recommend using find -exec rather than just recursive chmod/chown to not mess up even more ;-))
start the updates only after that and I am quite sure that the problems should be gone…
