The best solution would be to solve the cause of the Server 500 error. This would allow you to use the automatic update feature also in the future. If your server dies right after you've clicked the "Update now..."-button (before you are presented the new release info window "Welcome to the update wizard") the server most likely dies on when it is trying to access myDBR.com.
Few things that could cause the Server 500 error:
- Make sure your server has access to mydbr.com
- Do you have php_curl installed. If not, please enable it. It gives myDBR bit more flexibility when doing the update.
- Try to disable open_basedir if you have it enabled.
- See IIS / PHP error logs for more info about the error
The second option is to download the 2.8 manually, save the mydbr_config.php and mydbr/user directories and replace everything else with the new release. myDBR will update the database to 2.8 when it it started.
As said, the first option is the recommended one since it will save you lot of time in future.
--
myDBR Team