Unlike my typical tutorial formats, this one will be a near copy/paste from an email I sent to a real person so that other real people can connect this to their real brain and emotions:
I’m going to forewarn you that this email is dripping with anger/frustration so try to just plunder through it and even try to enjoy it if you can….
Apple/mac is nuts. I can’t put into words how much I can’t stand the company.
They do everything under the sun to make their users dumb and compliant – in fact, it’s creepy if you think about this…. I remember now (after this morning) why I full scale boycotted Apple and threw this iPod in the ‘smartphone trash pile’.
I will stop my rant here.
<insulting section about all iphone users removed>
But, back to the solution because at this point I just want to get our calendars working for the next few months, but please let me put in a plug here to strongly consider the company you are supporting and know that yes, there is a way to totally escape the Apple corporation forever. – It’s called Ubuntu. I hope your next move is far away from these guys… I leave it with you and I promise to dedicate all my free time to helping you if/when you are ready to make the move. Until then I hope I never have to turn this stupid thing on again:
Do this in this impossible-to-imagine difficult workaround solution, and I hope by God’s grace that your ‘issue’ is the same one I’m having here which has everything to do with the Fruit Co. and their ‘ways’.,,,
1. go to ‘settings’
2. go to ‘mail/contacts/calendars, etc’
3. add account
4. go to ‘other’ (because they weren’t respectful enough to give calDav and iCal a title or it’s own option space)
5. add calDAV account (*not* calendar subscription because it seems this fruit co can’t make this work without upgrading to the $10,000 phone or buying the latest fruit air laptop to go with it…??)
6. server: YOURSERVER.COM
7. user name: YOURCLOUDUSERNAME
8. password: your cloud password
9. description: your creative name for calendars
10. hit ‘next’
now here is where it gets *real lame*. It will say want to continue without SSL? Sure, no problem:
11. continue (yes, i will move forward without SSL)(why? Because fruit co is not secure so why bother with https? in fact, let’s make it *not work at all*)(let’s encrypt is legit SSL and it doesn’t want to work)
12. you will get “unable to verify account information” error. Why? No reason. Just because they want you to use their systems… but let’s overcome!
14. advanced settings
15. change whatever port number is listed there to 80
16. make sure SSL is off (should be)
17. go back (which somehow saves these settings even though there was no indication saving was happening..?)
18. hit ‘next’
19. but it doesn’t work! cannot verify account details blah blah? why? Because for no explainable reason, the advanced settings just randomly chose its own URL for the calendar – randomly – as if somehow Fruit Corporation is supposed to know where your calendar is hosted? no problem. let’s overcome…
20. hit ‘advanced settings’
21. make sure the ‘account URL’ is set exactly to this: http://YOURSERVER.COM:80/YOURSUBDIRECTORY/remote.php/dav/principals/users/YOURUSERNAME/
22. go back
23. done (which somehow means save?)
Here is a summary of what the two screens should look like to make it more simple to make sure you ‘followed their rules’
user name: YOURCLOUDUSERNAME
password: YOUR CLOUD PASSWORD
descxription: some long url probably
2. advanced settings screen
use ssl: off
account url: http://YOURSERVER.COM:80/YOURSUBDIRECTORY/remote.php/dav/principals/users/YOURCLOUDUSERNAME/
Now, you *BETTER* report back to me that this @#$#$@#$@#$@#$ is working or I’ll @#$@#$
<SMASHES FACE ON DESK>
Wayne Out There
Well, it has been quite a journey of learning and it has been quite good. Green Geeks, a big American website hosting company upset myself and a few other customers about their unwillingness to support the latest and best free and open encryption service, Let’s Encrypt. They wanted to sell their SSL certificates instead. The mentality is quite different from this hosting company that we found called Siteground who looks at the big picture. Let me think for a second. I’m a customer. I want to choose my hosting company. One company says ‘come over here and we’ll let you do your own certificates or we’ll sell you one” or company B says ‘We will sell you one and it’s our way or the highway.” Which one will I choose? Green Geeks needs to wake up and smell the coffee.
Anyway, Green Geeks forced me to figure it out by myself but it’s working. I got SSL installed on all my domains at Green Geeks. You can read my tutorial about how to do that here.
Now that you have your SSL stuff installed you probably are like me and have a bunch of Word Press sites. What you will find is you will probably get warnings that look like triangles, exclamation marks, etc, etc.
First, your best resource that I found through this process is this website where you can type in your domain and it will spit back the cause of your no-padlock SSL certificate problem.
Next, you’ll probably find this blog very educational and might help you decide a course of action that is slightly different from my decision to ‘just fix it quick’. For me, my blogs weren’t highly important (like this one) so experimenting didn’t bother me.
Now, without further adieu, here is the ‘quick fix solution’ to the ‘no padlock error in a Word Press website. Just install this plugin and, if it doesn’t fix by default, change the setting to match mine in the screen shot below.
Bonus Feature! Force your Word Press Site to Use HTTPS
Now that you’ve gone to the trouble of making SSL work and then fixing all the errors, why not force all traffic to run via HTTPS so your site is hyper secure? It’s easy with this this plugin. Just… well. Plug it in. And done.
Hopefully everything here works smoothly for you as it did for me. You’ll note my success since I did this tutorial to this blog! 😉