Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,971 questions
Live NodeJS Server Returns A "This page isn’t working" Error On Browser GET Request.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 64%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
San Antonio
0
Reputation points
Good morning from here, Microsoft team,
I followed Microsoft's guide on this page to deploy my NodeJS (ExpressJS to be exact) app.
On starting the server, I get the log
Thu, 27 Apr 2023 10:20:20 GMT body-parser deprecated undefined extended: provide extended option at index.js:12:27
(node:17860) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.(Use
node --trace-deprecation ...to show where the warning was created)App server, live on port 3000!
Which is exactly what I should receive if the server was started correctly. It listens on port 3000 and all known env variables are set on the server.
However, when I navigate to my server domain at https://trackstack-server-test.azurewebsites.net, from my browser (via GET), it loads for about 2 - 5 minutes and I get an error page that says:
This page isn’t working
trackstack-server-test.azurewebsites.net is currently unable to handle this request.
HTTP ERROR 500
(You can navigate to the URL as well to see for yourselves.)
Please, what can I do to correct this?
Thank you.
Azure App Service
{count} votes
-
VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator2023-04-28T08:17:27.65+00:00 @San Antonio Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.
In general, Http 500 error code is more common error and might be caused due to multiple reasons.
Based on the shared information, I have looked at the backend logs and we see that the above mentioned is in free tier app service plan. I would suggest try scale-up the app service plan to higher sku and see.
If you still face the issue, I would recommend you to run the
WebAppdowndetector in Diagnose and solve problems under your app to indentify the cause of the this problem.The below set of documentation, might be helpful in troubleshooting the NodeJs apps on Azure App service :
- Best Practices and troubleshooting guide for nodejs apps.
- Debug Nodejs apps on App service 1 2.
Feel free to reach back to me if you have any further questions on this.
-
VenkateshDodda-MSFT 25,111 Reputation points Microsoft Employee Moderator
2023-05-02T05:31:17.5666667+00:00 Hello @San Antonio ,
Following up to see if you have a chance to check my previous response and helped. Do let us know if you have any further questions on this.
Sign in to comment
Sign in to answer