Support

Once I login the page will not display and says their is a security certificate issue.

You have to contact your host. This means that you have set up that your site's administrator area must be accessed only under HTTPS but you do not have a valid SSL certificate for the dev subdomain. Your host can yell you how you can get and / or install a valid SSL certificate (most likely a new certificate for the subdomain or a catch-all / wildcard SSL certificate on the site). Actually, only your host can tell you that. All I can tell you is that this is what happens.

Alternatively, you may edit your configuration.php file and change the $force_ssl line to 

public $force_ssl = '0';

You may also have to edit your .htaccess file if it's also forcing non-HTTPS to HTTPS URLs for the administrator.

You said:

Once I login the page will not display and says their is a security certificate issue.

and

This is not an ssl issue.

Both statements cannot be correct at the same time. If the first one is correct, it is an SSL issue.

Server error The website encountered an error while retrieving http://beta.**************.com/administrator/. It may be down for maintenance or configured incorrectly. Here are some suggestions:

A 500 error, though, is a completely different thing.  A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):

ini_set( 'display_errors', true );
error_reporting( E_ALL ); 

Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:

php_flag display_errors On
php_value error_reporting 32767

and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:

display_errors=on
error_reporting=E_ALL

and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

If you still get a white page, delete the php.ini files your created and choose a different host. If your host doesn't allow you to debug any PHP-related issues there is no point paying them.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

You are restoring on top of an old version of Akeeba Backup and, presumably, an old version of your site which is running on Joomla! 1.5. You cannot restore a Joomla! 2.5 site on top of a Joomla! 1.5 site or vice versa. You will have to remove all folders and files before attempting the restoration.

You're welcome!