You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users with stricter security measures on their computers cannot open our links in emails because they currently use http. Additionally, adopting https is a best practice to ensure secure and trusted connections. This setup will address the issue and align with modern security standards by enabling HTTPS for link.url7680.socialincome.org.
Solution: Setting Up a Google Cloud Free Tier f1-micro Instance for HTTPS and SendGrid Click Tracking
Follow these steps to configure an f1-micro instance on Google Cloud to handle HTTPS for your subdomain (link.url7680.socialincome.org) and forward traffic to SendGrid.
Step 2: Set Up a Free VM Instance
Create a Project:
Go to Manage Resources in Google Cloud.
Click Create Project and name it (e.g., SendGridProxy).
Go to Compute Engine:
Navigate to Compute Engine > VM Instances.
Click Create Instance.
Configure the Instance:
Name: nginx-server.
Region: Choose a free tier eligible region (e.g., us-west1, us-east1).
Machine Type: f1-micro.
Boot Disk: Use the default Debian or Ubuntu image.
Firewall: Check Allow HTTP traffic and Allow HTTPS traffic.
Certbot will automatically configure NGINX to use the SSL certificate.
During the process, Certbot will verify that you own the subdomain by checking your DNS records. Ensure your DNS is correctly configured before proceeding.
Verify the SSL certificate:
Once the process is complete, visit your subdomain in a browser:
Navigate to https://link.url7680.socialincome.org.
Confirm the page loads securely (check for a padlock icon in the address bar).
Step 6: Update DNS Records in GoDaddy
Log in to your GoDaddy account.
Add an A Record:
Type: A
Name: click
Value: Your VM’s external IP (found under Compute Engine > VM Instances).
TTL: Default (1 hour).
Wait for DNS propagation (may take a few minutes).
Issue
Some users with stricter security measures on their computers cannot open our links in emails because they currently use http. Additionally, adopting https is a best practice to ensure secure and trusted connections. This setup will address the issue and align with modern security standards by enabling HTTPS for link.url7680.socialincome.org.
Solution: Setting Up a Google Cloud Free Tier f1-micro Instance for HTTPS and SendGrid Click Tracking
Follow these steps to configure an f1-micro instance on Google Cloud to handle HTTPS for your subdomain (
link.url7680.socialincome.org
) and forward traffic to SendGrid.Step 2: Set Up a Free VM Instance
Create a Project:
SendGridProxy
).Go to Compute Engine:
Configure the Instance:
nginx-server
.us-west1
,us-east1
).f1-micro
.Step 3: Connect to Your VM
Step 4: Install NGINX
Step 5: Install Certbot for SSL
To secure your subdomain with HTTPS using a free SSL certificate from Let’s Encrypt, follow these steps:
Install Certbot and the NGINX plugin:
Run the following command to install Certbot on your VM:
Obtain the SSL certificate:
Use Certbot to generate an SSL certificate for your subdomain:
Verify the SSL certificate:
Once the process is complete, visit your subdomain in a browser:
https://link.url7680.socialincome.org
.Step 6: Update DNS Records in GoDaddy
click
Step 7: Configure NGINX as a Proxy to SendGrid
Edit the NGINX configuration for your subdomain:
Add the following configuration:
Save and exit the file:
CTRL+O
, thenCTRL+X
.Enable the configuration and reload NGINX:
Step 8: Automate SSL Certificate Renewal
Step 9: Notify SendGrid
https://link.url7680.socialincome.org
) and request SSL click tracking.Step 10: Test the Setup
https://link.url7680.socialincome.org
.Cost Summary
Documentation
See also: SendGrid Support File
The text was updated successfully, but these errors were encountered: