Q: Detailed Description of the Problem A: After site creation I saw that some default themes and plugins needs to be updated (new versions available). When I click the Update button I’m greeted with this popup:
I don’t know what should I enter there to be able to update that.
I guess permissions should be tweaked or constant added to the wp-config.php file during the WP installation process.
How aboout MacOs? I am experiencing the same issue as slaFFik on MacOS.
I can’t use devKinsta until this is solved since no new plugins can be added or updated.
I’m using a site that was pulled down from my Kinsta server. I don’t have a clue what the Hostname, FTP Username, or FTP Password are. I’ve never used or needed them before.
As far as I can tell, Kinsta is the only resource for finding a fix.
I pulled the same site down and used Laragon to work on it. I had zero problems updating anything.
Hi @nametags4u . Try adding define(‘FS_METHOD’,‘direct’); inside your wp-config.php file. That should remove the issue until a patch is available for resolve this.
Hi @nametags4u , sorry for the difficulties here and that the above adjustments didn’t help Rest assured this is on our radar and we will update the thread as soon as we have something more to offer!
Hi all While we haven’t been able to duplicate this at the moment so far we feel this may be permission related, if anyone continues to see that prompt beyond the wp-config.php edit (perhaps @nametags4u ) may we please have you try running the following command?
I’m getting ready to try your suggestions… In the meantime, it didn’t dawn on me before, but I get Security Warnings every time I launch a site from DevKinsta. I always accept the risk. That may be why I can’t run updates.
This is the specific warning I get. Note that I do not get this warning when using Desktop Server, Laragon, or Local by Flywheel.
Warning: Potential Security Risk Ahead Firefox detected a potential security threat and did not continue to blanksite-1.local. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details. Learn more…
Frank
You’re welcome! I don’t believe that would cause it, as that should only relate to how your browser is validating the SSL with the local domain Are you able to share what version of Firefox you’re using? Is the same warning triggered on other browsers? I’ll check with our team about this as well as I haven’t been able to find much on this myself, I’ll keep you updated!
I deleted the local site and downloaded a fresh copy via DevKinsta. There are a couple dynamics in play. We have a new IT provider that locked me down so tight I couldn’t research military or law enforcement. That’s 90% of our business. So they opened up the firewall, I downloaded a fresh copy of the website, and ran the docker exec devkinsta_fpm chown -R www-data:www-data /www/kinsta/public/ code you sent. One or all of those combined seem to have fixed the problem.
Now all Kinsta has to do is make the thing lightning fast. I’m using SSDs, but it’s still slower than working online. This will be a great time saver once it’s optimized.