Update installation fails, but plugins update just fine

Hi! I’m having an unusual error when I try to update Grav from the admin panel. I’m currently on 1.7.50 and I see an update to 1.7.50.3 in the admin panel (yesterday it was 1.7.50.2 and I had this same issue)… when I select update, it looks like it’s going to update and then it spits out an installation failed message. The same message happens if I try to manually update with a .zip package from the Grav site using either 1.7.50.3 or the 1.8 beta. The error message is at the end of this post… there’s a LOT of diag/diag/diag’s.

In doing some research in the forums I found one post that seemed somewhat related and was also using DreamHost, it suggested turning off “mod_security” in the DreamHost Panel. I tried that and it didn’t resolve the issue, so I’ve turned that back on.

Plugin installs and updates are working just fine. And I was able to update to 1.7.50 a few days ago without issue.

Error message (with the actual user name and site folders redacted in the brackets):

Installation failed: Unable to create directory: /home/[ssh_user]/[site_folder]/tmp/grav-snapshots/stage-68fa40d84d7a2/package/.dh-diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag/diag

@jonesdl, The lead developer doesn’t visit this forum and lives instead on Discord and Github. Therefor, it is most productive/efficient if you could open an issue on the repo of Grav.

1 Like

Thanks for telling me about the Discord! I ended up not needing to post there because I saw in the chat that there was an issue with the configuration of 1.7.50 and for someone else’s issue they were able to turn off safe update to get it to work. I tried that and it worked for me.

So if anyone else is stuck on 1.7.50 and sees this, turn off safe update, and you should be able to get the latest release properly.

Thanks again!