Any suggestions as to why I'm getting this 500 error out of the blue? It just started happening this week. Where should I began looking?

Drupal 7.38
PHP 5.5.18
Backup & Migrate 7.x-3.1

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Postponed (maintainer needs more info)

Please provide more details, specifically when does the error occur? Do you see anything in the Watchdog logs (if database logging isn't turned on, try turning it on, trigger the error and see what messages were left, then turn off dblog again)?

Backo47’s picture

Backo47 commented

I have the same issue. It occured after setting new path for backups in local server.
Reinstalling plugin didn't help.

ddease2’s picture

ddease2 commented

Not sure if this is related, but I updated to MAMP PRO 3.4 and I was set to have different PHP versions for each host. I changed it to one version (5.6.10) and haven't had a 500 error since.

rob de koter’s picture

rob de koter commented

Same here, Drupal 7.50 PHP 5.5.38 Backup & Migrate 7.31
I did reinstall Backup & Migrate, no success

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Related issues: +#2832222: http error 500 at making backup with php 7.0

Sounds similar to #2832222: http error 500 at making backup with php 7.0.
What does the server errorlog say?

couturier’s picture

couturier commented
Version: 7.x-3.1 » 7.x-3.x-dev

Can someone confirm if this is still an issue with the newest 7.x-3.2 version?

francewhoa’s picture

francewhoa
he/him
Primary language French
Location Sept-Îles, Québec, 🇨🇦
commented
Component: User interface » Miscellaneous
Status: Postponed (maintainer needs more info) » Closed (works as designed)

We were able to reproduce this error. Steps to reproduce and potential resolutions.

I suggest to set this ticket to "Closed (works as designed)". Because we were able to reproduce this error. But it's likely cause by Apache configuration. Not by Backup and Migrate Drupal module.