Forum Replies Created

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter Jimmi

    (@jimmi61)

    Further update:

    I found this post and I found that the problem was that I access the administration panel without www and with https connection.

    I may even add the www to my bookmark, but I don’t like too much to avoid using an encripted connection: is there an alternative?

    Thread Starter Jimmi

    (@jimmi61)

    The news is that it happens in Firefox only, not in Opera neither in Epiphany. IE I couldn’t still test, I will do soon.

    Thread Starter Jimmi

    (@jimmi61)

    Today I ran the ‘UTF-8 Database Converter’ plugin with success.

    My previous question regarding the accents may be turned to another: is it necessary to code the accented characters with &Xgrave; like?

    Thread Starter Jimmi

    (@jimmi61)

    No errors in the errors.log

    With the plugin active I may still reach the login page, either http-https://mysite/wp-login.php, the problems start after pressing the login button.

    I changed *: to _default_: in any stanza, 80 or 443, without apparent changes.

    telnet your webserver on port 80 and tee the output to a file (telnet your-server 80 | tee log.txt) and type

    GET /blog/wp-login.php HTTP/1.0

    Gives me “HTTP/1.1 200 OK”. When I try to access the admin console I get in access.log:

    “GET /wp-login.php?action=logout HTTP/1.1” 302 – “-” “Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080213 BonEcho/2.0.0.12”

    Now please disable the plugin by moving the admin-ssl.php file out of wp-content/plugins.
    On my system I can run https://blogurl/wp-admin/ without the plugin.
    Does that work and generate log file entries?

    Yes. it does, but always complains for non protected contents. Is this as safe as running the plugin?.

    Thanks again for your help
    Jimmi

    Thread Starter Jimmi

    (@jimmi61)

    First remove the SSL re-write rules. Not needed if you use the Admin SSL plugin and I _think_ they wont work.

    For the new Virtual host *:443 make a dummy directory underneath the document root and put any HTML page there. I use phpinfo.php for that.

    Load that page in your browser and validate that the page works in https. Make sure you duplicate your wordpress section in the new SSL portion and try https://your-wordpress-blog-url-here/

    This I tested already and works perfectly

    Now activate the Admin SSL plugin and that ought to work.

    No, it doesn’t ?? The browser hangs for some 20-30 seconds then the same error.

Viewing 5 replies - 16 through 20 (of 20 total)