0

I have a angular universal application. When running locally (using express) everything works fine. It also works when running inside of node. However when I deploy production build to IIS with iisnode direct url navigate returns 500 Internal Server Error. I've had no luck with running it in node on azure.

lightbulb111
  • 23
  • 4
  • 2
    Check the logs inside iis – user733421 Mar 20 '21 at 18:59
  • 1
    Can you upload your sample code (be careful to hide confidential information)? This will help you solve your two problems. – Jason Pan Mar 22 '21 at 02:50
  • I created a new angular application, added universal per the docs. I created a new route i.e.: /contact-us. contact us loads fine, If I hit refresh I get 500 internal server error. – lightbulb111 Mar 22 '21 at 23:51
  • If my reply is helpful, please accept it as answer(click on the mark option beside the reply to toggle it from greyed out to fill in.), see https://meta.stackexchange.com/questions/5234/how-does-accepting-an-answer-work – Jason Pan Apr 02 '21 at 01:17
  • Has your problem been solved? Is there any progress? – Jason Pan Apr 06 '21 at 05:55
  • https://stackoverflow.com/questions/66871045/pm2-not-found-on-azure-app-service-with-node-14-runtime/66880978#66880978 – Jason Pan Apr 08 '21 at 06:09

1 Answers1

0

It is recommended that you use the contents of the build folder generated after npm run build when you publish. Like pic in this post. It's a good solution, and it works for me.

soultion

Copy blow file to wwwroot folder.

enter image description here

enter image description here

Reason

enter image description here

Jason Pan
  • 15,263
  • 1
  • 14
  • 29