Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
techwiki:host_godaddy [2022/02/27 19:12] – [Multiple SSL Guide] ying | techwiki:host_godaddy [2023/06/29 15:25] (current) – [SSL Guide] ying | ||
---|---|---|---|
Line 47: | Line 47: | ||
- put the domain name, then it shows nameservers, | - put the domain name, then it shows nameservers, | ||
- then, that domain will show as available on godaddy domain section, and ready for related domain settings | - then, that domain will show as available on godaddy domain section, and ready for related domain settings | ||
+ | |||
+ | * subdomain creation manually: | ||
+ | * https:// | ||
* domain transfer into godaddy | * domain transfer into godaddy | ||
Line 74: | 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 ====== | ||
* you can buy ssl just for primary domain, you can also buy ssl just for one of secondary/ | * you can buy ssl just for primary domain, you can also buy ssl just for one of secondary/ | ||
- | + | * for single domain case (updated 2022) (primary or addon) | |
- | * for single domain case (primary or addon) | + | - buy ssl |
+ | - go additional product to setup | ||
+ | - enter domain name for ssl (domain can be domain managed by godaddy or other party, but you need admin email for that domain) | ||
+ | - choose ssl issuer, both is fine. just go for first option and agree | ||
+ | - (note, if your domain and hosting both under godaddy, seems, it is auto verified and you can directly go Certificate tab under SSL to see it, refresh in 1-2min, thus you may not need the email steps if you see issued, just go step cPanel) | ||
+ | - choose verification method: admin@yourdomain.com and txt method (email is very useful, since you will get email instruction, | ||
+ | - go email, (normally within 10min, you can use resend in ssl page to send again, normally into your spam box called verify) | ||
+ | - click the email inside to confirm, go ssl page to refresh (it will show verification complete), within 2-3 min, below will show status issued | ||
+ | - go cPanel > SSL/TLS | ||
+ | - under " | ||
+ | * under " | ||
+ | * browse certificate, | ||
+ | - ssl done, you should see lock when browse site with https | ||
+ | * for single domain case (old) (primary or addon) | ||
- buy ssl | - buy ssl | ||
- go additional product to setup | - go additional product to setup | ||
Line 154: | Line 195: | ||
- (Final) to check your installed SSL on your cPanel, go cPanel > SSL : bottom link " | - (Final) to check your installed SSL on your cPanel, go cPanel > SSL : bottom link " | ||
* (Specially note: it seems even I put www.mydomain.com for addition domain of ucc ssl, mydomain.com also has lock, seems godaddy now offer free coverage for both www and non www now. lol) | * (Specially note: it seems even I put www.mydomain.com for addition domain of ucc ssl, mydomain.com also has lock, seems godaddy now offer free coverage for both www and non www now. lol) | ||
+ | - (Final extra) it seems only main domain ssl is auto installed, the rest domain need one manual extra click | ||
+ | * go " | ||
+ | * once loaded, click install certification button at bottom, then it is done for that domain. (seems only defined domain name format is secured, if I put www.TheDomain.com, | ||
- | **Fix parts of content for page not secure after new ssl install** | + | ====== Fix some content not secure issue after SSL update ====== |
+ | |||
+ | Fix parts of content for page not secure after new ssl install | ||
* for wordpress site case, just install a plugin to auto fix it | * for wordpress site case, just install a plugin to auto fix it | ||
* Really Simple SSL: https:// | * Really Simple SSL: https:// | ||
* WP Force SSL: https:// | * WP Force SSL: https:// | ||
- | * if you like to manual fix, go firefox console, you should see the list of content that is not secure | + | |
+ | if you like to manual fix, go firefox console, you should see the list of content that is not secure | ||
* check list | * check list | ||
- | - your custom css, content inside should change to https:// | + | - your custom css, content inside should change to https link |
- image, css, js linked from other non ssl site, should move to your own site | - image, css, js linked from other non ssl site, should move to your own site | ||
+ | - ref: https:// | ||
+ | - [better backup first before this step] https:// | ||
+ | * elementor > tool > replace : http:// | ||
====== End or Remove Product ====== | ====== End or Remove Product ====== | ||
Line 197: | Line 247: | ||
* notes: htacess may different for other hosting providers | * notes: htacess may different for other hosting providers | ||
+ | ===== Mail RoundCube error Connection to storage server failed ===== | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * basically, check your host provider |