Advertisement:

Author Topic: Converting to https, step-by-step...  (Read 21144 times)

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Converting to https, step-by-step...
« on: July 08, 2017, 03:01:04 AM »
Having just gone thru this the first time myself, I thought I'd share my notes & explain each step (as best I can, anyway).
 This is the stuff I wish I knew up front...  Whether you are doing a new install or trying to diagnose an issue, follow these steps in sequence to get your site up & running.

These steps are generic enough to help you whether you are running under 2.0.x or 2.1.x. 

(1.) Purchase & install your certificate.  Yes, this is the first step.  With a certificate installed, you can run either http:// or https://.  If you do NOT have a certificate installed, you can only run http://.   So... 

If you do NOT have a certificate installed, and you change all your URLs to https://, your site will (POOF!) disappear...  That's because your web server won't serve https:// content without the cert.  Install the cert first...

(2.)  Test your cert, to make sure it is installed & fully operational.  There are lots of tools online that will help you confirm it works.  One such tool:  https://www.sslshopper.com/ssl-checker.html

(3.)  Install an http to https redirect.  Without the redirect, your web server will still attempt to serve up http:// upon request.  So, for example, if you type in your forum's URL with http://, not https://, it will actually execute index.php insecurely.  Themes probably won't work though, so you will probably get that weird, blank-page, text-only version of your site.  A redirect will avoid lots of flaky behavior... 

Here is a good, multi-purpose Apache example right here, that will redirect ALL http:// traffic to https://, and further, tell search engines this is a permanent change:
Code: [Select]
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Save the above as a text file named .htaccess, and place it in the root folder of your site.  If you already have an .htaccess file, copy & paste the above at the top of the file. 

There are many other .htaccess examples out there, e.g., if you only want specific folders redirected.  This may be helpful if you have multiple forums, each in separate folders, and only some are https.  If you have such complicated needs, Google is your friend... 

(4.)  If installing...  Run the installer using https://  Using https:// is pretty important, as all URL settings created by the installer are based relative to how you invoke the installer.  Invoking the installer as https:// will make sure all of your URLs internally are https:// at the outset.  If you run the installer with http://, you will have to fix this later using repair_settings.php.

(5.)  If installing 2.1...  Select the Force SSL option.

(6.)  Run repair_settings.php. **MAKE SURE YOU USE THE RIGHT ONE**  There is a different repair_settings.php for SMF 2.1 up on Github!  Using repair_settings.php, confirm the following URLs are all setup with https://, not http://:
 - $boardurl
 - Your Smileys URL
 - Your Avatars URL
 - Your Custom Avatars URL (if you have one)
 - Your Theme URL (one for each theme!!!!)
 - Your Theme/Images URL (one for each theme!!!!)

Save your settings, exit, & delete repair_settings.php.   

I run repair_settings.php just as a safety measure, just to make sure it all went as expected...  I'm paranoid & like double-checking things...

(7.) If you were running 2.1 already, go to the Admin | Maintenance | Server Settings | General and choose "Force SSL throughout the forum" at the Forum SSL Mode prompt. 

(8.) If running 2.0.14+, or 2.1, consider activating the image proxy.  You probably want to do this if your site has mixed http:// & https:// content.  This happens if your forum members share a lot of images from other websites.  If there are mixed http:// and https:// images on the same webpage, you will at least get a security warning, & you will more likely get broken links.  This is because some browsers will not serve mixed http:// & https:// content as a security feature.  SMF's image proxy feature will download http:// images locally, so SMF can turn around and serve them up https://.  No more 'mixed' content issues.  This will significantly reduce broken links and security warnings on your site.  If your forum members share lots of images, you probably want the image proxy enabled. 

NOTE:  The upgrader doesn't change anything - if it finds a site http://, it leaves it http://.  If it finds a site with https://, it leaves it that way. 

What do you do if you're still having issues?  Run repair_settings.php again & triple-check all your URLs... 

Hope this helps.
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #2 on: July 08, 2017, 01:53:37 PM »
Just ran across a nifty tool that helps you confirm your redirect is working OK:
   http://www.redirect-checker.org/index.php

Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline lurkalot

  • Sophist Member
  • *****
  • Posts: 1,016
  • Gender: Male
  • Tinyportal Support
    • guitaristguild on Facebook
    • Tinyportal on GitHub
    • @GuitaristGuild on Twitter
    • Guitarist Guild
Re: Converting to https, step-by-step...
« Reply #3 on: July 08, 2017, 06:32:25 PM »
Thanks, handy post.  ;)

Converted a couple of my sites yesterday, before I read this.  Luckily all seems to have gone well.  I will just say though some themes and mods make calls to external scripts, so you might find that even though you might see the green padlock in your browser it's still blocking some of the content.

Offline 青山 素子

  • Server Team
  • SMF Super Hero
  • *
  • Posts: 17,025
  • 戦場ヶ原、蕩れ!
    • srvrguy on GitHub
    • @motokochan on Twitter
    • Nekomusume Moe
Re: Converting to https, step-by-step...
« Reply #4 on: July 09, 2017, 10:17:42 PM »
Some more useful links:

  • https://www.whynopadlock.com/ - Put in the URL to a page and it'll highlight things that are loading over a non-secure connection so you can correct them.
  • https://www.ssllabs.com/ssltest/ - The Qualys SSL Labs tester. It does a very complete check of your setup and will let you know what browsers may have trouble connecting, along with a nice grade on how secure your configuration is.
  • https://www.sslchecker.com/sslchecker - Another SSL checker. This one has the advantage of being able to alert you if you forgot a needed intermediate certificate, which will cause security warnings in browsers. (You can ignore a missing root, the browsers will have those.)
  • https://mozilla.github.io/server-side-tls/ssl-config-generator/ - The Mozilla SSL Configuration Generator. If you manage your server configuration manually, fill in a few details and it'll generate a recommended configuration for SSL setup. I recommend you keep the "intermediate" settings, as the "Modern" will exclude quite a few browsers and platforms still in use.

One thing to keep in mind with the image proxy is that it will increase your bandwidth as it has to fetch the insecure image and then provide it securely from your site. It shouldn't be a lot of extra traffic, but keep it in mind if you enable it.
Motoko-chan
Director, Simple Machines

Just because it's pouring down doesn't mean we're gonna drown. There's a time when all you can say is let it rain - Mat Kearney (Let It Rain)

Note: Unless otherwise stated, my posts are not representative of any official position or opinion of Simple Machines.


Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #5 on: July 22, 2017, 03:12:02 AM »
Another utility while we're at it:
https://github.com/sbulen/sjrbTools/blob/master/SMF_SSL_Diag.php

This is an inquiry-only utility that performs simple checks for the existence of a cert, the existence of a redirect, and also dumps the various SMF variables associated with SSL.  Works for 2.0 & 2.1.  To use, just plunk it in your forum home directory (where settings.php is) and execute it. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #6 on: July 27, 2017, 06:54:34 AM »
Thanks for this little guide.

A few months ago my host switched all his servers to https, but didn't tell me to do anything except change the IP address.  A few weeks ago I moved to a new host.  And it was only inspecting my site after the move, when I realized I'm now in a position of having mixed http and https contents.  Even though I've had my SMF with Tiny Portal for 4 years, I'm still kind of a newbie at running a website.

For #5, I'm not installing 2.1 right now.  But I guess I will eventually.  Do I need to remember to check Force SSL option?

For #8, I thought the purpose for running the repair settings thing (in #6) is to change all the http instances to https.  And if it is, why would I still have mixed http/https images?  My site provides support for a graphics program, so I certainly will have mixed images.  But again, I thought repair settings was going to fix that.

After #8 it says
Quote
NOTE:  The upgrader doesn't change anything - if it finds a site http://, it leaves it http://.  If it finds a site with https://, it leaves it that way.
I'm not sure what that means.  What upgrader?

Thanks!
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #7 on: July 27, 2017, 09:48:39 AM »
Re #5:   Short answer: Yes.  You need to set this new 2.1 setting that didn't exist in 2.0. 

Re #8:  Repair_settings.php helps you address SMF settings.  It does NOT, however, update the contents inside your posts.  Users can enter URLs, e.g., for images, inside posts.  Post content is probably the cause of mixed content warnings/issues.

This is why SMF added the image proxy - to address mixed content issues caused by links to images within posts.

Re the upgrader:  This note just points out that the upgrader does not modify any existing SSL-related settings. 

2.1 is still in beta, and there are some enhancement requests in the queue to make it a little smarter.  Upgrader behavior may change.


The main thing to know at the moment is that - no matter what happens - SMF makes it very easy to change / correct settings using the Admin control panel &/or repair_settings.php to fully support your desired SSL configuration.  It's safe.  The tools exist to correct issues & settings. 
« Last Edit: July 27, 2017, 10:40:25 AM by shawnb61 »
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline aegersz

  • Sophist Member
  • *****
  • Posts: 1,185
  • Gender: Male
  • "mods" junkie
    • dopetalk
Re: Converting to https, step-by-step...
« Reply #8 on: July 27, 2017, 05:12:10 PM »
this may be of interest. I had to make this change to repair_settings.php
SMF 2.0: 135+ mods installed (the full list can be seen at http://forum.drugs-and-users.org/index.php/topic,3301)

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #9 on: August 01, 2017, 04:23:47 AM »
Quote
Re #5:   Short answer: Yes.  You need to set this new 2.1 setting that didn't exist in 2.0.

Ok, I'll try and remember.

While I've been trying to digest all this info, I keep thinking I should do repair settings first, and set the redirect 2nd.  Is there some reason why you suggest making the redirect first?

Will I need to make the change suggested by aegersz, before I use repair settings?
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline aegersz

  • Sophist Member
  • *****
  • Posts: 1,185
  • Gender: Male
  • "mods" junkie
    • dopetalk
Re: Converting to https, step-by-step...
« Reply #10 on: August 01, 2017, 05:14:10 AM »
i think i needed to make that change as i might have not setup my .htaccess for https yet.
SMF 2.0: 135+ mods installed (the full list can be seen at http://forum.drugs-and-users.org/index.php/topic,3301)

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #11 on: August 01, 2017, 08:14:00 AM »
Oohh, and another question. 

I have 2 sites, 2 TLDs.  But the 2nd one lives as a separate page in the file structure on the server.  But it looks like a separate site, which I think is accomplished with a redirect.

Do I need to upload repair_settings.php separately into that directory, and use the same process separately, for that site?

And just to repeat my last question.  Does it really matter whether the htaccess redirect is done before or after using repair_settings?

Thanks again :)
« Last Edit: August 01, 2017, 08:58:33 AM by brynn »
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #12 on: August 01, 2017, 11:16:01 AM »
Do I need to upload repair_settings.php separately into that directory, and use the same process separately, for that site?

Yes, you run it once per site.  Yes, you put it into each forum's root directory.  From the 2.0 repair_setting.php link provided above (https://wiki.simplemachines.org/smf/Repair_settings.php):

"Upload the file repair_settings.php with an FTP client to the root directory of your forum (where Settings.php can be found)."

Does it really matter whether the htaccess redirect is done before or after using repair_settings?

If you do it all in one sitting, not a lot of difference.  But I put the redirect early in the process for two reasons:
(1) Remember, people can still type in http:// in their URLs.  Without the redirect, the content will still be served up http://.  Also remember that lots of posts may have links to other posts, that are still http://.  A good redirect will clean up ALL of these loose ends. 

(2) Most of the SMF utilities, the Installer, the Upgrader & even repair_settings.php, operate from how they are invoked.  If you invoke repair_settings.php as http://, its recommendations will be http://.   If you invoke it with https://,  its recommendations will be https://.

The sooner your redirect is in operation, the sooner ALL updates will use https://.  Even if you forget to type in https://.

If you have a redirect active, or, if you invoke repair_setting.php via https://, I don't think you need aegersz's code fix.  Everything will be https:// already. 
« Last Edit: August 01, 2017, 11:28:45 AM by shawnb61 »
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #13 on: August 01, 2017, 12:04:00 PM »
Oh, thank you SO much!
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #14 on: August 03, 2017, 01:32:50 PM »
I've noticed some images loading slowly, since I've made these changes.  Specifically, images in signature take several more seconds to load, after the rest of the page loads.

Could this be related to the image proxy?  Is there a way to fix it?

Thanks :)
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #15 on: August 03, 2017, 03:33:55 PM »
Changing http to https for the profile image solved it!

Now a different issue.  I have 2 sites using SMF forum/portals.  One of them doesn't have the image proxy option.  Or at least, it's not where the option for the other forum is, and I can't seem to find it.

They do use different themes, but it doesn't seem like a theme issue (or else the options would be in the theme options.

Or maybe the image proxy is provided by a mod that I don't have installed in one of them?
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline Illori

  • Project Manager
  • SMF Master
  • *
  • Posts: 48,402
Re: Converting to https, step-by-step...
« Reply #16 on: August 03, 2017, 03:46:02 PM »
do you have 2.0.14 installed on both of them?

Offline brynn

  • Jr. Member
  • **
  • Posts: 359
  • Gender: Female
    • Inkscape Community
Re: Converting to https, step-by-step...
« Reply #17 on: August 04, 2017, 06:05:16 PM »
Ah, thanks Illori.  I just realized that, and was coming to post.  I'll upgrade asap.
Inkscape Community  (SMF with Tiny Portal)

Inkscape for Cutting Design  (originally a phpBB forum, converted to SMF, and using Simple Portal)

Offline Matthew-me

  • Semi-Newbie
  • *
  • Posts: 78
  • Gender: Male
  • I know what I know and I know what I don't know.
Re: Converting to https, step-by-step...
« Reply #18 on: August 20, 2017, 10:23:27 AM »
Thank you for documenting this shawnb61. Used it to do a clean install on moving host. All worked. I didn't run repair settings .. just updated Avatar, Attachment, Theme and Smileys URL's manually after importing database. I think that was all.

Kudos. Worked like a dream.
How will you make the world a better place today?

Offline aegersz

  • Sophist Member
  • *****
  • Posts: 1,185
  • Gender: Male
  • "mods" junkie
    • dopetalk
Re: Converting to https, step-by-step...
« Reply #19 on: August 22, 2017, 04:36:59 PM »
Ah, thanks Illori.  I just realized that, and was coming to post.  I'll upgrade asap.

I will upgrade too as prior to 0.14, any linked images that are not https will disable SSL for that particular page - is that correct ?
SMF 2.0: 135+ mods installed (the full list can be seen at http://forum.drugs-and-users.org/index.php/topic,3301)

Offline Matthew-me

  • Semi-Newbie
  • *
  • Posts: 78
  • Gender: Male
  • I know what I know and I know what I don't know.
Re: Converting to https, step-by-step...
« Reply #20 on: August 23, 2017, 08:53:48 AM »
I will upgrade too as prior to 0.14, any linked images that are not https will disable SSL for that particular page - is that correct ?

2.014 includes a port from the Beta 2.1 of the image proxy option and https for Avatars.

Simple Machines Forum has released a new patch to the 2.0.x line, bringing our latest release version to 2.0.14.
...
The quick summary of changes is as follows:
  • Added PHP 7 support.
  • Ported image proxy support from SMF 2.1.
  • Also added HTTPS for avatars.
  • Accept email addresses with long TLDs.
  • See the changelog for more.

Without upgrading pages will still load over SSL but you won't see the green padlock if there is mixed content, or you may get a warning or refusal to load - depending on browser and configuration. Upgrading to 2.014 would be my personal recommendation. Having just done a fresh install on a new server, everything is working great with SSL across the whole site.

Kindly,

M
How will you make the world a better place today?

Online vbgamer45

  • SMF Friend
  • SMF Super Hero
  • *
  • Posts: 19,491
    • smfhacks on Facebook
    • VBGAMER45 on GitHub
    • @createaforum on Twitter
    • SMF For Free
Re: Converting to https, step-by-step...
« Reply #21 on: August 23, 2017, 09:21:21 PM »
I would also recommend http2 with apache. Easy to setup on apache 2.4
You get a nice speed boost for ssl sites
httpd.conf file
add
LoadModule http2_module modules/mod_http2.so


And in each virtual host that has SSL
Protocols h2 http/1.1
Community Suite for SMF - Take your forum to the next level built for SMF, Gallery,Store,Classifieds,Downloads,more!

SMFHacks.com -  Paid Modifications for SMF

Mods:
EzPortal - Portal System for SMF
SMF Gallery Pro
SMF Store SMF Classifieds Ad Seller Pro

Offline aegersz

  • Sophist Member
  • *****
  • Posts: 1,185
  • Gender: Male
  • "mods" junkie
    • dopetalk
Re: Converting to https, step-by-step...
« Reply #22 on: August 27, 2017, 06:08:18 AM »
I just moved to 2.0.14 and am very happy. everything is working well. image proxy is a cool thing.
SMF 2.0: 135+ mods installed (the full list can be seen at http://forum.drugs-and-users.org/index.php/topic,3301)

Offline seosefi

  • Newbie
  • *
  • Posts: 2
Re: Converting to https, step-by-step...
« Reply #23 on: September 06, 2017, 03:23:45 AM »
I've spent like 10 days to convert to https, it's really hard to switch. Thank you for completing the process by looking at the makalen. It's been good to fix it. For those who want to switch to https, there will also be a small recommendation, the webmaster search console needs to set the property as https, and the robots.txt file needs to be modified as https in the site map path.

Offline Kindred

  • The Mean One
  • Support Specialist
  • SMF Legend
  • *
  • Posts: 55,277
  • Gender: Male
    • Kindred-999 on GitHub
Re: Converting to https, step-by-step...
« Reply #24 on: September 06, 2017, 04:14:11 PM »
Sorry, but that last post made no sens at all....
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #25 on: September 06, 2017, 09:39:24 PM »
I believe seosefi is saying that if we use them, we may need to also update our URLs in Google Webmaster Tools and Bing Webmaster Tools (for Bing & Yahoo) 

Also that if you have a SITEMAP: specified in your robots.txt, don't forget that, too. 

These make sense to me.   Easy to forget that stuff. 

I think the makalen reference is a typo(???).  The only connection my brain made was to Macallen scotch, which I agree is a critical part of successfully completing the process. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline peterinwa

  • Jr. Member
  • **
  • Posts: 333
  • Gender: Male
    • MySchnauzer.net
Re: Converting to https, step-by-step...
« Reply #26 on: October 10, 2017, 10:49:03 PM »
All my websites have been working fine after being converted with a .htaccess file, all showing the lock and secure. Until today.

Now they all work fine except for my forum which is in the folder /forums in my /public_html directory. It is showing NOT SECURE in multiple browsers.

What I don't understand is how it is possible that all my other websites, whose index.html files are found in other folders in my /public_html directory, are running fine and secure.

Any ideas what might be causing this?

Thank you,

Peter
Here's my forum:  www.MySchnauzer.net/forums

Offline 青山 素子

  • Server Team
  • SMF Super Hero
  • *
  • Posts: 17,025
  • 戦場ヶ原、蕩れ!
    • srvrguy on GitHub
    • @motokochan on Twitter
    • Nekomusume Moe
Re: Converting to https, step-by-step...
« Reply #27 on: October 10, 2017, 11:06:11 PM »
Is it specifically loading over http? If it's using https, you probably have an issue with mixed mode content. You can put a URL in the form over at https://www.whynopadlock.com/ and it will tell you what's loading insecurely.
Motoko-chan
Director, Simple Machines

Just because it's pouring down doesn't mean we're gonna drown. There's a time when all you can say is let it rain - Mat Kearney (Let It Rain)

Note: Unless otherwise stated, my posts are not representative of any official position or opinion of Simple Machines.


Offline peterinwa

  • Jr. Member
  • **
  • Posts: 333
  • Gender: Male
    • MySchnauzer.net
Re: Converting to https, step-by-step...
« Reply #28 on: October 10, 2017, 11:16:18 PM »
I used the link and all my other sites test fine, except for some insecure links to other websites. There are a good number in the forum. Could they cause the NOT SECURE issue?

They look like this:

Total number of items: 71
Number of insecure items: 5
Insecure URL: http://i990.photobucket.com/albums/af29/liz-wills/91daa7b807d8f9a426656dd94b924b9c_zpsff5vopcw.jpg
Found in: https://www.myschnauzer.net/forums/index.php?PHPSESSID=ho5bpq6s5cjpq17o22pl6la613;wwwRedirect

The forum test gave me:

SSL verification issue (Possibly mis-matched URL or bad intermediate cert.). Details:
ERROR: no certificate subject alternative name matches

This means nothing to me. I also don't know why it happens in the SMF folder and not the others. They would all operate under the same SSL.

Thank you very much!
Here's my forum:  www.MySchnauzer.net/forums

Offline Kindred

  • The Mean One
  • Support Specialist
  • SMF Legend
  • *
  • Posts: 55,277
  • Gender: Male
    • Kindred-999 on GitHub
Re: Converting to https, step-by-step...
« Reply #29 on: October 10, 2017, 11:25:14 PM »
Not really Anything you can do about those
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

Offline peterinwa

  • Jr. Member
  • **
  • Posts: 333
  • Gender: Male
    • MySchnauzer.net
Re: Converting to https, step-by-step...
« Reply #30 on: October 10, 2017, 11:30:00 PM »
Do you think those items are causing the forum to show not secure? Would they cause this?

SSL verification issue (Possibly mis-matched URL or bad intermediate cert.). Details:
ERROR: no certificate subject alternative name matches

I think maybe this started today because the browsers just started checking for secure sites?
Here's my forum:  www.MySchnauzer.net/forums

Offline Kindred

  • The Mean One
  • Support Specialist
  • SMF Legend
  • *
  • Posts: 55,277
  • Gender: Male
    • Kindred-999 on GitHub
Re: Converting to https, step-by-step...
« Reply #31 on: October 10, 2017, 11:53:26 PM »
1- they will cause mixed content...   turning on the proxy in the forum settings will help, but may not fix. Broken photobucket links

2- no, that error is something else. Talk to your host

3- actually most browsers did this a few months ago
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

Offline peterinwa

  • Jr. Member
  • **
  • Posts: 333
  • Gender: Male
    • MySchnauzer.net
Re: Converting to https, step-by-step...
« Reply #32 on: October 10, 2017, 11:56:18 PM »
Thank you.
Here's my forum:  www.MySchnauzer.net/forums

Offline Sacha

  • Semi-Newbie
  • *
  • Posts: 63
  • Gender: Male
    • sacha.ungarelli on Facebook
    • @@sachaun on Twitter
    • Argos Games
Re: Converting to https, step-by-step...
« Reply #33 on: October 11, 2017, 08:31:42 AM »
If i have Rewrite enabled in .htacces, some users receive the following error. I had to disable it in .htaccess file:



Quote
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]


# Errors!
ErrorDocument 400 //index.php?action=httperror;c=400
ErrorDocument 401 //index.php?action=httperror;c=401
ErrorDocument 402 //index.php?action=httperror;c=402
ErrorDocument 403 //index.php?action=httperror;c=403
ErrorDocument 404 //index.php?action=httperror;c=404
ErrorDocument 405 //index.php?action=httperror;c=405
ErrorDocument 406 //index.php?action=httperror;c=406
ErrorDocument 407 //index.php?action=httperror;c=407
ErrorDocument 408 //index.php?action=httperror;c=408
ErrorDocument 409 //index.php?action=httperror;c=409
ErrorDocument 410 //index.php?action=httperror;c=410
ErrorDocument 411 //index.php?action=httperror;c=411
ErrorDocument 412 //index.php?action=httperror;c=412
ErrorDocument 413 //index.php?action=httperror;c=413
ErrorDocument 414 //index.php?action=httperror;c=414
ErrorDocument 415 //index.php?action=httperror;c=415
ErrorDocument 416 //index.php?action=httperror;c=416
ErrorDocument 417 //index.php?action=httperror;c=417
ErrorDocument 500 //index.php?action=httperror;c=500
ErrorDocument 501 //index.php?action=httperror;c=501
ErrorDocument 502 //index.php?action=httperror;c=502
ErrorDocument 503 //index.php?action=httperror;c=503
ErrorDocument 504 //index.php?action=httperror;c=504
ErrorDocument 505 //index.php?action=httperror;c=505

I think the problem is "RewriteEngine On" because i deleted lines of https and .htaccess was like this and the continued:

Quote
RewriteEngine On

# Errors!
ErrorDocument 400 //index.php?action=httperror;c=400
ErrorDocument 401 //index.php?action=httperror;c=401
ErrorDocument 402 //index.php?action=httperror;c=402
ErrorDocument 403 //index.php?action=httperror;c=403
ErrorDocument 404 //index.php?action=httperror;c=404
ErrorDocument 405 //index.php?action=httperror;c=405
ErrorDocument 406 //index.php?action=httperror;c=406
ErrorDocument 407 //index.php?action=httperror;c=407
ErrorDocument 408 //index.php?action=httperror;c=408
ErrorDocument 409 //index.php?action=httperror;c=409
ErrorDocument 410 //index.php?action=httperror;c=410
ErrorDocument 411 //index.php?action=httperror;c=411
ErrorDocument 412 //index.php?action=httperror;c=412
ErrorDocument 413 //index.php?action=httperror;c=413
ErrorDocument 414 //index.php?action=httperror;c=414
ErrorDocument 415 //index.php?action=httperror;c=415
ErrorDocument 416 //index.php?action=httperror;c=416
ErrorDocument 417 //index.php?action=httperror;c=417
ErrorDocument 500 //index.php?action=httperror;c=500
ErrorDocument 501 //index.php?action=httperror;c=501
ErrorDocument 502 //index.php?action=httperror;c=502
ErrorDocument 503 //index.php?action=httperror;c=503
ErrorDocument 504 //index.php?action=httperror;c=504
ErrorDocument 505 //index.php?action=httperror;c=505

Then i deleted "RewriteEngine On" and worked fine:

Quote
# Errors!
ErrorDocument 400 //index.php?action=httperror;c=400
ErrorDocument 401 //index.php?action=httperror;c=401
ErrorDocument 402 //index.php?action=httperror;c=402
ErrorDocument 403 //index.php?action=httperror;c=403
ErrorDocument 404 //index.php?action=httperror;c=404
ErrorDocument 405 //index.php?action=httperror;c=405
ErrorDocument 406 //index.php?action=httperror;c=406
ErrorDocument 407 //index.php?action=httperror;c=407
ErrorDocument 408 //index.php?action=httperror;c=408
ErrorDocument 409 //index.php?action=httperror;c=409
ErrorDocument 410 //index.php?action=httperror;c=410
ErrorDocument 411 //index.php?action=httperror;c=411
ErrorDocument 412 //index.php?action=httperror;c=412
ErrorDocument 413 //index.php?action=httperror;c=413
ErrorDocument 414 //index.php?action=httperror;c=414
ErrorDocument 415 //index.php?action=httperror;c=415
ErrorDocument 416 //index.php?action=httperror;c=416
ErrorDocument 417 //index.php?action=httperror;c=417
ErrorDocument 500 //index.php?action=httperror;c=500
ErrorDocument 501 //index.php?action=httperror;c=501
ErrorDocument 502 //index.php?action=httperror;c=502
ErrorDocument 503 //index.php?action=httperror;c=503
ErrorDocument 504 //index.php?action=httperror;c=504
ErrorDocument 505 //index.php?action=httperror;c=505
« Last Edit: October 11, 2017, 08:43:46 AM by Sacha »

Offline humbleworld

  • Sr. Member
  • ****
  • Posts: 886
    • best article
Re: Converting to https, step-by-step...
« Reply #34 on: December 26, 2017, 09:36:03 PM »
my forum, by default, has no www, and it is installed on a subdomain.

i tried this .htaccess file before but it was in conflict with prettyURL mod. How to fix it?

Offline shawnb61

  • Support Specialist
  • Full Member
  • *
  • Posts: 584
    • sbulen on GitHub
Re: Converting to https, step-by-step...
« Reply #35 on: December 27, 2017, 09:41:12 AM »
I think you're going to need to ask a few questions in the Pretty URLs support thread for a problem specific to that mod.   I see you asked once - be persistent.
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Offline Somegras

  • Newbie
  • *
  • Posts: 2
Re: Converting to https, step-by-step...
« Reply #36 on: December 29, 2017, 02:34:26 PM »
Followed this guide, https:// works but Google indicates that it is still not fully function (the green lock with info). How can I fix this?




Offline lurkalot

  • Sophist Member
  • *****
  • Posts: 1,016
  • Gender: Male
  • Tinyportal Support
    • guitaristguild on Facebook
    • Tinyportal on GitHub
    • @GuitaristGuild on Twitter
    • Guitarist Guild
Re: Converting to https, step-by-step...
« Reply #37 on: December 29, 2017, 02:54:16 PM »
Followed this guide, https:// works but Google indicates that it is still not fully function (the green lock with info). How can I fix this?



The address for your logo image at the bottom of the page

http://xsfserver.com/footerlogo.png

Change to

https://xsfserver.com/footerlogo.png

Offline Somegras

  • Newbie
  • *
  • Posts: 2
Re: Converting to https, step-by-step...
« Reply #38 on: December 29, 2017, 03:06:48 PM »
Followed this guide, https:// works but Google indicates that it is still not fully function (the green lock with info). How can I fix this?



The address for your logo image at the bottom of the page

hxxp:xsfserver.com/footerlogo.png [nonactive]

Change to

hxxp:xsfserver.com/footerlogo.png [nonactive]

Done, seems to have fixed everything for guests at the board index, however, when I am being logged in, it isn't functioning at the board index. If I go deeper in posts it sometimes works and sometimes doesn't.

Offline mrsfalcon

  • Semi-Newbie
  • *
  • Posts: 20
Re: Converting to https, step-by-step...
« Reply #39 on: January 03, 2018, 12:24:36 PM »
Thanks for this! Switched to https a while back but just forced it this am along with some other upgrades to improve safety and performance. I had some unhappy users but fixed the problem quickly with your instructions!