azure web sites - IISNode running Node.js with multiple domains issue -


I do not have any basic, no-frills node NPM-Express blog site on the auction website and IIS load balancing or just iisnode That causes the issues that cause the app to run. Js. Walking out of IIS did not experience any issues. No website, just express it using vash templates.

The problems I have run are: Using web deployment and some node_module, for example if npm lwip works first, then it will not be reappointed again. Sometimes other JS and Wash files are not updated either.

While using the site a plain wash templates section (has to face public) and the site had a login side. Simple one-page public has to face a message 500 error will cause one of the three requests it will have to do. No logs were generated and all logging was turned on. The error was from iisnode and not only the node.

Using Visual Studio 13 with all the latest updates, remote debugging was simply not working. Actually the log-in part was used in the dark using NPM-passport-local, but the domain was never changed while using it. It was only the public-page page which would be so. FYIs were multiple sub-domains pointing to multiple domains and sites in the public side. Everyone entered the Ezoor portal correctly and will work with intermittent 500 errors. This page contained links to other blogs with the entire URL, so the domain would change which problem should be, but I suspect there was something to do with it.

I ended up putting nodes on my own to create a blue VM and work on the site without the use of IIS. FYI, I did not have to face any issues to run the node site locally on my sand.

Has it experienced any kind of issues using the Isionode and have you got work for it? I suspect that this can happen when multiple domains are used for the same example.


Comments

Popular posts from this blog

winforms - C# Form - Property Change -

java - Messages from .properties file do not display UTF-8 characters -

javascript - amcharts makechart not working -