I have instance running in oracle cloud and domain in Google Domains. I want to enable HTTPS, So I added A record in DNS with HOST name www and valid ip address
I want to use the let's encrypt SSL for the domain. I followed this link
https://certbot.eff.org/instructions?ws=apache&os=ubuntufocal
But still HTTPS is not working.
Note: I have domain ending with ".dev".
Added A record in DNS
followed this link
https://certbot.eff.org/instructions?ws=apache&os=ubuntufocal
Related
I have a domain purchased from Godaddy. Then a Virtual Machine setup on Azure with an web application installed on it.
So thus far I have:
An Azure VM with an application running on it, lets say the ip for the VM is 12.3.456.789
A domain name I purchased from godaddy, e.g mydomain.com, I then created a subdomain for e.g sub.mydomain.com
I then added an SSL certificate to this subdomain which worked fine, after I changed the DNS A record for the subdomain to the ip address of the VM 12.3.456.789, also the application on the VM is accessed on port 4000. So https://sub.mydomain.com:4000
The issue is that when I access my domain via https I get the ERR_SSL_PROTOCOL_ERROR in all browsers but when I access it via http then the application on it loads completely fine.
Any ideas on what I would have done wrong or left out in my setup?
Also if I did not provide enough information do let me know.
commercial SSL certs are always signed to include the TLD
(Top Level Domain -> in your hypothetical case: mydomain.com) !
You should contact godaddy to change the certificate to change the SAN (Subject alternative Name to sub.mydomain.com)
One example:
You order a ssl certificate for the subdomain www for your domain mydomain.com.
mydomain.com is valid by its nature (SAN -> it's the TLD)
Whereas www.mydomain.com is the SUBJECT.
Best H.
To rewrite to rule from https as you are getting ERR_SSL_PROTOCOL_ERROR please check you are correctly provided ssl cerficate SSL Certificate Checker as my SSL provided is DigiCert.
And to make Https ensure in your remote desktop in IIS manager click your virtual machine ->binding -> Https and port as 443 and upload certificate.
In your virtual machine try to add outbound security rule provide service as HTTPS and port as same in 443
Reference: https://learn.microsoft.com/en-us/answers/questions/23397/not-able-to-secure-windows-azure-vm-in-https.html
I am trying to host a website on a subdomain e.g. sub.example.com through Google Bucket/Load Balancing with HTTPS traffic using Google-managed certificate.
I am using Cloudflare as DNS Server with Full end-to-end encryption enabled. The error I got in google console dasboard is FAILED_NOT_VISIBLE that Google interprets that like below:
Certificate provisioning failed for the domain. Either of the following might be the issue:
The domain's DNS record doesn't resolve to the IP address of the Google Cloud load balancer. To resolve this issue, update the DNS
records to point to the load balancer's IP address.
The SSL Certificate isn't attached to the load balancer's target proxy. To resolve this issue, update the load balancer configuration.
Google Cloud continues to try to provision the certificate while the managed status is PROVISIONING.
The AA record is added properly to Cloudflare DNS records and there is no problem in accessing sub.example.com when using HTTP for Load Balancing configuration.
Please consider that the example.com is SSL enabled using a self-signed Cloudflare certificate. Should these URLs (i.e. example.com and sub.example.com) use the same certificate? I assume not as Google LB is going to the server the requests on sub.example.com.
Any help to resolve this issue is greatly appreciated.
I have a domain in Godaddy called "x.app" and I want to transfer it to Azure App Service. I have created a DNS Zone called "x.app" and I changed all the Nameservers in Godaddy:
In Azure DNS Zone, I have created a CNAME, A, TXT Records:
A has name of # and value of App Service IP Address
CNAME has name of wildcard * and alias of App Service domain
TXT has name of # and value of App Service domain
I have added the Name of x.app as a custom domain and added a keyvault certificate:
When I just browse my domain: x.app I receive this error:
Your connection is not private Attackers might be trying to steal your
information from x.app (for example, passwords, messages, or credit
cards).
Anybody has an idea, what could cause this problem? Thank you!
There might be a typo. According to your DNS records configuration in Azure DNS, you should add the domain x.app instead of x.com as the custom domain in the app service.
If you have done it. These errors typically originate from two things: the first is a client-side issue (your browser, computer, OS), and the second is that there is an actual problem with the certificate on the website (expired, wrong domain, not trusted by the organization). You could get more tips to fix the error here.
For the error, you could also check an error code message which helps to try and pinpoint the exact issue and click the Advanced in Google Chrome. For example,
NET::ERR_CERT_COMMON_NAME_INVALID (this occurs when the certificate
does not match the domain)
In this case, you could upload an SSL certificate in which CN or DNS name matches the domain x.app. Additionally, when you bind a certificate with IP SSL, App Service creates a new, dedicated IP address for your app. You should remap A record for IP SSL with this dedicated IP address.
I have an Azure VM which is using a cloud service. The URL is e.g. Mydomain.cloudapp.net. I have used a CName alias so my domain is mapped on to it so e.g. www.mydomain.com goes to it. However I can still get to it via the cloudapp.net url. Can I disable the cloudapp.net url so only my domain is used. I want to route it through cloudflare. I have a team city server on there and I thought it would be an easy way to implement SSL.
You don't have option to remove the cloudapp.net domain. You can configure your custom domain with your own SSL and start using it (for end users). Unless you are using cloudapp.net domain explicitly, you don't have any risk of using the azure wildcard SSL certificate, and since you normally won't communicate the .cloudapp.net domain to end users, there won't be any risk as such.
If you want to protect the VM, you can use whitelisting so that authorized users only can connect
My company changed names recently, so along with that came a new domain. Both the old site and the new site are HTTPS and are on the same server using separate DNS entries.
I setup a 301 redirect which works great if people go to oldsite.com, but if they go to https://oldsite.com they get an SSL error.
Is there any way around this? Hopefully through DNS, server config, or htaccess file.
With TLS/SSL, only one certificate can be presented by the server per IP address. So if oldsite.com is using the same IP as newsite.com, the certificate for https://newsite.com will be the one sent to the client, which will (by definition) raise an SSL error for https://oldsite.com.
To have both oldsite.com and newsite.com both active, you'll have to have separate IPs for each. These can reside on the same server, with some (possibly complicated) routing configuration depending on your server's OS, to ensure requests to each IP are replied to from the same IP. However, even with DNS entries for both, you cannot share an IP address with multiple HTTPS domains.
Edit: You could also use virtual domains (exact config dependent on which web server you're running) to present the certificate for oldsite.com, then send the redirect after the TLS session is in place. I'd have to know which web server you're using (Apache, Nginx, Lighttpd, etc) to give a config example, though.