62 lines
1.5 KiB
Markdown
62 lines
1.5 KiB
Markdown
# Honest Answer - iisnode Issue
|
|
|
|
## Problem
|
|
iisnode gives error 0x00000002 even with the simplest possible file. This means **iisnode itself cannot execute Node.js**.
|
|
|
|
## Root Cause
|
|
The iisnode installation or configuration is broken. Even after:
|
|
- ✅ Setting all permissions
|
|
- ✅ Configuring Node.js path
|
|
- ✅ Creating simplest test files
|
|
- ✅ Disabling logging
|
|
|
|
The error persists. This indicates a fundamental issue with iisnode.
|
|
|
|
## Solutions
|
|
|
|
### Option 1: Reinstall iisnode (Try This First)
|
|
1. Uninstall current iisnode
|
|
2. Download fresh from: https://github.com/Azure/iisnode/releases
|
|
3. Install correct version (x64 for 64-bit Windows)
|
|
4. Restart computer
|
|
5. Try again
|
|
|
|
### Option 2: Use PM2 (Recommended - Easier)
|
|
PM2 is simpler and more reliable:
|
|
|
|
```cmd
|
|
npm install -g pm2
|
|
cd dist
|
|
pm2 start server.cjs --name pozoapp
|
|
pm2 startup
|
|
pm2 save
|
|
```
|
|
|
|
Then access: `http://localhost:3000`
|
|
|
|
### Option 3: Run Node.js Separately + IIS Reverse Proxy
|
|
1. Run Node.js on port 3000
|
|
2. Configure IIS URL Rewrite to proxy to Node.js
|
|
3. No iisnode needed
|
|
|
|
### Option 4: Use IIS Application Request Routing (ARR)
|
|
Set up reverse proxy from IIS to Node.js running separately.
|
|
|
|
## My Recommendation
|
|
**Use PM2** - It's:
|
|
- ✅ Simpler
|
|
- ✅ More reliable
|
|
- ✅ Better for Node.js
|
|
- ✅ Works on Windows
|
|
- ✅ No IIS configuration headaches
|
|
|
|
## Why iisnode Failed
|
|
- Complex setup
|
|
- Permission issues
|
|
- Configuration problems
|
|
- Version compatibility issues
|
|
- Windows-specific quirks
|
|
|
|
PM2 avoids all these issues.
|
|
|