Table of Contents
Installing WordPress Was the Easy Part
I thought installing WordPress on GCP would be the difficult part.
It wasn’t.
The real problem started when I tried to set up SSL.
At first, everything seemed simple. I had already launched a small free-tier GCP server, connected my domain, and installed WordPress successfully. The site worked, but it still showed the dreaded “Not Secure” warning in the browser.
That was the moment I realized the easy part was over.
Why SSL Became Confusing
Like many beginners, I thought enabling HTTPS would take only a few clicks. Most tutorials make it look effortless. Just install a plugin, activate SSL, and everything magically works.
That was not my experience.
I started with a plugin called Really Simple SSL because almost every tutorial recommended it. The plugin itself was easy to install, but after activating it, my site became unstable.
Some pages loaded with HTTPS while others did not.
Sometimes the browser still showed warnings.
Sometimes images disappeared.
At one point, I thought I had broken the entire site.
The Plugin That Made Things Worse
Then I discovered something most beginner tutorials barely explain:
SSL is not just a WordPress setting.
It involves:
- the server
- the domain
- DNS settings
- certificates
- redirect rules
- and sometimes the web server configuration itself
That was the point where I realized I had no idea what I was doing.
I spent hours opening random tutorials, SSH windows, DNS dashboards, and WordPress settings pages. Every guide assumed I already understood concepts that I had never used before.
What Beginner Tutorials Rarely Explain
Some tutorials used Certbot.
Others used Cloudflare.
Some edited Apache configuration files directly.
Others relied completely on plugins.
I kept switching between methods because I thought one of them would magically fix everything.
Instead, I only became more confused.
At one point, I was staring at my SSH terminal wondering why a “simple SSL setup” suddenly involved Linux commands.
The funniest part is that installing WordPress itself took less than an hour.
SSL took me several days.
Getting Lost Between Different SSL Methods
The biggest problem was not technical difficulty.
It was uncertainty.
Every change felt dangerous because I did not fully understand how the pieces connected together.
If DNS was wrong, SSL failed.
If redirects were wrong, the site looped infinitely.
If certificates were missing, browsers showed warnings.
And because I was using a free GCP server, I constantly worried that I would accidentally create some paid resource while trying to fix things.
That anxiety probably slowed me down more than the actual setup.
What Finally Worked
Eventually, I managed to stabilize everything using:
- Certbot
- proper DNS settings
- HTTPS redirects
- and a much simpler setup than the one I started with
Ironically, the more tutorials I read, the more complicated everything became.
The final solution was actually smaller and cleaner than I expected.
Final Thoughts
Looking back now, I think SSL setup is one of those things that sounds easy only if you already understand servers.
For beginners, it feels like entering a completely different world hidden behind WordPress.
And honestly, that experience changed the way I look at “simple tutorials” online.
Many guides skip the confusion part.
But the confusion is the real experience.
Especially on GCP.
If you are currently struggling with SSL on a WordPress server, you are probably not doing as badly as you think. Most of the stress comes from trying to connect systems that were never explained clearly in the first place.
Installing WordPress was easy.
Understanding how everything around it worked was the difficult part.
📌 Previous: GCP Google Cloud’s Bitter Billing Trap #2
👉 Next: WordPress Menus are confusing #4