WP-admin redirects to login after adding SSL certificate

Question

I have a page on my wordpress site which adds file content to a div using jquery.get. The file being targeted is a wp-admin file. The problem is, since I added SSL certificate this file no longer loads. When I check the file which is actually loaded it appears to be the log in page.

Jquery Code:

jQuery.get('/wp-admin/admin.php/?page=booking.multiuser.5.3/wpdev-booking.phpwpdev-booking-resources&tab=availability&wpdev_edit_avalaibility=<?php echo key($_REQUEST['avail']); ?>/', function(data, status) {
        alert("Data: " + data + "\nStatus: " + status);
}

In the alert box I get status:success but the data: that is loaded is the standard wordpress login page.

I have checked other answers on stackoverflow which suggest trailing slashes are the issue but this has not solved the problem.

Is the site switching protocols to http when calling the jquery? I have read elsewhere that this can be an issue and wordpress will log out a user if an http url is called from https file. How would I check to see if this is happening?

UPDATE: If I browse to the file directly I am also redirected to the log in page, even if I am already logged in.

Answer 1

Go to your admin area, general settings, and update your "WordPress Address (URL)" and "Site Address (URL)" field value with https. and then update your permalinks setting, by simply click on "Save Changes" button.

In case if you are not able to login to your admin area also, do this changes directly in your database. To update directly in database open your wp_options table, search for option_name = "siteurl" and changes its option_value with your https URL.

Hope this will help you.

Answer 2

The issue was the custom login page we have. $user_verify = wp_signon( $login_data, false ); should be $user_verify = wp_signon( $login_data, true ); - setting the value to 'true' creates a secure cookie. If the cookie is not secure, each time a user tries to access wp-admin files they are logged out.

For details check the [wordpress codex][1] for wp_signon.