Im currently trying to move my current redirect engine off a nginx proxy on a linux box to Azure. Currently ive been triyng to do it with this example:
dev.oldurl.com --> dev.newurl.com
This is the rule I currently have:
CDN Rules
When I have gone to the URL, im just getting a certificate error, I should also add that on the Domains section on the CDN I have this error "CNAME/alias record is not currently detected" I can confirm these are present in our on prem DNS server.
Thanks in advance.
As for the certificate error. You should have certificates corresponding to the URL's/domain names you are using in respective places. So the nginx server object receiving and redirecting dev.oldurl.com requests should have a certificate for dev.oldurl.com and the server receiving/handling requests for dev.newurl.com should have a certificate for dev.newurl.com.
For the CNAME record error, the Azure CDN will be looking at the public DNS records published on the internet. So you should check with your internet DNS provider for your domain to update the records.
Related
Recently we have created a new CNAME entry for the internal react website which is deployed in Azure. It has been pointed to traffic manager since we are deploying in two regions. After the CNAME entry is create, the URL throws 404 error. We have already configured the entry access restriction to all internal users. Appreciate if anyone can help to identify the issue.
For the error, you could add the new CNAME subdomain to your app service---custom domains---add custom domain as the picture displaying steps 1-5. After you validate the subdomain and add the subdomain into the custom domains, you should access the subdomain URL via the traffic manager. Read this blog for more details.
In addition, only Web Apps at the Standard SKU or above are eligible for use with Traffic Manager. Attempts to add a Web App of a lower SKU fail. Read Azure web apps as the endpoints.
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.
Our website mywebsite.com is currently managed by Wix DNS. We wanted to create a subdomain api.mywebsite.com to forward requests to aws api gateway. Here are the steps I tried
Created an ACM certificate for *.mywebsite.com
In AWS console API gateway I created a custom domain and associated it with ACM certificated I created about. I got a cloudfront target domain name somecloudfrontid.cloudfront.net
I created a CNAME record in wix that points api.mywebsite.com to somecloudfrontid.cloudfront.net.
But, when I tried to hit api.mywebsite.com I get this error:
ERROR
The request could not be satisfied.
Bad request. Generated by cloudfront (CloudFront)
Am I missing any step? How can I get this working? Do I need to transfer my domain to AWS router 53 to make it work with AWS?
I suggest transferring the domain to Route53. There you can create an alias for your subdomain under Hosted Zones, and point it directly to your cloudfront target domain, as well as several other AWS resources quite easily.
I am hosting a web app on a Digital Ocean VPN. I set up an A record via GoDaddy to point my domain to the VPN server. I'm wondering if there is a way to still access public files from within the web app that I have on GoDaddy shared hosting at that same address.
I basically want to access a file at http://example.com/uploads/somedoc.pdf
Which would be at the following path on the GoDaddy server:
home/site/public_html/uploads/...
But example.com now points to the VPN. I tried using the GoDaddy website IP address instead in the URL but that doesn't work either. I get a 404 file not found error even though the files are actually in the uploads folder. I figure it's looking for them on the VPN instead.
In case anyone else runs into this problem I solved my issue by simply adding an A Record for a subdomain in my DNS zone file and I was able to point my VPN server IP to that subdomain. So with my web app being served at app.example.com I was successfully able to access the files on the GoDaddy shared server from my web app (ie example.com/uploads/somefile.docx).
To ensure that the client would still visit the web app at the new subdomain I setup a permanent redirect to send all traffic from example.com to app.example.com instead of them having to remember to type the subdomain each time they want to access the web app.
Azure uses SSL across their webapps and has a cert for *.azurewebsites.net. We have been trying to setup subdomains that point to our webapp but we keep receiving security errors or redirect errors. So for example, we set an A record that points from subdomain.ourcompany.com to the assigned IP. Then we set a CNAME record for awverify.subdomain to awverify.webappname.azurewebsites.net.
When you try and access the site, we get a "too many redirects" error. I don't know if it's relevant but both ourcompany.com and www.ourcompany.com are not hosted on Azure and their A records point somewhere else.
Any idea why we're getting this error? Note that if we drop the A record and instead create a CNAME record from subdomain.ourcompany.com to webappname.azurewebsites.net, then we receive a SSL certificate error saying that the site isn't trustworthy. I tried to get around this using cloudflare but to no avail.
Any thoughts on why this is happening?
Please see this article to properly configure custom domains:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
The end result is that you will have the following in your Azure Web App:
And the following on the DNS registrar side:
Note that 23.99.65.65 is the VIP of the stamp in which my Azure Web App is hosted, and is displayed at the bottom of the Custom domains and SSL page. It should also be displayed when you resolve (your website name).azurewebsites.net via digwebinterface.com.
Once that is complete, you will have the domain correctly configured and the next step is to purchase a certificate for your site. Once you have purchase the certificate, you can configure it using the following guide:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/
Note: the reason you are getting an SSL error now is probably because you're using the default SSL cert, which is issued to *.azurewebsites.net. Since this doesn't match your custom domain name, it's going to be an error, although https://(your-site-name).azurewebsites.net should be okay.