• One thing I found installing 2.6:

    I installed the test blog in a secured (SSL) environment, so my access would be https://my_web/blog.
    No way. At least: index.php IS accessed but no stylesheet is accessed, not is any content. Login failes: cannot find page; admin acess fails, cannot find page.

    The reason is that in the options table, the records for “Site URL” and “HOME” lines state “https://my_web/blog” where it _should_ read “https://my_web/blog”. After changing this, it worked fine.

    Would it be an idea that if a new blog is created, to use the same protocol here that is used creating the blog (so “http” is the install script is run using a non-SSL link, and “https” if SSL is used)?

    (I propabvly had the same issue on previous versions)

Viewing 1 replies (of 1 total)
  • Hi WillemGrooters,

    Thanks for this topic. I do not seem to find documentation about INSTALLING and RUNNING WordPress over an SSL platform permanently, which is exactly what I need to do with two blogs.

    There are various questions about this scenario, i.e. running WP over SSL and only SSL, I mean the lot, not just Administration.

    A number of issues could be uploading files, linking to pictures stored in picture hosting sites, inserting YouTube videos into articles, etc…

    My main concern is that visitors browsers will pop up the annoying msg saying “Do you want to see both secure and unsecure content?”.

    Another issue is the SSL Certificate installation. Now, I am familiar with this. However, after installing the SSL Certificate, I assume it will not be possible to install snipets of code to produce the desired GRAPHIC saying the site is authentic and secure.

    And another issue is PLUGINS and WIDGETS… I reckon there will be zillions of problems with PLUGINS and WIDGETS using external resources. One such case is Global Translator, for instance.

    Anyone else could perhaps share experiences running WP completely under SSL?

    Thank you & Regards

Viewing 1 replies (of 1 total)
  • The topic ‘New blog under https not accessable’ is closed to new replies.