WordPress wp-admin redirects to https

1 Views

I have this problem, when I try to login in my wp dashboard (wp-admin) it redirects to a https connection.

when i type websitename.com/wp-admin, it’ll show the login page but the url has is different.
it says, websitename.com/login.php?redirect_to=https://websitename.com&reauth=1.

Read More

I never did anything odd, i was just editing the plugin and later on this thing happens.

What’s the problem with this?

Anyone can help?

Post Views: 1

Related posts

Leave a Reply

4 comments

  1. So if you are having this issue only when you go to ../wp-admin then it is because you have force ssl admin set to true. You can find this in wp-config.php in the root of your WordPress site, you need to set this option to false.

    define('FORCE_SSL_ADMIN', false);

    I am assuming your siteurl in the wp_options table in the WordPressdatabase is set to a http:// address.

  2. open your wp_options table in database.

    Search for siteurl and check option value of siteurl. I think that url is redirected to
    https. Change it to http.

  3. Old question, but something has never been mentioned here: any user can choose to use SSL.

    You may want to check your wp_usermeta table:

    mysql> select * from wp_usermeta where meta_key = 'use_ssl';
+----------+---------+----------+------------+
| umeta_id | user_id | meta_key | meta_value |
+----------+---------+----------+------------+
|        9 |       1 | use_ssl  | 1          |
+----------+---------+----------+------------+

    use_ssl need to be set to 0 if you don’t want to be redirected (useful for local development):

    update wp_usermeta set meta_value = 0 where meta_key = 'use_ssl' and user_id = YOUR_ID;

  4. There is a bug in chrome and chromium 44.0.2403.89 which also causes this bug. Especially to sites using Woocomerce. But all frameworks using PHP could be effected.

    This is not the same problem as the author but i think google will lead those of you that have the same problem as me here anyway.

    The description of problem which is found and described in the link below is that chrome started to add ‘HTTPS:1’ header to all requests. Which leads to a problem with PHP way to handle headers and checking ssl.

    There is a patch on the way that renames the header ‘HTTPS’ to ‘upgrade-insecure-requests’.

    https://ma.ttias.be/chrome-44-sending-https-header-by-mistake-breaking-web-applications-everywhere/