I'll keep it short. I published my MERN stack project that I created before on heroku. There was no problem, but when I run localhost, I can get a response with a proxy between the backend and the front-end.But it doesn't work on heroku, what should I do? can you help me?
Related
I've created a flask app and hosted it on Heroku. I then followed the heroku documentation on connecting the custom domain, as per link: https://devcenter.heroku.com/articles/custom-domains.
I added the custom domain of my app to heroku (*.cfoskillset.com) and created a CNAME record on Godaddy with the DNS target that Heroku generated. I waited for about 20 minutes. However, the doain is not working. I am getting an error message: "NET::ERR_CERT_COMMON_NAME_INVALID" and chrome is saying the connection is not secure.
I searched Stack Overflow for other questions on this, however, none of the replies or solutions worked for me.
What am I doing wrong?
heroku custom domain
goddady dns settings
I am developing a website, where posts are published through Strapi. My website is a React app. For Hosting, I use (Amazon's) AWS.
My question is simple. I want to deploy my localhost application, and make visible to the WWW. I was searching for tutorials but could not find any that helps me in this.
Thank you!
ok deploy process is simple:
You get a server like digital ocean.
you push your projecto into a github repo.
Configure mongo, node, ngnix and clone your project into www folder
enter in your folder app and make npm install --production
latter insall PM2 and make it run
this is a little explaination the real explanaition you can see here:
how to deploy strapi app on ubuntu server
The www you can modified adding Cname at your server and vinculing your dns with you domain in you name domain proveedor
im having a problem with Heroku and Zerigo DNS.
Im using Zerigo to make DNS work on heroku, the problem began when i delete the app to rebuild all my web site.
Once i delete and rebuild i couldn't install Zerigo DNS to the new app. The problem is even worse because my domain still works!
As you guys can see, when you access http://www.estatisticaslotofacil.com.br, you are redirect to a web site. This site is hosted on heroku using Zerigo DNS.
But i dont install Zerigo to this new app, because it keeps giving me this message:
! could not create zone; already registered on Zerigo to a different account?
Can someone help solve this?
I have an Octopress blog (amyhua.me, github.com/amyhua/amyhua-me) that I've generated with several posts and have deployed to Heroku. I've configured my DNS correctly (product check on DNS configuration passes), and the blog works on my local host. I did a git push heroku master which was successful, and the heroku logs show no apparent errors. But when I try to visit my heroku app at amyhua-me.herokuapp.com, it shows a message:
"Heroku | No such app
There is no app configured at that hostname.
Perhaps the app owner has renamed it, or you mistyped the URL."
I even started over with a new heroku app, deleting my former amyhua-me heroku app, and creating a new one I named amyhua-me (since my DNS servers point to amyhua-me.herokuapp.com), and it still throws a "No such app" message when I visit the herokuapp url.
Any ideas?
So for anyone who cares, I solved my own problem.
It was the difference between pointing to www.mydomain.herokuapp.com versus mydomain.herokuapp.com from my DNS server.
Pointing to mydomain.herokuapp.com goes to my heroku app, mydomain.
Pointing to www.mydomain.herokuapp.com goes to a "Heroku | No such app" page.
Lesson learned: don't use the "www" in your DNS configuration!
Or.... just avoid the hassle and use the Zerigo DNS heroku plug-in.
I am running a PHP application on Heroku and am wondering if I can have wildcard subdomains on top of the herokuapp.com hosted subdomain. For example I have my application running on mysubdomain.herokuapp.com through Heroku, however can I make it so *.mysubdomain.herokuapp.com points still to my server?
I am simply uploading my PHP application to the heroku instance by using 'git push heroku master'
unfortunately what you are trying to achieve is not feasible