Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter lp1dev

    (@lp1dev)

    Very strange indeed! The admin bar does shows up on the front-end! I tried to create a new used on the front-end, it works but when I try to access the user’s profile (which is under wp-admin/profile.php) I encounter the same issue. Everything under wp-admin throws exactly the same error. I tried to manually add an user to the database, and it gets me to the same point. I checked the usermetadata table, I didn’t see anything unexpected. I updated my htaccess, but it uses relative links, is there a specific configuration I should do inside it? I tried to use it to redirect http traffic to https, but it didn’t fix the issue. I tried the subdomain example and it didn’t seem to do much change. I’m going to try again tomorrow to tweak my .htaccess.

    Do you think a mixed-content error might throw this kind of error? Because I have a few of them because of some plugin! Or could it be some cache somewhere, rewriting my urls without the https (even through it seems quite unlikely)?

    Replacing every https://yourdomain to https seems like a great idea! Do you have any specific plugin in mind?

    Thanks for your time!

    Thread Starter lp1dev

    (@lp1dev)

    Hi kyjus25! Thanks, but unfortunately my website is not under www, but it IS under a subdomain (devversion.mydomain.com) . Since I’m not 100% percent sure what could be the source of the issue I’m going to explain a little bit more precisely what I did.

    I have a dev version of the WordPress, hosted on our company’s server, it is an Apache Server Running Plesk and it is inside a subdirectory (Similar to https://preview.mywebsite.com/websites/mywordpress), there is no HTTPS/SSL configuration on this wordpress instance.

    We have to migrate it to our client’s hosting, so I:

    – Made a sql dump of the mysql database
    – Updated the client’s database with the dump
    – Pushed the sources through ftp on our client’s domain, but under a subdomain (devversion.mydomain.com) to avoid breaking the production website,
    – Updated the home and siteurl variables inside the wp_options of the database with https://devversion.mydomain.com
    – Updated the wordpress’s wp-config.php to connect to the new database

    That’s when the issue occured, I then tried to add $_SERVER[‘HTTPS’]=’on’ and define(‘FORCE_SSL_ADMIN’, true) to my config.php file (among many other potential fixes I found online) but nothing worked so far.

    Is there something I might have missed? I set the debug to true but I don’t have more information.

    • This reply was modified 7 years, 5 months ago by lp1dev.
    Thread Starter lp1dev

    (@lp1dev)

    Thanks for the link! I tried setting FORCE_SSL_ADMIN to true or false, but none of them worked, I made a RewriteRule to redirect everything to https but it didn’t work either, I tried disabling all of my themes and plugins too but it didn’t seem to fix the problem. I was thinking about running my wordpress through a reverse proxy to fix my SSL problems but I’d love to be able to avoid it if someone has another solution

    Thread Starter lp1dev

    (@lp1dev)

    Hi Daniel! Thanks for your quick answer! Actually the weird part is that I don’t have a redirect loop (it would be easier to debug), I have a “Sorry, you are not allowed to access this page.” even through I am logged with an Admin account

Viewing 4 replies - 1 through 4 (of 4 total)