Search results

Unfortunately we don't have a development server that this is an issue on so that's not an option for me...

OK, thanks. I'm too tired to dare action this on a production server right now, but this sounds promising! I'll let you know how I get on.

Interesting... So, this should do it then? sudo cp -a /usr/lib64/*.so* /var/www/vhosts/chroot/usr/lib64/

Do you mean the curl binary? So `./update_chroot.sh --add curl` ? Perhaps there's a way to just list out all of the programs PHP depends on and --add those. Although, surely the `for` loops in my earlier post should have done this actually...

Perhaps this is better explained by example. Attached is one of our cron scripts (I've had to zip it up to attach here but it's just a 39 line PHP script). You can ignore the require lines at the top - those just set up some variables that all scripts rely on basically. So this is effectively...

But surely PHP should be able to access files by public URL even if it's binary is chrooted?

PHP is set to run as an FPM app under Apache and regardless of whether the domain is set to chrooted or not, this seems to work just fine. It's the "access to the server over ssh" setting under the domains hosting settings that I want to change to /bin/bash chrooted. Until today, doing this...

Thanks John. Any idea how I'd do the binding please? Ref copy() - I think PHP wraps Curl into all file read functions, like copy(), so that you can open http URLs with them. I've noticed SoapClient functions fail too so I think it's probably that I need to add curl and maybe wget in to the...

Actually, it turns out this still isn't enough for some PHP crons to work. Scripts using PHP's copy() command to copy remote files fail, and scripts connecting to MySQL using localhost instead of 127.0.0.1 fail too. I'm sure there are other similar issues.

Three years later, I've finally cracked it. For anybody stumbling onto this still looking for a fix, with the help of How to add programs to a chrooted shell environment template in Plesk this is what's finally working for me. I can now have chrooted SSH with working SFTP access and PHP cron...

Thanks @Peter Debik but this doesn't seem to be working for me on CentOS 8. I'm wondering whether CentOS 8 has some kind of security modules running that override user-set umasks or something, but comparing the various SSH / PAM etc configs with a working CentOS 7 box doesn't seem to bring up...

Any thoughts on this one yet please?

I've just set up a new server for a client using a single domain Plesk license. Usually we use multi-domain licenses which of course include subscriptions and plans, so the settings I'm seeing in this install are a bit more restrictive but as far as I can tell everything is configured as per our...

I've just set up a malbox on one of the old servers, sent a test email to it, migrated, and it doesn't look like this email has duplicated this time. Migrator 2.20 isn't released yet and PMT-4721 isn't referenced in the changelogs yet, but PPPM-11776 fixed back in April sounds suspiciously...

Almost another month has passed. That's 5 months now, paying for servers we no longer need because migrating mail accounts from them isn't working...

This is getting ridiculous now. It's been 4 months since I opened this thread, 2 months since it sounded like we were getting a fix, and almost a month since I asked for an update but still the patch isn't released and there's no eta?

Any eta for Plesk Migrator 2.20 yet? There's been a couple of minor versions since March 16th but no sign of a PMT-4721 fix within them...

Brilliant, thank you!

I see Plesk Migrator 2.19.0 was released a couple of days ago with an intriguing changelog entry: Is there any chance PMT-4721 self resolves because of this, or was it an entirely different issue? We're still having to pay to keep these old servers online and would appreciate any updates you...

Damn. Not even a loose one? Is it likely to be ready in weeks or are we talking months?... Years? We're literally paying a couple of hundred GBP per month more than we need to at the moment, for servers hosting websites that we expected to be migrated by now, and this bug is the only thing...