I have an node js express app for service module and angular app for web, which is deployed in the windows 10 iis server at the domains
"http://localhost:8011" and "http://localhost:8012"
If i test the site in my browser like
"http://localhost:8011" and "http://localhost:8012"
or
"http://{port number}:8011" and "http://{port number}:8012" it's working
but if same thing i open in others computer the angular application is working without any issue.
but the node js is not working
it's giving the error like
This site can’t be reached
{port number} took too long to respond.
Can any one suggest me what is the error and how to resolve this issue.
Thanks in advance.
It is not very clear from the question but from what I understand you are trying to serve a node express app through IIS?
If this is the case, you should look at the iisnode package which is really helpful. You will also need to install the IIS rewrite-rule module if this is not already installed.
If this is indeed what you are looking for let my know, and I will edit me answer to include more details.
Related
I installed an app with the application manager in cpanel and I don´t know where can I find the errors log, can you help me?
The solution was simple but I see a lot of people is having the same issue, the problem was I was not pointing to the proper directory when I set up the app in the application manager in cpanel, you should select the directory where exactly your app.js is located, for example my app.js was located inside home/server/src and I was pointing to home/server because the package.js was there, also you should select development in the application manager when you set up the app otherwise you don´t see the node.js errors just a short passenger description, after that you will be able to see the errors in your web browser just writing your app routes like you were checking any other site.
I have node js api and it works when starting using nodemon from node terminal. Now I want to deploy it to IIS. How can I do it? Please reply, it is important.
To run Node.js apps on IIS on Windows, iisnode module is needed. Please follow this article to get going. Primary requirement to run your Node.js app on Windows is the iisnode module. If you follow the instructions carefully, you can get it working pretty quickly.
PS: You would also need to assign user IIS_IUSRS READ permissions to the folder (and its parent folder) which contains your Node.js API sources. web.config which mentions the iisnode module is very important for everything to work smoothly.
I have been looking all over the internet for two weeks now and I have no clue what is happening.
I have an app running on a node.js server. The app uses the Vue.js framework and Vuetify.js, so I don't have a "traditional" js server. The website works perfectly on local, but every time I try and deploy it on an Azure (Windows) web application (per request from the company I am developing for), the only thing that is displayed is this: " The page cannot be displayed because an internal server error has occurred. ".
I did set the Azure Web App to use node.js as instructed on the official documentation.
According to my searches, it is probably a problem with my web.config file, but I can't seem to solve it, so would be really happy if someone could help me out here.
What I have tried so far:
multiple versions of the Web.config file
opening the 443 and 80 port on the Azure Web App to rule out any kind of conflict there
moving around my Vue classes to try and solve a problem there
making the front end in HTML files and in Vue files. Right now it is back into Vue files
I can't seem to find what else to try and would be really grateful if anyone had a solution!
I can add my web.config here if needed
Thanks in advance!
I am fairly new to NodeJS, here is the problem statement:
I have a small app (let's consider default app) of ReactJS. I installed NodeJs on my Ubuntu Server. Now when I hit mydomain.com in a browser I want my ReactJS app to show there. I know I need to do some configuration but somehow not able to find what's the right way of doing it. I have nothing installed on my Ubuntu server except NodeJS and npm.
Any suggestion will help me.
Thanks
For pure Node.js solution, tou can use static files (HTML/JS/CSS) HTTP server like following
https://github.com/cloudhead/node-static
https://github.com/indexzero/http-server
I've used http-server which is super simple and can be installed as a CLI tool as well
We have created an application that runs on node.js using Angular2 but you have not launch it with "npm" which uses the lite-server. However, we are being told that we much run under IIS but the problem is npm loads all of the packages for you correctly, IIS and IISNode know nothing about all these packages we have downloaded via "npm". We have yet to see anyone who has ever created an Angular2 or even Angular application that runs under IIS using IISNode.
Does anyone know how we would have it load all the modules correctly?
I answered Mike's question within the issue he opened on the IISNode Repo on Github. Here are the excerpts from that issue answer.
Angular2, as far as I know, has nothing to do with IISNode and shouldn't present any issues with running your app in an IISNode environment.
IISNode provides a way to run node.exe on an IIS Server instead of using a process manager like pm2 or forever. You can run an Angular2 app hosted with a Node.js/Express backend easily by just following any examples for getting an Express server running in IISNode. Take a look at this tutorial I wrote on StackOverflow for getting an Express app running in IIS with IISNode. Once you've got your Express app running its just a matter of getting your Angular2 transpiled to a browser compatible JS version and serving that.
I was able to successfully run the Angular2 Quickstart in IISNode just now (I know this isn't a full blown app) and I also know I wouldn't have made my node_modules static but for the purpose of the exercise I have.
Here is the repo it works perfectly and loaded up just fine for me.
Just clone the repo, place on your IIS box and do npm i and you shou>ld be good to go. Make sure the app is reachable at root otherwise you'll need to do some additional work. Again I know this is simplistic but it is a demonstration that IISNode has no problem with loading the essentials of Angular2.