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!
Related
First off, I'm really, really sorry if this has been asked before, but I did not find a satisfying answer. This step seems missing / unthreatened in literally all explanations and tutorials out there.
I've read literally everything about making a Shopify App and I've built one and it works. I'm in the stage of submitting it, but I discovered the project directory is about 40k+ files large. When debugging the App, I ran the test server over ngrok over my local laptop, but it's kind of self explaining that I won't keep it running there 24/7 for the next 50 years.
After reading all guides, I still lack in one important information.
How is my app being pushed/pulled/deployed to their server? What exactly do I do to achieve this, and furthermore, how do I update bugfixes afterwards?
I am aware there is a review process and everything, the question is, when and how does my local app version move over to their servers. exactly?
I was really not able to find satisfying answers to this.
Help greatly appreciated.
You have to host your application on your own server be it a Public app or Custom app.
Public APP
They will review the approach not the code, they can't see your code,
it's deployed on your server.
In shopify developer account open create public app form, add your app urls.
Submit your app for approval.
Custom APP
They won't review anything, just deploy your app on your server and
add your links in the custom app form.
I have NextJS app with SSG. This functionality was added recently and according to it I should do next-export after next-build to get static files. But after appearing in 9.4 of Incremental Static Regeneration I need to keep server on by npm-start command (in my case I use custom server file with next-express functionality). It works good locally and It works good when I get artifact from Azure. But It doesn't work globally when it will be deployed finally. Help please
Through my attempts, I found that it is impossible to install globally or use next in Azure Web App. That is, it cannot be deployed through Github.Deploying using other methods such as FTP cannot run successfully. It should be related to the azure node environment.
But the method provided in this post says that it can be processed by adding web.config. I think it should be useful and helpful to you. Please read it carefully and try it.
You also can read this document, maybe it useful to you.
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.
I have a Mean stack node.js application and amazons remote desktop machine. I need to deploy my node.js application to amozon.
I have uploaded my files to wwwRoot folder. It contains a default index.html page.
After uploading files also, i got that same index.html display in browser.
Please let me know how i can deploy and run my node.js application.
Thanks in Advance
I highly suggest you follow a guide or tutorial to get yourself set up with a node.js web server. From your question is seems to me that you're missing some key points on how a node.js web server functions and there's really not a single answer to your question. I recommend you read up on the following tutorial:
https://blog.risingstack.com/your-first-node-js-http-server/
Good luck!
I put a basic, no frills node npm-express blog site up on a azure website and the IIS load balancing or just iisnode itself seemed to cause issues running the app.js. Running outside of IIS didn't experience any issues. No websockets, just express using vash templates.
The issues I ran into are:
Using web deploy and some node_modules intermittently not deploying. npm lwip for instance would work at first then wouldn't if deploying again. Sometimes other js and vash files would not update also.
When using the site there was a plain vash templates section (the public facing side) and a login side of the site. The simple one page public facing side would intermittently create a 500 error. One out of every three request would do this. No logs generated and all logging was turned on. The error was from iisnode and not node itself.
Using visual studio 13 with all the latest updates, remote debugging simply didn't work. Basically in the dark. Oddly the logged in portion using npm-passport-local worked but that never changed domains when using. It was only the pages on the public side that this would happen. FYI, the public side had multiple domains and various sub domains pointing to the site. All entered correctly in the azure portal and would work with the intermittent 500 error. The page had links to other blogs with full urls, hence the domain would change. Which should be an issue but I suspect had something to do with it.
I ended up having to create a azure vm and install node on it myself to get the site working without the use of IIS. FYI, running the node site locally on my sand I never encountered any issues either.
Has anyone else experienced issues like this using iisnode and did you find a work around for this?
I suspect it may happen when multiple domains are used for the same instance.