Last night I migrated a site to Heroku with Network Solutions. The process went well for WEBSITE.com and www.WEBSITE.com, but https://WEBSITE.com does not work. I have the CName "*.WEBSITE.com" set to "WEBSITE.com.herokudns.com." and www.WEBSITE.com set to www.WEBSITE.com.herokudns.com.
Network Solutions said it will take time for the root URL to work through the system.
Related
I've the following situation. I made a SPA with React/Redux and deployed it with gh-pages to github. In the package.json the homepage is https://www.url.com. The DNS on the domain provider (Uniregistry) points to my cloudflare instance. On cloudflare I have 4x A-records pointing to the IP for github. And one CNAME with wwwwwhich resolves to iepur1lla.github.io.
When I try to access the URL via Chrome I get ERR_NAME_NOT_RESOLVED, though when I try to access the URL via TOR browser it works perfectly fine, redirect and SSL certificate, everything.
At first I researched on Stackoverflow, what could cause this issue, and I checked the DNS propagation for my country. And it points to Cloudflare, and my github URL points to the IPs which are as A records in cloudflare.
I really could use an advice. Thanks in advance.
The issue is resolved. After investigating with the dig and nslookup commands, I found out that in some cases the default DNS from Uniregistry which has been updated to Cloudflare DNS, was still resolving. I went to uniregistry and purged my DNS servers and put the same cloudflare DNS in and after waiting the TTL time it resolved fine. Yay!
I'm running two sites on Linode. Testing server.
I have one Wordpress site running on sample.com
I have another Ghost site that I want to run on www.sample.com
Note: the first one doesn't have www prefix
However when I try to access www.sample.com my browser instantly shows my Wordpress site at sample.com ( the one without www )
I can not narrow down where this setting is being enforced at.
I figure it either has to be in the Linode DNS settings -OR- in the nginx server settings. I can't find anything indicating that there should be a redirect of any kind.
Ammendment: On the nginx side, there is are two configuration files. The default server config file is pointing to the Wordpress installation which is loading for both www and non-www cases.
Ammendment: The remaining 1 configuration file is pointing to the Ghost installation.
Ammendment: When using the same two configuration files, but only changing the hostname to be "mail." instead of "www." the ghost installation loads just fine. The "mail." host was already registered in the dns settings, so I just borrowed it as a test.
What am I not consdering?
I'm not quite sure what happened. But, 24 hours later, the problem went away. Somewhere in the pipeline, old host/ip/port sets were getting cached and I couldn't resolve where. But, now it's working fine.
Thanks Richard Smith for taking time to talk me through it.
I've removed my app from Heroku, but I forgot to remove my custom domain from heroku. Now i'm stuck with two versions of one site. .nl is working correctly, www..nl is giving me the error message "Heroku | No such app"
What to do? I've already edited my DNS records, but still doesn't fix this problem,
Many thanks,
If you are getting a Heroku message, then your DNS is still pointing to Heroku. There is no Heroku setting that could cause it to take control unless your DNS is sending traffic there.
If http://something.nl is working, but http://www.something.nl is not, then you probably didn't change all of your DNS settings properly.
The only other option I can think of is that your webserver on your VPS is routing traffic from www to the Heroku app, that is very unlikely though.
Last option... wait longer for DNS propagation if everything is correct.
I deployed my app to heroku and I added my godaddy domain to heroku with:
heroku domains:add www.domain.com
heroku domains:add domain.com
But when I type domain.com sometimes it doesnt work and it redirects me to godaddy. Only www.domain.com works fine. Is there anything I am missing in configuration?
This is my DNS records setting
Host
# 68.178.232.100
# 75.101.145.87
# 75.101.163.44
# 174.129.212.2
C-NAME(Alias)
www proxy.heroku.com
From what you've described your Heroku setup is fine. You need to make sure your GoDaddy DNS records are correctly pointing to Heroku, and specifically that your # record is set correctly so the root domain is handled by Heroku.
Update:
The Heroku IPs are:
75.101.163.44
75.101.145.87
174.129.212.2
68.178.232.100 is GoDaddy. Delete that record and you should be ok.
Check your DNS settings. If your DNS is set up properly you may just need to wait for it to propagate out to other nameservers, which can take up to a week. In all likelihood it will only take a day or two.
I have been testing an app and have all of the functionality worked out. Being my first go with ror I have a few questions about my next step; grateful for direction on this.
Should I do all of the design and UI before putting my app online, or after?
In trying to research this I have found three things that keep coming up as great tools to help deploy - Heroku, Capistrano, and Phusion Passenger. I know Heroku let's you deploy quickly and easily, but is this the option if I want my app at it's own URL? I currently host other websites (Wordpress) at Hostmonster, but they aren't supporting Rails 3 yet.
What is the difference between the functionality of Passenger and Capistrano? I have been searching, but not knowing some of the terminology, I'm not sure how to decipher all of it.
Go with Heroku — there's no need to clutter your brain with all of the hosting stuff since you don't already know it. Heroku is great, and you can easily have your own domain name. Point your nameservers to a.ns.zerigo.net and b.ns.zerigo.net and run…
heroku addons:add zerigo_dns
heroku domains:add example.com
heroku domains:add www.example.com
Set your domain's DNS servers to a.ns.zerigo.net and b.ns.zerigo.net.
And done deal, you're ready to deploy on Heroku. Your first dyno (app instance) is free, Zerigo's basic dns is free. You're rolling with 2TB/bandwidth (soft limit) and a whole lotta request-serving for a grand total of $0 and 15 minutes.
And for deployment, from start to finish here (provided you develop within the limitations of Heroku's platform [ie. read-only filesystem, PostgreSQL, bundler-dependent]):
heroku create yourapp
git push heroku master
heroku open # opens yourapp.herokuapp.com in your default browser
If you need to configure your DNS records:
heroku addons:open zerigo_dns
It's like magic, but it's all just solid engineering.
And to be clear, I don't work for Heroku.
Whether to finish your UI designing before going live is a decision you have to make. I don't think this will have any rails - deployment related consequences. So if you want to deploy and release fast in a rapid manner, go ahead.
You should be able to use your own domain name even if you are hosting with heroku. Take a look at this
Capistrano lets you deploy your apps with ease. So you don't have to login to your remote server and pull code from git, restart services...etc etc. You can just run cap deploy from your workstation and everything will be deployed on your server and all services will be restarted..etc.
While passenger is something like mod_php. It hosts your application. It works with apache or nginx. You will most probably end up using both capistrano and passenger. I don't think they are comparable because they do two different things.