Make the transition of an existing UBB.threads forum from http to https.
Summary 1) Obtain a valid security certificate from your webhost or a reputable third-party seller. I've purchased many "PositiveSSL" certs from SSLs.com. 2) Install it using SHA-2 and make sure it is configured properly. 3) Update ALL your URLs in the Control Panel or manually in your config.ini file. This includes the Homepage URLs, Contact pages, Referer Check, any forum headers/footers, etc. 4) Run a SQL query on your posts, private messages, user avatars, profile comments tables to replace "http://www.YOURDOMAIN.COM" with "https://www.YOURDOMAIN.COM" 5) Set up HTTP to HTTPS 301 redirects in your .htaccess file to forward from http:// to https:// 6) Update all external plugins to ensure they are HTTPS compliant (sharaholic, twitter, facebook, youtube, ubb custom-tags, and, if your website contains non-UBB.threads content, all those internal site links - trust me you won't find them all in a single pass) 7) Test your website. BONUS: Update your URLs in google/bing webmaster tools. Update any ads placed on your website, such as Google Adsense. Update any website analytics code.
** MAKE A BACKUP BEFORE YOU BEGIN **
UPDATE 2019-07-02: As of UBB.threads 7.7.2 a simple 1-click utility is built-in to accomplish the database transactions for you.
Control Panel > Content Rebuilder > Transition Actions: Update Forum URL References from HTTP to HTTPS
The 1-click utility performs the following updates:
The SQL ** BE VERY CAREFUL OF "POST_DEFAULT_BODY" and "POST_BODY" USAGE - DO NOT INTERCHANGE THEM • POST_DEFAULT_BODY - [BBcode] This is the original post. CONTENT REBUILDER > REBUILD POSTS takes this and converts it to POST_BODY [HTML] • POST_BODY - [HTML] This is shown to the user. it is generated from POST_DEFAULT_BODY
To update your POSTS: * ubbt_POSTS - POST_DEFAULT_BODY
Code
UPDATE ubbt_POSTS
SET POST_DEFAULT_BODY = replace(POST_DEFAULT_BODY, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
* ubbt_POSTS - POST_BODY
Code
UPDATE ubbt_POSTS
SET POST_BODY = replace(POST_BODY, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
To update your PRIVATE MESSAGES: * ubbt_PRIVATE_MESSAGE_POSTS - POST_DEFAULT_BODY
Code
UPDATE ubbt_PRIVATE_MESSAGE_POSTS
SET POST_DEFAULT_BODY = replace(POST_DEFAULT_BODY, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
* ubbt_PRIVATE_MESSAGE_POSTS - POST_BODY
Code
UPDATE ubbt_PRIVATE_MESSAGE_POSTS
SET POST_BODY = replace(POST_BODY, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
To update your USER AVATARS: * ubbt_USER_PROFILE - USER_AVATAR
Code
UPDATE ubbt_USER_PROFILE
SET USER_AVATAR = replace(USER_AVATAR, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
To update your PROFILE COMMENTS: * ubbt_PROFILE_COMMENTS - COMMENT_BODY
Code
UPDATE ubbt_PROFILE_COMMENTS
SET COMMENT_BODY = replace(COMMENT_BODY, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
To update your USER SIGNATURES: * ubbt_USER_PROFILE - USER_DEFAULT_SIGNATURE
Code
UPDATE ubbt_USER_PROFILE
SET USER_DEFAULT_SIGNATURE = replace(USER_DEFAULT_SIGNATURE, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
* ubbt_USER_PROFILE - USER_SIGNATURE
Code
UPDATE ubbt_USER_PROFILE
SET USER_SIGNATURE = replace(USER_SIGNATURE, 'http://www.YOURDOMAIN.COM', 'https://www.YOURDOMAIN.COM');
HTTP to HTTPS 301 Redirects For Your .htaccess File
Code
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Notes and Further Reading Full URLs (http:// and https://) vs relative URLs (//): If you want to correctly FULLY go SSL, use the full protocol name of "https://www.YOURDOMAIN.COM" instead of just "//www.YOURDOMAIN.COM" The reason to use just double slashes instead of the HTTPS protocol declaration, is if you intend to have your secure urls (https) distribute different content than your open urls (http), since both are seen as separate urls on search engines.
If you are switching to HTTPS, it is advised to fully replace all your http protocol references with https, and forward all calls from http to https. Do not allow the browser/end-user to choose http by leaving your protocol blank with an open "//" url.
Sometimes IE7 and IE8 do not correctly handle "//" assets. They look at this as being a file transfer, and will attempt to download the page through a download window. Even though the "//" asset is a spec from 1996/1998 https://www.paulirish.com/2010/the-protocol-relative-url/
Google SEO HTTPS Migration Checklist (for the ad and SEO focused) Source: Search Engine Roundtable • Update all your ad code to support HTTPS • Ensure your analytics will work on the new HTTPS URLs • Update your site search (if not using the inbuilt UBB.threads search methods) to support HTTPS and discover new URLs sooner • Create and submit your new HTTPS XML sitemaps • Review the Google site move article • Verify the new HTTPS site with Google Webmaster Tools and track indexation, crawling, search queries, etc.
Final Steps • Test your site using the Qualys Lab tool • Followup by searching for, and reading additional articles on "http to https site moves," to know what to expect
I also thought this to be complicated my first time I did it. But isaac laid it out step by step to follow.and it really is easy to do.
First step is the ssl certificate that has to be installed on the server via the hosting control panel. Be it either a free one provided by the host or a private purchased one. To me that was the hard step.
Then just follow the directions given above..
As far as paths in the ubb control panel goes. paths that have the http:// are the only paths that need to change to https://
For number 4 there is a selection in the re builders now that will run all the query's for you automatically.. You just click on the link and it runs. As far as cloudflare , yes they provide a free ssl if you use them as a proxy.
Yes that is because you're using a Content Delivery Network (CloudFlare; not a proxy), they provide a free SSL for all accounts; it is what I use on all of my sites.
I force all HTTP traffic to HTTPs through a CloudFlare Page Rule:
Quote
If the URL matches: example.tld/*
Then the settings are: Forwarding URL, 301 Redirect https://www.example.tld/$1
The above forces WWW, you could also just trigger for non-HTTPS by:
Quote
If the URL matches: http://*.agardenersforum.com/*
Then the settings are: Always Use HTTPS
If you're already using HTTPs through CF steps 1/2 are moot. For the rest you just need to access UBB.threads over HTTPs and run the rebuilder " Update Forum URL References from HTTP to HTTPS".
![[Linked Image]](https://www.ubbcentral.com/forums/ubbthreads.php/ubb/download/Number/2527/filename/HTTPS SEO Checklist.jpg)
