iisnode | Hosting node.js applications in IIS on Windows | Runtime Evironment library

On the localhost module, lazy loading is working fine, showing meta tags and HTML content in in the view page source, but it is not showing on the live server. On the live server, I can only see meta tags and HTML contents of components that are direct children of AppModule but lazy loaded modules components are not showing meta tags and HTML. This weird behavior is only on the live server.

app.server.module.ts

I've got error during deploying my app to IIS Server. I use URL Rewrite and IISNode. I gave all permissions to IUSR and IIS_IUSRS, and I went throught a lot of errors, but I can't go through this one. I will be very grateful for your help.

I've got this error

My web.config file looks like:

I am attempting my first deployment of a Node.js web app to an Azure App Service. I am publishing through VS 2019 and it looks like it's publishing correctly.

I am able publish using the standard server.js code snippet that comes with default project creation. In a browser I see the correct Azure URL and "Hello World" displays correctly.

Here is the default code snippet:

I'm using a Linux server in azure app service. Previously, I was able to deploy my nextjs app with no problems on app service, and it ran just fine. However, after another deployment the docker image suddenly kept timing out. After hours of being unable to fix this, I deleted the app on azure, recreated it, and deployed and everything worked smoothly once again. After another deployment recently, it happened again and the docker image is timing out, and I'm unable to find what the problem is. Before anyone asks, yes, nextjs is starting on port 8080 and I have the PORT and WEBSITES_PORT app variables set to 8080 in app service, you'll also see this in the logs below. My web.config and server.js files are in the root directory. I also used this tutorial to publish the nextjs app on app service: https://parveensingh.com/next-js-deployment-on-azure-app-service/

Here are the logs:

Here's my server.js:

I have created website with React project and hosted on IIS webserver(ON VM). I have defined web.config file rules

I've run into a roadblock trying to get my web app to run on a Windows Azure App Service.

My app has a Node.js/Express back-end written in TypeScript (compiled with tsc, not Webpack) and uses Sequelize to connect to a SQLite 3 database, stored locally. The front-end is a React app built on Create React App.

The problem is that when sequelize tries to require sqlite3, a MODULE_NOT_FOUND error occurs, causing sequelize to throw a "Please install sqlite3 package manually". (See full stack trace below.)

The sqlite3 folder with the expected files is clearly present in the node_modules folder in the Azure file system, so I really don't get how require("sqlite3") could be failing.

Here's what I've tried so far:

1. I tried pretty much every suggestion in this sequelize issue.
2. I searched StackOverflow, but most of the questions relate to Electron, which I'm not using. Nonetheless, I read most of them, and tried any of the suggestions that seemed relevant.
3. I made sure the version of node on my development machine is the same as on my Azure Window App Service (14.16.0).
4. I tried deleting the node_modules folder and running npm install --production using the Azure console.
5. I tried running npm rebuild from the Azure console.
6. I tried running npm cache verify from the Azure console.
7. I tried globally installing sqlite3 using npm install -g sqlite3 from the Azure console, but that action was forbidden by Azure.
8. I tried installing sqlite3 from the source using npm install sqlite3 --build-from-source.
9. I added console log statements to node_modules/sequelize/lib/dialects/abstract/connection-manager.js to verify that the module name passed to the require statement was "sqlite3", and it was.
10. I tried replacing moduleName with the actual string, "sqlite3".
11. I checked to make sure all the sqlite3 files in my App Service file listing matched the ones installed on my development machine.
12. I probably tried a lot of other things I'm not remembering right now!

Needless to say, none of these things made any difference. Every time I checked the logs, the error was the same (and I checked the timestamps to make sure the logging system was actually working.)

Here is the full stack trace:

Error: Please install sqlite3 package manually

• at ConnectionManager._loadDialectModule (C:\home\site\wwwroot\node_modules\sequelize\lib\dialects\abstract\connection-manager.js:84:23)
• at new ConnectionManager (C:\home\site\wwwroot\node_modules\sequelize\lib\dialects\sqlite\connection-manager.js:24:21)
• at new SqliteDialect (C:\home\site\wwwroot\node_modules\sequelize\lib\dialects\sqlite\index.js:15:30)
• at new Sequelize (C:\home\site\wwwroot\node_modules\sequelize\lib\sequelize.js:340:20)
• at new Sequelize (C:\home\site\wwwroot\node_modules\sequelize-typescript\dist\sequelize\sequelize\sequelize.js:16:9)
• at getSequelize (C:\home\site\wwwroot\getDatabaseInfo.js:33:16)
• at Object.getDatabaseInfo [as default] (C:\home\site\wwwroot\getDatabaseInfo.js:15:23)
• at Object. (C:\home\site\wwwroot\server.js:55:47)
• at Module._compile (internal/modules/cjs/loader.js:1063:30)
• at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
• at Module.load (internal/modules/cjs/loader.js:928:32)
• at Function.Module._load (internal/modules/cjs/loader.js:769:14)
• at Module.require (internal/modules/cjs/loader.js:952:19)
• at Module.patchedRequire [as require] (C:\PROGRA~2\SITEEX~1\APPLIC~1\28F926~1.41\nodejs\node_modules\diagnostic-channel\dist\src\patchRequire.js:15:46)
• at require (internal/modules/cjs/helpers.js:88:18)
• at Object. (C:\Program Files (x86)\iisnode\interceptor.js:459:1)

What else can I try?

I am using i18n with Angular Universal SSR. The issue is that the client received the text in source locale and after a few seconds are replaced with the correcty locale.

For example, client load http://localhost:4000/en-US/ in the first display shows in es locale and after a few seconds the text is replaced with en-US locale texts.

The build folders are created correctly and the proxy works perfect for each locale. I want the server to return the html with the correct translation so the SEO crawlers can find the content correctly in each locale.

It seems that the problem is in the build, is not generated with the correct locale.

The proyect config in angular.json file:

I am currently using Okta with OIDC and Node Express to log into a web app that I made. I want my users to be able to logout of just my app and not okta itself as the okta is for my company and that would log them out of all the other websites that use the company okta. Okta recommends doing this on their website.

I am working to deploy an SSR nuxt app through azure.

When I run yarn build and yarn start locally, it works fine.

The pipeline is correctly building and sending the files over correctly.

I am copying over the file through the pipeline, then unzipping them.