I still new for Bitnami serve.
Now i setup Bitnami server on AWS. I still don't have Domain name. Right now, im using IP Domain to access it. the question is, Do i really can setup SSL encryption (HTTPS) by using IP domain?
i was followed this documentation https://docs.bitnami.com/general/how-to/generate-install-lets-encrypt-ssl/
but it required domain name.
please help
Here a bitnami engineer, if you want to use HTTPS you need a domain. Let's Encrypt not allow IP, you need to search another or create a self-signed certificate.
To the last one, you can use OpenSSL.
Related
Because of resource and performance problems I want to move my website from Shared hosting to VPS. In this process, I also want to migrate from PHP 5.6 to PHP 7.4. Therefore I need to re-code the PHP scripts. So I need time for my own on the new Plesk server to get things done.
I have the next steps in mind:
Create the webspace with the domain name on Plesk.
Upload the sources and database to the VPS.
Install an SSL certificate on the new site.
Add the domain name to the hosts file.
Re-code and test the new site.
Change the DNS to the new IPs.
There is a deadlock situation, however.
I can not issue a new SSL certificate without changing the DNS.
I can not migrate and test the site without an SSL certificate.
Of course, this is done before by many developers, but how it's done?
Does anyone know? And which other problems can I expect?
Purchase a wildcard certificate or create one by letsencrypt
And use a subdomain like test.yourdomaine
And point it to your reverse proxy vps new ip
I have a domain purchased at 1and1 and set up at AWS EC2 with SSL and Apache server.
Even the domain pointing to the correct IP (using nslookup I can see it), it works from some places and not from others.
For example, here from my workplace, I see this page (the domain does not reach the EC2 server):
I launched a Windows EC2 at AWS to make a test and from there, everything is correct (the page loads and SSL is valid):
From my client's computer, it has another behavior. It reaches the EC2 server, but is says the SSL is invalid:
Has anyone faced the same problem?
The first thing you need to do is get an Elastic IP, the instance IP can change during reboot etc but elastic IP are static IP’s so you should make sure you create one of them and assign it your running instance.
Create Hosted Zone and Record Sets
Documentation is here - https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingHostedZone.html
Create a recordset and add values
Add the Amazon NameSpaceServers in Control panel of Domain Provider
Import the SSl certificate to AWS Certificate manager (Optional). Documentation is here https://docs.aws.amazon.com/acm/latest/userguide/import-certificate-api-cli.html#import-certificate-api
Self signed certificate will not work.
Deploy the SSl certificate into Apache server and configure the traffic for https.
Open the AWS in-bond traffic port documentation is here - https://aws.amazon.com/premiumsupport/knowledge-center/connect-http-https-ec2/
I have a https web app running on my aws ec2 instance.
https://ec2-52-91-100-69.compute-1.amazonaws.com/
I need to get a ssl certificate for the same so that the scary warnings do not appear.
How can I do this? I tried to buy a ssl from clickssl.com but their helpdesk emailed me with the following:
"You completed enrollment process for domain name
ec2-52-91-100-69.compute-1.amazonaws.com.
I believe you cannot get SSL for this domain name because root domain
name amazonaws.com is Amazon property."
If this is the case is there no way to get a ssl certificate for my application? I dont believe thats the case.
Any help will be appreciated.
First you need to register a domain through a registrar (e.g. GoDaddy or Amazon Route 53). Next you assign an Elastic IP to your EC2 instance and use your registrar's DNS tool to make your domain point to the Elastic IP address. Then you can request an SSL certificate for your own domain.
You do need to register a domain, or use a subdomain of a domain you already have registered. You do NOT need to use an Elastic IP - they are limited and eventually (if you use multiple domains in your AWS account) you will run out. Instead, you can use a CNAME to point to the AWS name (e.g., ec2-52-91-100-69.compute-1.amazonaws.com).
Once you have that set, use Let's Encrypt to get a free widely accepted certificate. There are plenty of tutorials on the installation process - try:
https://ivopetkov.com/b/let-s-encrypt-on-ec2/
Just noticed the original question is OLD - which means (among other things) that Let's Encrypt wasn't even an option at the time. But for anyone who stumbles across this question now, it is a great solution.
I am using a VPS which doesn't host any website, or domain name. I need to remote-access that VPS using Remote Desktop.
To be sure no one is eavesdropping my traffic with the VPS, I need to setup an SSL certificate on the server. But the first thing they ask is a Fully Qualified Domain Name. Is there any way I can skip creating a domain that I don't need in order to buy the certificate? Since I will only need it for my remote desktop sessions?
Here are the facts:
1- You need a fully qualified domain name to request a certificate.
2- You don't have to bind the domain to the server in case you don't want to.
3- After installing the certificate, if the server address is not the same as the domain associated with the certificate, you will get a warning that the address doesn't match the certificate.
Hope this will help anyone who has case similar to mine.
I use SSL certificate for a web site I set up in Amazon EC2 Machine Instance. The SSL certificate is for one domain name, which is not public DNS for the Amazon Machine Instance. The browser always complains the mismatch in the domain name because it compares the domain name of the SSL certificate to the Amazon public DNS.
How can I set up not to cause this problem?
I tried both domain name forwarding and A Record setting.
Maybe it's because I'm not so familiar with Amazon EC2 and I haven't configured domain name correctly.
Any help will be greatly appreciated.
The browser compares the domain name that you've typed in the address bar with the domain name in the certificate. If they're different then there's an error: that's by design.
The way to "fix" this is to buy a certificate for whatever domain name you type into the browser to get to the EC2 instance: mywebsite.com, not ec2-x-y-z.compute-1.amazonaws.com or whatever...
After that the instance has an IP you can setup a domain name with it if you want. The easiest way is you can use through a DNS service like EveryDNS. Just provide your domain name registrar with EveryDNS’s domain name servers, create an EveryDNS account, add your domain and create an A record with your newly associated EC2 instance IP address.
after that you have to get a certificate for that domain name.If you do these steps and still having problems pls let me know.
also you can read here for further details.
and i faced same problem before you can check the amazon forums for the exact answer