Odd Behavior – https reverts to http in the add plugin navigation

I’m assuming you’re using WordPress HTTPS, but you didn’t actually say. Are you?

Yes. I couldn’t use an alternate port otherwise.

I can’t reproduce this issue. Could you tell me if this happens with the development version?

I don’t know when I’ll have the time, but I’ll check.

Okay, I tested it and it still doesn’t work. By the way, I was confused by the lack of a port number box until I added the port number to end of the SSL domain.

It’s really odd because my rewrite rule says to rewrite anything with /wp-admin/ in it. Could it be because WordPress uses force_ssl_admin (or lack thereof) to write those URLs?

In the meantime, perhaps I need to limit my rewrite rule for logging in only.

If you didn’t install it through the Dashboard, you have to deactivate/reactivate the plugin to run the install/upgrade process. I moved the port out of its own field, that’s why your port was missing.

It’s just a bug somewhere in the code. Not sure where, though.

I found the problem and it isn’t your plugin. The default fastcgi_params file for NginX doesn’t include:

fastcgi_param HTTPS on;

It took me a lot of searching through bug reports to find it. Once I added that, all of the URLs suddenly worked as expected. Perhaps you may want to add that to the FAQ somehow.

By the way, the development version of the plugin works perfectly (for me).

You should have had a lot more issues than that if that was the fix. At least you got it working.

I try to leave the server configuration up to the user and their hosting provider. If the server isn’t correctly reporting that the page is HTTPS, there’s really nothing I can do about it. The plugin has an entry in the debug log called “SSL: Yes/No” that helps identify this issue. If it says No on an HTTPS page, the server is set up wrong. I have limited time to develop and support the plugin, so I try to focus on people having issues with the plugin directly.