I've tried to attach the build log but stack over flow was keep throwing errors, so i will go ahead and skip the build log. As far as the build log goes, there wasn't an error.
As you can see there is no error generated while building the system on heroku's side. I did everything that my domain name company told me to.
However, when I go to my custom url, www.example.com, I see an error:
Heroku | No such app
There is no app configured at that hostname.
Perhaps the app owner has renamed it, or you mistyped the URL.
The url that heroku gives me works but when I connect it to my namecheap domain, it keeps giving me that Heroku | No such app-error.
Related
I developed a website using react and node.js, and my team deploy it on the server, the problem is when we try to use the website using the new domain or IP address it gives us this error:
Although it works fine in the localhost:3000 in the server, can you please give me the hints to solve this
I also faced the same issue because of not updating
backend URL so make sure to check the backend URL in the frontend. If you host any cloud-like Heroku then include on .env
In your case, there might be some other reason as well.
I'm new to web dev and this would be my first proper deployment so apologies if this is a basic question. After following the steps on Heroku and Domain.com, my app is not showing at the desired url: www.rocketcreative.agency
Heroku
I've set up a basic web app (a draft version atm) on Heroku, and the code is working fine on https://hidden-sierra-22116.herokuapp.com . I've followed the Heroku instructions to generate a DNS target (cubic-orange-7jtaz36102kt9f8dir53koko.herokudns.com) for a domain I own (www.rocketcreative.agency) Heroku Dashboard Screenshot
Domain.com
I added the DNS target to Domain.com as a CNAME (with 'www' as the host name). I've waited 24 hours for the changes to propagate, and DNS checking sites indicate that the DNS has propagated. I've spoken to Domain.com support and they said everything appears to be set up correctly. Domain.com DNS Screenshot
Terminal:
In the terminal, when I input host www.rocketcreative.agency, it returns www.rocketcreative.agency is an alias for encircled-horseradish-4mpqnlzar9say364tz3hgy80.herokudns.com.
Browser Results for www.rocketcreative.agency
Safari: 'Safari Can't Find The Server'
Chrome: 'www.rocketcreative.agency’s server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN'
I imagine this is a really basic question but if anybody could help that would be great. If there's any other info I need to provide please let me know. :)
Hold the phone! I've solved this one, but I'll leave the question up incase anybody encounters the same. Ran the Heroku DNS Diagnostic tool and there were some issues with https:// - fixed by running: heroku domains -a hidden-sierra-22116 heroku ps:resize web=hobby heroku certs:auto:enable heroku certs:auto It said 'cert issued' and now the url works
As the title says, when the application is supposed to be built and good, (at least during deployment, the log files etc always state that the build was successfull) when everything should be set to go, I open the site and encounter 2 console errors:
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
Failed to load resource: the server responded with a status of 503 (Service Unavailable) favicon.ico:1
Tried looking up those errors and finding solutions but none of them seemed to work, Even though, the application works perfectly on local heroku (where you can test your app, in the heroku enviroment).
Not sure what I could do to fix my problem, as many forums suggest that you can't really do anything about it if it works fine on local heroku, it's must likely a server fault.
Thanks
edit: kinda fixed it myself after long days of struggling. Changed up file locations, moved server.js etc out from backend, into the main folder, and created a client folder, which now contains all the frontend stuff. Exact opposite what I used to have, since I used to have frontend out in the 'wild' and only had a backend folder for... well, backend files/folders/scripts.
Problem solved... kind of, still not sure why the first version i tried to use didn't work, but at the end of the day, I'm fine with it
Here's the only error message I've been able to find, from an error file in /LogFiles/W3SVC1180911273:
ModuleName iisnode
Notification EXECUTE_REQUEST_HANDLER
HttpStatus 500
HttpReason Internal Server Error
HttpSubStatus 1001
ErrorCode The system cannot find the file specified.
(0x2)
I have a project I've been developing locally that I'm trying to now host to Azure. It's a Node project using socket.io, Webpack, and Typescript for the server-side and client-side JS. I haven't been able to get it working. Navigating to the site gives me a "This page isn’t working" 500 error.
I've created a custom deploy.cmd file that runs webpack and compiles my typescript. I've created an iisnode.yml file to make sure loggingEnabled: true is set. I've turned on Web Sockets in azure, and ensured that <webSocket enabled="false" /> is set in my site's generated web.config, though I don't think sockets are the issue.
I also made sure that the express app is listening on process.env.PORT so that it uses the named pipe from Azure.
I use a site log tail to view the node logs and when I first navigate to the site after starting it, I see my node server start up successfully, without errors, and begin running. But the request always fails, multiple times in a row.
I can't find anywhere that it says what the actual file is that it can't find.
I previously had some ENOENT: no such file or directory errors thrown by node, and those showed up in my /site/LogFiles/Application/logging-errors.txt file, as well as my streaming logs. So the issue isn't with Node, it's with IISNode. And I can't figure out where to get more details about what's failing.
I'd greatly appreciate anyone being able to help me figure this out.
Recently I started getting The connection was reset. error message (error code is ERR_CONNECTION_RESET) when I open one of my websites. This has nothing to do with application(node.js) level afaik as no changes or deploys were made in the application. To add to this, there were no error logs so I am assuming the request did not even receive the node app. The website is hosted on godaddy and its backend is a elastic beanstalk application. How do I fix this? On the web browser, in the second attempt it automatically loads correctly. But in a iframe which embeds my website, this has become a nasty issue as the browser does not even retry. I did the DNS analysis using dig command and all that but could not find anything relevant. Interesting part is this only happens after some interval (it does not happen continuously). On reload it works without fail.