Github
$ ssh -T git@github.com $ git@github.com: Permission denied (publickey).
Huh?
The .ssh directory itself looks fine.
Checked logs with
ssh -vT git@github.com
or
ssh -vvv git@github.com
Error traces point to the key.
Checked Github SSH Key on the web page.
It’s gone!
Turns out SSH public keys have an expiration date and get automatically deleted.
Recreated and set it up. Problem solved.
Github’s access method has changed.
「git push -u origin develop」
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
Password authentication is now deprecated and replaced with access token method.
You need to log into Github on the web and create an access token.
１．Open the settings page( https://github.com/settings/tokens )
２．Click [Generate new token]
３．Enter an appropriate token name in the note field
４．Set permissions (need at least [repo] permission if modifying repositories)
５．Click [Generate token]
６．Save the generated token ★Important! Copy the token displayed here
★[repo] permission required to access repositories
★[workflows] permission required to update GitHub Actions
★Due to security constraints, token expiration can only be set up to max 360 days
git push -u origin develop Username for 'https://github.com': hogehoge Password for 'https://hogehoge@github.com':★
hogehoge = username
★ = token
You can now access with these credentials
Apache 2.4.39
[.htaccess] Or [httpd.conf]
# Set allowed IPs to 0.0.0.0 # AWS ELB admin screen access control <location "/wp-admin"> # Admin IP SetEnvIf X-Forwarded-For "0.0.0.0.*" allowed_ip_admin SetEnvIf X-Forwarded-For "0.0.0.0.*" allowed_ip_admin Order Deny,Allow Deny from all Allow from env=allowed_ip_admin </location>
Notes on things to watch
– Register the SMTP Server’s Global IP as an A host record in DNS
– Register SPF record in DNS
– Register DMARC record in DNS
– Register DKIM record in DNS (if needed—about 35% adoption as of June 2019)
■MX, SPF and other mail server verification tools
■DMARC record check tool
– For AWS, submit a request to remove SMTP sending restrictions
■About removing AWS SMTP sending restrictions
To avoid being flagged as spam mail
– Set “Reply-to” in outgoing emails from your system
Received an error when attempting to add an Elastic IP.
By default, Elastic IP has a limit of 5 addresses. You need to submit a request to increase this limit.
You’ll get a response in about 30 minutes.
Request link: Elastic IP request form
Important! Make sure you’re logged into AWS before clicking the link.
■When IP addresses are needed for a new service
Limit increase request 1
Service: Elastic IPs
Region: Asia Pacific (Tokyo)
Limit name: EC2-Classic Elastic IP address limit
Requested limit: 10
------------
Description of request reason: IP address is required to build a new service