WordPress HTTPS (SSL)
Too many redirects / variable not defined (2 posts)

  1. heutger
    Posted 4 years ago #


    I have issues since your last new major release of WordPress HTTPS it is required that a SSL port is provided, if not, the first release .0 result in a PHP parse error because of an undefined variable, but although this problem has been resolved in newer releases the front page without being logged in result in a loop (too many redirects said by chrome), it no HTTPS port is set. Once it is set, although it's the default port 443 recently not required, everything works fine.

    That's just to report the bug, a solution is possible with setting port 443, recently required directly in the database, now it still works in the backend.



  2. Mike Ems
    Plugin Author

    Posted 4 years ago #

    Have you tried resetting the settings and not specifying a port? Seems odd that you need to. I haven't had this issue. I may need to take a peak at your setup to see what's going on there.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WordPress HTTPS (SSL)
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic