I have multiple GoDaddy domains that point to AWS DNS Servers, which in turn point to a load balancer and thence to (at the moment) an instance. All but one of these work fine and one steadfastly refuses to work, even after deleting and recreating (multiple times).
Using the SDK I have tried to find a significant difference between Zones / Resource Record Sets and have not come up with anything that would explain it. DNSSTuff has not yielded any clues (nor have a couple of other online tools).
An example of a working domain is care.work, and the failing one is plaitapp.org.
Thanks in advance.
It just appears to have been amazingly slow propogation for one domain, while all the others were almost instant.
Related
0
I realise that LightSail is an entry level provision that enables people like me who sadly don't know near enough to tap into what is pretty amazing tech. However, it's very frustrating that things that should work just as a result of a few clicks definitely DO NOT. Furthermore, most of the documentation is outdated or lack sufficient detail. Does AWS really want to charge $18 per month for something this buggy / filling up countless forums with people expressing their difficulties and frustrations??
For over a day now (8+ hours) I have tried in vain to set up a Load balancer connected to two Wordpress / Bitnami Instances. First the DNS related to the LB 7668[...].eu-west-2.elb.amazonaws.com was clearly broken in that clicking that link returned a Safari couldn't open the page error:
Safari can’t open the page “7668[...].eu-west-2.elb.amazonaws.com”
because Safari can’t find the server
“7668[...].eu-west-2.elb.amazonaws.com”.
Having found out the relevant IP I was able to load the page, but still...
But it is when it comes to setting things up within the DNS zone where the trouble really begins. When assigning my domain to a Static IP address associated with one of my instances everything works fine—but obviously the load balancer is not "active"; i.e. traffic to my domain goes straight to the instance. However when assigning the domain to the LoadBalancer (with certificates, validated, etc.) the page instantly "breaks" with the error message:
"Too many redirects occurred trying to open
“https://7668[...].eu-west-2.elb.amazonaws.com”. This might occur if
you open a page that is redirected to open another page, which then is
redirected to open the original page."
At this point there's zero help from within Lightsail and none of the docs (mostly outdated or overly vague) cover this. So I hit various forums, searching and the problem seems to be all over the place in various forms with potential "solutions", none of which however work... I can't help thinking this problem would be very simple for someone knowledgeable to fix, but there's certainly no way within Lightsail to solve this... MEGA FRUSTRATING.
As such, after 8+ hours, I now deleted the Load balancer (not wanting to be charged for something that doesn't work) and returned to serving my website content from a single instance.
What am I missing? Why is such a no doubt simple problem for those in the know, seemingly insurmountable for the kind of audience Lightsail is aimed at? What is the solution?
I am unable to restart my VM for 2 hours now, my services are down because of that error :
The zone 'projects/******/zones/northamerica-northeast1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
I can't rely on gcloud having to be down for hours because of ressources. what should I do, I can't afford changing zone, it needs to be in Canada. I can't also afford changing the IP it's behind a DNS. I just need to restart my VM. my business is down...
What's the issue/solution ?
thank you
I'm glad to see that you solved your issue by trying a different machine type. I was about to suggest trying a different machine type and then checking whether it allowed you to restart your VM.
I wanted also to mention in case this can help other users that in case that trying a non-shared core machine type, or a VM from a different family doesn't help you can try to recreate your VM in a different zone of the same region (I've been using northamerica-northeast1-a without any issue so far).
However, in case you want to prevent this from happening at all after a given restart, I recommend you to create a reservation to make sure that these resources are available to you and don't impact your workload/application.
Finally I found this links that maybe you can be interested on: Patterns for scalable apps. It discusses how it's best to deploy your app/workload in different zones to make sure it is more resilient by being balanced and you wouldn't need to change your DNS records every time you need to switch the VM serving the backend.
I am trying to connect my Amplify app to a GoDaddy website and the AWS instructions are not clear on how to do this.
Following these instructions I created a CNAME record to point to my Amplify app.
(Image from the documentation)
I have a "master.xxxxxxxx.amplifyapp.com" and a "feature.xxxxxxxx.amplifyapp.com", am I supposed to use one of these or just the "xxxxxxxx.amplifyamp.com"?
It seems from the docs that these records take up to 2 days to update and I do not want to waste 4 days attempting this by trial and error.
Edit
Following #Rodrigo M's answer I used the 'master.xxxxxxxx.amplifyapp.com' route for the CNAME record but when I go to the page all I see is the error:
This page isn’t working xxxxx.domain.com redirected you too many times.
And then when I look in the Network tab I see that the page did a bunch of 302 redirects where the name and the initiator were "Index.html".
Does anyone have any ideas of what is going wrong?
Each of the AWS Amplify domains that you reference refer to a branch of your app eg master or feature. Use the full domain name eg master.xxxxxxxx.amplifyapp.com as the target of your CNAME record for the branch you want to expose on your custom domain.
All of the standard DNS propagation warnings say allow 24 to 48 hours but in practice it's usually much much quicker so don't worry about waiting for two days too much.
I can see your DNS TTL is set for 1 hour. This value is how long the DNS system will cache your DNS records. Which means you can make a change and it would take up to an hour for those records to be updated throughout the internet. You could drop that to 5 minutes or less if you want to do trial and error testing or make quick switches to a different branch.
Godaddy doesn't support ANAME/ALIAS so you can't connect it properly. However you can forward the domain without www
Scroll down to the Forwarding section of the go daddy DNS page and set up a Temporary (302) http forward from yourdomain.com to www.yourdomain.com
It took about 30min for this to take affect for me.
I am dealing with some weird inconsistency issues with the dns to my subdomain, and was hoping someone would be able to shed some light!
I have a domain purchased through Google Domains and have a need to use the main domain, and a single subdomain for my api service. With Route 53, i have 2 hosted zones, one for the main, and one for the subdomain, each providing the 4 NS configs, and two aliases back to my Elastic Beanstalk nodes for the www & non www calls.
For my main domain, using WhatsMyDomain, the propagation is pretty much worldwide at all times, but when it comes to my subdomain, it is intermittent and changes throughout the day, where it was working in one location earlier on, it will then stop working.
In Google Domains, i have all 8 NS configurations set in my DNS settings.
I feel like im missing just one piece of something, just can't figure it out
Thanks to Michael - sqlbot for his return question, never even thought about just trying it by adding an alias to the subdomain in the original Hosted Zone! In the docs on AWS, they do provide info on having 2 different zones, which i think thats what i stumbled across when i first started, but i believe there is a bit more setup involved in that route!
Just made the switch, gonna see if this solves the issue!
Right now the website is running locally and I'm still working on it.
While doing this I also have to make it visible to a specific group of users as I need their feedback in order to add/change features, etc.
I've tried to find a free web hosting without any luck (see dependencies).
I was thinking to create a VPN but then I will have to use my PC as a host for a virtual machine which is by far not what I'm looking for.
Therefore, my questions are:
1. Which is the best way to achieve this (website visibility for TESTING) fast and easy?
2. If a dedicated web host is the best solution, please point me to an easy-to-use and cheap one. What I've tried so far: elastichosts, alwasydata, stackable, 1FreeHosting and probably others I don't remember right now. For a reason or another I couldn't use none of the above.
Another aspect to be considered: I want this only for simple testing and I don't need a lot of server resources. Also the traffic will be very low as there are only 5 testers. That's why I wouldn't pay too much for it. I will probably need this temporary web hosting for 2-3 months.
Dependencies:
- as the website uses mezzanine, for the moment I only need mezzanine's dependencies.
Thanks in advance!
You can always just setup port forwarding on your router. This would allow your testers direct access to your app. Though this might give your PC more exposure than you want.
Heroku has a free tier.
In your non free options, an instance at linode costs $20/month, but requires some setup. Rackspace has similar options in their cloud servers line. Both are no contract servers.
My blogpost covers gracefully deploying a Mezzanine site. The monthly hosting cost is nothing compared to the cost of a slow, painful deployment process.
An EC2 micro-instance right now costs as little as ~US$3.50/month. I create and destroy staging servers on EC2 servers for testing and sharing with others.