Alright, thanks for double-checking those permissions and getting AMP updated. Since permissions don’t seem to be the issue, we might be looking at something a bit trickier. To narrow it down, let’s perform a test with a simpler backup location to isolate the problem.
Here’s what we’ll do next:
-
Create a temporary local backup directory:
mkdir /home/amp/backups sudo chown -R amp:amp /home/amp/backups sudo chmod -R 755 /home/amp/backups
-
Update AMP to use this new backup location:
- Go into the AMP web interface.
- Use the search box to find the backup settings.
- Change the backup location to
/home/amp/backups
.
-
Restart the AMP instance and see if the backup plugin loads:
- Restart the instance via the AMP interface by right-clicking the instance and selecting “Restart”.
Let’s see if AMP happily loads the Backup Plugin using this simpler, local directory. If it works, we can then try figuring out what makes /media/backups/
different. If it fails, it might point to something more intricate with AMP itself or how it’s configured. Let me know how it goes!