I am receiving some issues on Drupal.
I have integrated Amazon cloudfront with Drupal.
The Cloudfront origin for my domain is drupal.example.com and Cnames are www.example.com and example.com.
The problem is that some images are
are forming the URL's like this
data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
Please suggest.
Related
I am trying to use the directions given in
https://www.npmjs.com/package/express-subdomain
to set up subdomain.
I a hosting my server in amazon EC2 and the DNS provider is google-DNS.
but I am getting error while accessing the page.
404. That’s an error.
The requested URL / was not found on this server. That’s all we know.
So I need to do any configuration in EC2 or in my DNS?
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 have a website mydomain.com with the DNS configured through Cloudflare. I am in the process of setting up an API accessible through api.mydomain.com
The servers I use are hosted on Digital Ocean, but I would like to use some of the features of the Amazon API Gateway Interface (I will later be migrating all servers over to Amazon). The API server is the same as the website (again this will later be separated, but for now the effective A record is the same Digital Ocean node). The API Gateway Interface is configured and I can access it just fine through the provided endpoint someamazonendpointurl.com/stage
On Amazon I have created a Cloudflare distribution with origin api.mydomain.com. It has some basic HTTP to HTTPS behaviours along with query string parameters. I then set a CNAME record on Cloudflare to point to the endpoint URL. When I try and access api.mydomain.com though I get the Chrome error:
ERR_TOO_MANY_REDIRECTS
Does anyone have any idea what I might have misconfigured. I realise this is a bit of an odd setup, but it is a stop-gap while we migrate our servers over to amazon.
UPDATE
I noticed I had a CNAME record in cloudfront to api.mydomain.com. I've now removed this but get:
ERROR
The request could not be satisfied.
Bad request.
Generated by cloudfront (CloudFront)
Request ID: <id>
Most likely you have your SSL mode on Cloudflare set to "Flexible", which doesn't use https to connect to the origin server. API gateway tries to redirect non-secure requests, so you have a redirect loop.
Set your SSL mode to "Full" and you should be good to go! You can do this on the "Crypto" tab of the Cloudflare dashboard.
I have a static website hosted on a Google Cloud Storage Bucket. I also have moved the DNS to Google Cloud DNS. So everything is in control on the Google Cloud Platform.
I only have some problems left:
How to solve www / non-www requests? I pointed the non-www now to a server outside the google cloud platform which redirects to www. I don't see another possibility to refer both directly to the same bucket.
How to solve http / https? SSL is not possible yet on buckets. The https version can be reached ofcourse, but I get a warning and the googlebot has problems with it too. For some reason they indexed some https versions of some pages while I have set canonical links to the https version. And I don't see any possibilities to set up redirects correctly.
Unfortunately, that is not possible at this time. When using CNAME redirects to GCS, a bucket must exactly match the specified domain. You may not map several domain names to one bucket or vice versa.
Furthermore, "domain.com" with no subdomain is, unfortunately, right out, as DNS CNAMEs cannot be set on root domains.
We have our company website hosted at Windows Azure Websites and set up an A-Record for our domain.
The problem is that one can also reach our site using the mangomint subdomain of http://azurewebsites.net (I don't want to post the full url here because Google shouldn't see this). This is bad in terms of SEO and duplicate content.
How can I disable the subdomain in favor of our main domain?
Well I don't think you can change the official azurewebsites.net DNS records, so you have only two solutions :
Find a way to disable this subdomain in the Azure Websites configuration EDIT: Not possible, from what astaykov said in the comments. thanks to him.
Make your website automatically redirect (HTTP 301, permanent redirect) the user when he lands on the subdomain.