I setup a Heroku app with vhost for subdomain handling. The app stopped responding to the custom domain originally assigned to it but the main Heroku app is live and working however, the subdomain link does not work for heroku. Please how can I fix this issue. app-name.herokuapp.com works. subdomain.app-name.herokuapp.com does not work. Also, customdomain.xyz does not work too.
All apps deployed on heroku actually are on subdomain of herokuapp.com so you can't create a subdomain for your app while using herokuapp.com for this you have to set custom domain, please follow the link to check how to set up custom domain.
Related
I have deployed my meteor app to some random name/url. I own the actual URL I want , myapp.com, at Godaddy. I did not deploy to that URL literally because I did not understand how the URL at Godaddy was going to be used at meteor. I believed I would have to do something over at Godaddy after I deployed. Now, I am ready to deploy with myapp.com on the meteor command line. What is going to happen? What steps will I have to take to make sure the url is properly directed over to the galaxy servers? I have read this article and the CNAME for my URL at Godaddy is already set to Eastern Us galaxy server. How does all this work?
Edit:
So, I was able to deploy to www.myapp.com and this all worked. But then, when I wanted to type maypp.com into the browser, it failed. I was able to get to my site by typing www.myapp.com into the browser, but this is not what I want. When I deleted this app and redeployed to myapp.com, I could not connect no matter what and I was refused when generating the SSL certificate.
If your CNAME DNS record for myapp.com is set to point at the galaxy servers, then it should work once you run meteor deploy myapp.com. The mechanism behind this is a type of reverse proxy: The server that responds to the incoming HTTP(s) request will inspect the request and see under what name it was reached, in your case myapp.com. Based on that information, the reverse proxy redirects the request to the internal resource that runs your app.
I created a Node.JS server in Bluemix and everything runs fine. But I can only access it through the given Bluemix domains.
I tried to configure the CNAME on my domain provider TransIP but it doesn't work. And I also couldn't find a lot of documentation about it.
Can you point me to the right place or tell me how to do it?
Researching past posts makes it seem like you have to use a service like DNSimple in order to have a naked domain (i.e. "example.com") for Heroku apps. I am wondering if that is still true, or if I can achieve this using only my app server.
I am using Namecheap BasicDNS and my app is a node/express app hosted on Heroku.
Thanks in advance for any tips. I am just trying to make sure before I purchase. Thank you.
You can't point your apex domain to an hostname (hence to Heroku), because you can't use a CNAME for the apex.
Consequently, the only way to point your root domain to a service like Heroku is by using a DNS provider that provides a CNAME-like feature for the root domain, that is what DNSimple calls ALIAS.
You can also find more information in the Heroku documentation.
I have an APP that was awarded the gorunning.pt domain. It happens that when I call the gorunning.pt domain without the www everything works, when I add the www http://www.gorunning.pt/ I receive the page 404 application not found.
I've already set the DNS CNAME for the application of IP , also tried the url gorunning.azurewebsites.net defined by Azure , created a type A registration.
This is expected. Your DNS configuration is correct. However the Azure Web App's front-end doesn't recognize the www sub-domain as it is not mapped in the portal.
You will also have to map the www.gorunning.pt to your web app gorunning.azurewebsites.net in the Azure Portal. :)
From the dig web interface, it seems the domain has mapped to the Azure web app. However it shows 404 not found. As I know your custom domain maps to an empty web site, so the easiest way is deleting your existed web site then custom domain to the new web site again. If you still encounter the same issue, please submit a ticket via the following screenshot.
Just can't seem to get this one ...
I have an AWS Beanstalk app running on IIS. The load balancer is configured for SSL and so is the security group.
So, I enter http://www.example.org and it works.
I enter https://www.example.org and it works too. Running SSL, great!
Now, I want to force SSL, so my understanding from this thread (Redirect to https through url rewrite in IIS within elastic beanstalk's load balancer) is that I configure the health check and add the described rule in the web.config file.
When I enter http://www.example.org I should redirect to HTTPS, but it doesn't work for me?
I seem to have two web.config files, one under the Default IIS site and one under my own site (beneath the Default). This entry doesn't seem to work in either place, but bonks completely under the default site.
Any ideas about what I am doing wrong?
Okay, my last paragraph tipped me off.
I was exporting my application (locally) as a sub application of the IIS Default app. This same configuration translates to AWS - so AWS adds a rewrite rule in the Default app to point to the sub application you deployed.
I had two web.config files. One in the Default IIS app and the other in my application.
So, I changed my local config so my app WAS the Default and then exported and deployed the same configuration to AWS.
As the Default app in IIS the redirect works!