- Newest
- Most votes
- Most comments
The increase in cost after the SSL installation on GCP likely came from unintended usage like excessive egress traffic or misconfigured services running in the background.
Now that you're on Lightsail and have SSL set up yourself, it's a good step forward. However, past misconfigurations (like incorrect DNS records, SMTP errors, or bad redirection rules) can still affect your site if they've carried over during the migration or remain in your WordPress database or .htaccess
file.
Regarding max_execution_time
and max_input_time
In Lightsail, you can modify these PHP settings by creating or editing a custom php.ini
file, typically at /opt/bitnami/php/etc/php.ini
if you're using the Bitnami stack.
-
SSH into your instance.
-
Run:
sudo nano /opt/bitnami/php/etc/php.ini
-
Search for
max_execution_time
andmax_input_time
, and increase their values, e.g.:max_execution_time = 300 max_input_time = 300
-
Restart the PHP-FPM and web server:
sudo /opt/bitnami/ctlscript.sh restart
GA4 & Non-Indexed Pages
The links Google sends you could be:
- Legacy URLs from your old GCP setup
- URLs in your sitemap that no longer exist
- Auto-generated WordPress URLs (tags, search pages, etc.)
Check your sitemap, clear unused redirects, and use the Google Search Console "URL Inspection" tool to review what Google sees.
SMTP & Login Lockouts
SMTP issues could stem from:
- Old plugin settings (e.g., pointing to GCP IPs)
- Missing or misconfigured SPF/DKIM/DMARC records
- IP reputation issues from your previous host
You might consider using a trusted SMTP provider like SendGrid, Mailgun, or Amazon SES to stabilize email delivery.
Relevant content
- asked a year ago