I'm currently having trouble with hosting with dokku on digitalocean. Everything uploads just fine, all "pre-flight checks" pass and dokku even says that my application was deployed successfully. However when I go to the domain i used for the app (which is this). I get an error saying webpage isn't available, or since i'm using CloudFlare for DNS it says "Website is offline". I have all the dns servers pointing to CloudFlare and standard dns and the wildcard dns are setup as so...
Happy to add more information if needed.
The domain appears to work for me. Did you get this sorted out?
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 have started creating my own nodejs app (for the first time) that I hope to deploy at some point, perhaps to Heroku or another platform.
I need for my app to encrypt traffic namely for user passwords and sessions (note there is no other obviously sensitive data).
I started looking into serving my app using HTTPS (SSL) however I am now wondering if I need this. If my app is to be hosted and deployed using Heroku/other platform won't all requests be trafficked through their servers presumably using HTTPS by default? I am guessing that the request will then be routed using HTTP to my application, although I am struggling to understand how this works. Ultimately I would like to know if I can ignore worrying about paying for SSL certification and such like when it will not matter in this hosting environment?
Help much appreciated. Matt.
If you are using heroku then you must be using paid dyno( hobby or professional) and heroku provides free SSL to all paid dynos. Furthermore if you think that at some point you can switch hosting then there is always freessl available via Let's encrypt.
Heroku serves all requests with and without SSL in default herokuapp url.
Use cloudflare free plan. Open a free account in cloudflare, Copy the DNS. Then set the DNS in your domain service provider (godaddy or sth), then change the Cname config for the website inside cloudflare. Now you have a free certificate.
I have a hosted website using an Azure webapp. Sometime yesterday, portions of my website began to fail with network requests showing ERR_INSECURE_RESPONSE. Random image files, css, sometimes even the index (which Chrome really doesn't like). However, if I refresh a few times in Chrome, the assets load just fine. I'm access the site through the subdomain created when the webapp was set up so the SSL certificate is for *.azurewebsites.net and appears to be valid.
Is there a way to debug this further? Logs from my server don't seem to be showing any issues and there isn't a clear repro.
The fix for this was pretty simple and I wanted to post in case anyone stumbles across this because (I think) the settings by default were in the config that served the error.
I had a custom domain and had set up SSL for that domain on my Azure web app. The error I was seeing is that from time to time Azure would return the default SSL certificate for azurewebsites.net instead of the SSL cert I had purchased for the domain. The fix was to switch from IP SSL to SNI SSL. This can be done from the "SSL Settings" in your Azure Web App. Click the host name and modify the SSL Type.
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?
Our application is making HTTP requests with HttpClient to some websites. In local it always work, but for an unknown reason it fails in production.
Our application is an Azure Website.
We are getting the following error: Unable to connect to the remote server.
We have an IP Based SSL certificate, our IP address is not blacklisted anywhere. It was not happening before 3-4 days.
Depending on the URL we call, it sometimes work, sometimes not, we really don't get why.
UPDATE
It seems to only happen when we make requests to website hosted by GoDaddy, called their support and our IP address is not blocked.
If you isolated that this is not a GoDaddy issue, I would contact support on Azure. It might be a tech issue or networking issue. They will help you isolate the source and fix it.