This duplicates an identical question asked previously on SO.
However, the accepted answer there appears no longer to work. The accepted answer there is:
Prior to this I had only a CNAME Record with a 'www' host pointed to
Heroku. Now I also have an ALIAS Record with the root host '#' pointed
to Heroku.
I tried to add an ALIAS record on Namecheap with host=='#', pointing to 'https://www.example.com'. But, Namecheap put up a message saying:
Error occured: INVALID_ADDR : 'https://www.example.com' should not be
an IP/ URL for ALIAS record.(host name: #)
I also tried an ALIAS record with host=='#', pointing to my web host (us-####-#.galaxy-ingress.meteor.com). Namecheap accepted that, but my web host said the Namecheap configuration was incorrect when I tried to generate an SSL certificate.
What's the correct way to do this on Namecheap?
Looking at the error message when setting up Alias, it seems that https:// in the value field is the issue. Have you tried alias for # as a host and www.example.com as value?
At the moment Meteor Galaxy requires a CNAME record, and as noted in the comment above, Namecheap doesn't want you to use a CNAME record for this. The solution, provided by Galaxy, was to use a third-party service. I won't post the url to the 3rd-party service here, as that might look like spam, but you can read about it in Galaxy's docs here:
https://galaxy-guide.meteor.com/dns.html#root-domain
Related
So I know this seems like a question many people have asked before but I wasn't able to find an answer yet so I'll ask anyway.
I have a few websites set up on one IP address, which means I need to use SNI - one of said subdomains is mail.domain.tld, which works perfectly fine and another is cloud.domain.tld, which unfortunately doesn't.
cloud.domain.tld redirects to www.domain.tld when it is up.
manually typing 'cloud.domain.tld/login' works even when other websites are up but I haven't been able to make the subdomain append /login automatically, which is what I want to do.
when I change the name of cloud.domain.tld to mail.domain.tld, leaving the entire config the same, it works.
when I added clou.domain.tld and clouds.domain.tld to my DNS settings and set the website to those it works too.
So I changed the location / block from
rewrite ^ /index.php$uri; - as default in owncloud configuration
to
return 301 /index.php$uri;
and now this problem has been resolved, however logging out now returns a CSRF error.
I am using AWS EC2 to host my WP site having cyberpanel (Litespeed Ent and LScache plugin). Using free Let's SSL certificate (certbot).
I tried to active AWS cloudfront CDN on my site but getting following error
SSL_ERROR_NO_CYPHER_OVERLAP in firefox
ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome
Below is screenshot of my various setting
Origin Setting
I am using Public DNS as my origin domain
Distribution Settings
Generated the SSL in AWS certificate and applied here. Added cdn.domain.tld as alternate domain name and added it as cname pointing to distribution in route53
Default Cache Behavior Setting
I am not sure what I am doing wrong here?
Note: I have TLS v1.3 enabled in my Litespeed
Ok, I found the Solution. I was doing some mistakes.
I have SSL certificate for mydomain and its www version only. No wildcard SSL. And I was adding cdn.mydomain.tld as Alternate domain names which have no valid SSL.
So I changed Alternate domain names to mydomain.tld and www.mydomain.tld and it started working.
Also, the SSL certificate that I generated in ACM was wrong, I added *.mydomain.tld as domain name, But I had to add mydomain.tld also, which I did and it solved the problem
Hope this help someone and he/she does not make silly mistake like me
Thanks #Michael-sqlbot and Jeff from jeffreyeverhart.com for pointing me in right direction.
I'm probably doing something silly, but I can't seem to be able to figure this out.
I've waited over 24 hours for Firebase to validate my domain, but the status just stays at "needs setup" and "domain not verified".
Per other other related answers on StackOverflow, I use # as the Name for TXT, instead of what Firebase said to put there (I also tried the "acme-challenge.www.mydomain.com" for a while).
Here are my GoDaddy records:
Anyone got ideas what might be wrong?
OK. I think I got to the bottom of it finally (I'm really new to this domain business). I originally added www.mydomain.com and not the naked mydomain.com to the "connect domain wizard". And I believe since I didn't have a CNAME www pointing to # it could never have worked.
Now I just added mydomain.com to the wizard, and Firebase instantly validated the domain.
The status is now "pending" since it takes up to 24 hours to validate the certificate, but the site already works.
Make sure to delete the original A records using the name #. Only keep the A records that are pointing to the Firebase Hosting IP address.
EDIT:
Change your TXT value to google-site-verification=YOURCODE.
It must include google-site-verification=.
Add custom domain from GoDaddy to firebase hosting
Simple step-by-step solutions with screenshots are found here
I have a domain that already setup for byte.nl hypernode server:
you can see details at:http://network-tools.com/default.asp?prog=express&host=lerenjas.nl
But I still couldn't access using lerenjas.nl and I can access by 'http://europell.hypernode.io/' what could be problem. any help would be great.
I already tried many things.
Thanks
There is nothing nginx has to do in this case. Your DNS is not set for lerenjas.nl. When you check it in the network tool url you have provided, it says "lookup failed". But for hypernode.io, lookup is successful.
So, you will have to check the byte.nl name servers.
I deployed a Meteor app to IBM Bluemix which created an address like myapp.mybluemix.net.
Inside Bluemix panel, since we have our own custom domain, I registered it with the address myapp.com and then I created three routes: myapp.mybluemix.net, myapp.com and www.myapp.com. I also created an enviroment variable ROOT_URL = 'www.myapp.com', since we want the www. version to be used instead of the naked domain.
Inside the DNS provider panel, I put a CNAME record as www.myapp.com CNAME myapp.mybluemix.net and a A record as myapp.com A XXX.XXX.XXX.XXX (pointing to the public IP of Bluemix host).
With all these, my app was opening well, but with duplicated URLs. Then I discovered the Canonical package and republished my app with it included hoping to solve the canonical need.
Unfortunately, all requests both to myapp.com and www.myapp.com redirects to myapp.mybluemix.net!
I can't see what configuration is causing this problem. What of the described steps I went wrong?
Following steps helped me configure canonical URL :
1) Install the canonical meteor package
2) Configure two routes to your application (naked and www subdomain)
3) Set CF environment variable : cf set-env leadershipboard ROOT_URL "http://www.vamsee.ml"
4) Configure DNS server CNAME to route traffic to Bluemix application :
5) Use slightly modified meteor buildpack : https://github.com/JProgrammer/cf-meteor-buildpack
Hope it helps.
I think that very probably the error is not with the custom domain configuration (which is working fine because according to your description all the routes are resolved correctly) but with the www redirect you are doing to make the www.myapp.com the default host.
If you provide more details about you have implemented it we could help you in finding out what could be wrong