Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| techwiki:host_godaddy [2023/06/29 15:12] – [Multiple SSL Guide] ying | techwiki:host_godaddy [2023/06/29 15:25] (current) – [SSL Guide] ying | ||
|---|---|---|---|
| Line 77: | Line 77: | ||
| For office365 email, since each main email cost money, you may add alias for main email like info@ or contact@ to catch email to main email for free: https:// | For office365 email, since each main email cost money, you may add alias for main email like info@ or contact@ to catch email to main email for free: https:// | ||
| + | ====== some notes before setup SSL ====== | ||
| + | |||
| + | **if you install wordpress with http home link type** | ||
| + | * read below first, you may understand why this process may be your option before setup SSL | ||
| + | * once you setup purchased SSL, you may have to update wordpress all links from old http to https | ||
| + | * so before SSL setup, use installatron or whatever to backup http version of current wordpress | ||
| + | * delete the wordpress installation on server | ||
| + | * install SSL as process below | ||
| + | * restore the installatron backup to new location, and choose https link of the site domain | ||
| + | * or install fresh wordpress with https link and restore old backup content into new wordpress | ||
| + | * that way, most wordpress default link will be updated in new site with https | ||
| + | |||
| + | **alternative, | ||
| + | * this method, SSL update process below basically use your 3rd party signed certificate instead of your self-sign certificate | ||
| + | * while you develop the site, just add exception to your self sign certificate to continue development process | ||
| + | * once later update the new SSL, there is no need to update https links, as it is https link at start, just you need to tell browser to allow you continue visit site | ||
| + | * drawback, while if you build site for someone else, they also need to add exception to browser when they visit the site before you use purchased ssl | ||
| + | |||
| + | **or, just purchase the SSL before you do any site** | ||
| + | * that way, you dont need to do any update process as above 2 method, | ||
| + | * but you lose the certificate time as you develop the site and not show to public | ||
| + | * if your site take half year to build, then you waste half year of certificate time for your purchased ssl certificate | ||
| + | |||
| + | now, you can read below process to decide which is your best workflow for SSL update | ||
| + | |||
| ====== SSL Guide ====== | ====== SSL Guide ====== | ||