Showing posts with label website. Show all posts
Showing posts with label website. Show all posts
Sunday, August 18, 2019
Sunday, July 21, 2019
Website Email: Amazon SES
Setting up email on my server isn't as straightforward as it may seem. Amazon is concerned about their servers being used for email spam and have implemented restrictions, forcing you to request a lift on these restrictions or use their SES program. However, with SES, the first 62,000 emails are free and it sounds like a legit service. So let's do it.
ALL
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/quick-start.html
VERIFY EMAIL ADDRESS
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-email-addresses.html
GETTING THE EMAIL ADDRESS IN THE FIRST PLACE
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-sendmail.html
IAM User: howtocureinsomnia.emailserver.iam
SMTP Username:
In OneDrive (in web folder not in remembers)
SMTP Password:
In OneDrive (in web folder not in remembers)
ALL
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/quick-start.html
VERIFY EMAIL ADDRESS
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-email-addresses.html
GETTING THE EMAIL ADDRESS IN THE FIRST PLACE
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-sendmail.html
If you're using Amazon SES to send email from an Amazon EC2 instance, you should also complete the following steps:
- If you're using Amazon SES to send email from an Amazon EC2 instance, you might need to assign an Elastic IP Address to your Amazon EC2 instance in order for receiving email providers to accept your email. For more information, see Amazon EC2 Elastic IP Addresses.
- If you're using Amazon SES to send email from an Amazon EC2 instance, you should complete the Request to Remove Email Sending Limitations form. Requesting this change removes the sending limit restrictions that Amazon EC2 applies to port 25 by default.
IAM User Name: howtocureinsomnia.emailserver.iam
The new user will be granted the following IAM policy:
"Statement": [{ "Effect":"Allow", "Action":"ses:SendRawEmail", "Resource":"*"}]
IAM User: howtocureinsomnia.emailserver.iam
SMTP Username:
In OneDrive (in web folder not in remembers)
SMTP Password:
In OneDrive (in web folder not in remembers)
Scratch all that! You should NOT be hosting your own webserver!
I just need an email name.
Email names come from some kind of email registry, the same way domain names come from a domain registry.
So I bought an email off of godaddy, but then found out godaddy doesn't control my domain - AMAZON does. lol
So I am trying to link it up with amazon... shit... kind of wish I didn't pay for a whole year... well, at least I didn't buy the backup service or any other etc shit.
Trying to link all that up in Route 53, but it's tricky. I am very unclear about the SRV records in particular, since amazon isn't really setup to accept the "protocol" and "service" fields. I set it up via BOTH solutions offered at the below link, and now I'm just waiting 24 hours for my work to propegate so I can know for sure that it's failing verification.
More Research Indicates that Email DOES come from server??
With cpanel, for instance, you can create as many "users" as you want.
With Amazon SES, you can verify email with an S3 bucket, install the email server of your choice (like cpanel's), and get as many emails as you want.
So.. what... the... faackk... dad was wrong??
Looking at this? https://aws.amazon.com/marketplace/pp/B072K5KX96?qid=1563765902151&sr=0-2&ref_=srh_res_product_title
Amazon also has "Amazon WorkMail"
Monday, July 15, 2019
Worpress Reset
So, first thing I come to is updating PHP so I can be compatible with the newest wordpress. I quickly come to the conclusion that this is something i must do in linux.
https://code.tutsplus.com/tutorials/upgrading-your-linux-server-to-php-7--cms-27583
I start reading and first thing up: "Go ahead and purge all the current PHP"
and I'm like... "ahhh... yeah... about that..."
And now I am creating a copy AMI so if something goes wrong I have a 7/15/19 backup image to run from. Only took about 2-5 minutes.
This guide is better actually:
https://fizzbuzzer.com/upgrading-php7-amazon-linux-ec2-instance/
And now I realize my server probably hasn't been updated since 2015. Which is probably a PRETTY BIG DEAL.... ooo boy
step 1
"
"
lol... fack
....
https://code.tutsplus.com/tutorials/upgrading-your-linux-server-to-php-7--cms-27583
I start reading and first thing up: "Go ahead and purge all the current PHP"
and I'm like... "ahhh... yeah... about that..."
And now I am creating a copy AMI so if something goes wrong I have a 7/15/19 backup image to run from. Only took about 2-5 minutes.
This guide is better actually:
https://fizzbuzzer.com/upgrading-php7-amazon-linux-ec2-instance/
And now I realize my server probably hasn't been updated since 2015. Which is probably a PRETTY BIG DEAL.... ooo boy
step 1
"
Login to your Linux instance and perform the regular system updates first
1
|
$ sudo yum update
|
lol... fack
....
Some things to note about SUDO / Service / Linux
1. You're using linux, not unix. lol
2. service commands like restart for things like httpd and mysqld require SUDO
EX:
$ service mysqld restart
cat: /var/run/mysqld/mysqld.pid: Permission denied
$ sudo service mysqld restart
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
:)
New FTP User Created
user: press
pass: std23
Seems to work!!
Setting up SSH on AMI Linux
Amazon: FAILED
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-amazon-linux-2.html
GoDaddy / Linux: FAILED
https://www.godaddy.com/help/manually-install-an-ssl-certificate-on-my-apache-server-centos-5238
GoDaddy / AWS Server: FAILED - DO NOT USE THIS STRAT... Will cost more money and not the legit way to go...
https://www.godaddy.com/help/manually-install-an-ssl-certificate-on-my-aws-server-32075
Well, after going 2.5 hours over the budget it's pretty clear this is going to take more work than I have time for to meet "live" deadline. Will implement first thing after going live.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-amazon-linux-2.html
GoDaddy / Linux: FAILED
https://www.godaddy.com/help/manually-install-an-ssl-certificate-on-my-apache-server-centos-5238
GoDaddy / AWS Server: FAILED - DO NOT USE THIS STRAT... Will cost more money and not the legit way to go...
https://www.godaddy.com/help/manually-install-an-ssl-certificate-on-my-aws-server-32075
Well, after going 2.5 hours over the budget it's pretty clear this is going to take more work than I have time for to meet "live" deadline. Will implement first thing after going live.
Warning - Security
Sunday, July 14, 2019
Website Recovery and Optimization
New objective added:
"Pre1: Get website back online, editing tools recovered, www working, update wordpress, and implement SSL"
I reset the server, which got website working, got all my editing tools back online, got www. working, but that's where I ran into issues... how to FTP so wordpress can install its own stuff... and then ran outta time before looking into updating.
I also did a backup of the server's HTML folder on my computer under _work\website and server\BACKUP so I could play around without ruining the site. Sounds like the config.wp file will be 100% needed.
WWW:
just made in AWS Route 53 tool. Key was just using an "a". added www. + ham. for fun.
FTP / Updating wordpress
https://entrepreneurisback.blogspot.com/search?q=ftp
particularly the "Day 37" post pointed me in the right direct
https://stackoverflow.com/questions/17768201/wordpress-on-ec2-requires-ftp-credentials-to-install-plugins
https://stackoverflow.com/questions/8686125/update-wordpress-theme-on-ec2
https://wordpress.org/support/article/updating-wordpress/
SSL:
http://www.howto-expert.com/how-to-get-https-setting-up-ssl-on-your-website/
...should be able to set it up with a plugin easy enough, but have to update wordpress for a decent plugin.
https://ssl-ccp.godaddy.com/wizard/create/DV_SSL/1/0?cb=&app=
NOTE: The private keys are @ _work\website and server\SSL
"Pre1: Get website back online, editing tools recovered, www working, update wordpress, and implement SSL"
I reset the server, which got website working, got all my editing tools back online, got www. working, but that's where I ran into issues... how to FTP so wordpress can install its own stuff... and then ran outta time before looking into updating.
I also did a backup of the server's HTML folder on my computer under _work\website and server\BACKUP so I could play around without ruining the site. Sounds like the config.wp file will be 100% needed.
WWW:
just made in AWS Route 53 tool. Key was just using an "a". added www. + ham. for fun.
FTP / Updating wordpress
https://entrepreneurisback.blogspot.com/search?q=ftp
particularly the "Day 37" post pointed me in the right direct
https://stackoverflow.com/questions/17768201/wordpress-on-ec2-requires-ftp-credentials-to-install-plugins
https://stackoverflow.com/questions/8686125/update-wordpress-theme-on-ec2
https://wordpress.org/support/article/updating-wordpress/
SSL:
http://www.howto-expert.com/how-to-get-https-setting-up-ssl-on-your-website/
...should be able to set it up with a plugin easy enough, but have to update wordpress for a decent plugin.
https://ssl-ccp.godaddy.com/wizard/create/DV_SSL/1/0?cb=&app=
NOTE: The private keys are @ _work\website and server\SSL
Subscribe to:
Posts (Atom)