You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nothing about the installation on a IIS 10? please add the documentation, the setupsamples.bat throwing error
PS C:\Program Files\iisnode> .\setupsamples.bat
Installation of node.js samples for IIS 7
This script must be run with administrative privileges.
This installer will perform the following tasks:
* ensure that the IIS_IUSRS group has read and write rights to "C:\Program Files\iisnode\www"* delete the "Default Web Site/node" web application if it exists
* add a new site "Default Web Site/node" to IIS with physical path pointing to "C:\Program Files\iisnode\www"
This script does not provide means to revert these actions. If something fails in the middle you are on your own.
Press ENTER to continue or Ctrl-C to terminate.
Appuyez sur une touche pour continuer...
Ensuring IIS_IUSRS group has full permissions for"C:\Program Files\iisnode\www"...
fichier traité : C:\Program Files\iisnode\www
1 fichiers correctement traités ; échec du traitement de 0 fichiers
...success
Ensuring the "Default Web Site/node" is removed if it exists...
ERROR ( message:Impossible de trouver l'objet APP avec l'identificateur "Default Web Site/node". )
Installation failed. Cannot ensure site "Default Web Site/node" is removed
PS C:\Program Files\iisnode>
Azure seems to be using a private build of iisnode from January 2018, versioned 2.27.0, whereas the current release (from 2017) is 2.26. It seems to work just fine on Windows 10 / Windows Server 2016 through Windows Server 2022.
You can grab a copy of the binaries by accessing Kudu for your App Service and copying the files from C:\Program Files (x86)\iisnode
...or if you're comfortable with trusting a random stranger from the Internet, I've exfiltrated all of the files under C:\Program Files (x86)\iisnode and C:\Program Files\iisnode and put them in this .zip file.
Because I created my test AppService in the Shared tier (D1) it was running the 32-bit version of Node. I've also included the 64-bit files from C:\Program Files\iisnode - (what's interesting is that the x64 files include the www files but the 32-bit version does not - I assume because node.exe itself runs as a 64-bit process so it won't need different filesystem paths).
Activity
lextm commentedon Jun 1, 2024
Since 2015 HttpPlatformHandler has been a more suitable option to host Node.js web apps on IIS, https://docs.lextudio.com/blog/the-rough-history-of-iis-httpplatformhandler/
daiplusplus commentedon Jun 17, 2024
Azure seems to be using a private build of
iisnodefrom January 2018, versioned 2.27.0, whereas the current release (from 2017) is 2.26. It seems to work just fine on Windows 10 / Windows Server 2016 through Windows Server 2022.You can grab a copy of the binaries by accessing Kudu for your App Service and copying the files from
C:\Program Files (x86)\iisnodeScreenshot proof:
daiplusplus commentedon Jun 17, 2024
...or if you're comfortable with trusting a random stranger from the Internet, I've exfiltrated all of the files under
C:\Program Files (x86)\iisnodeandC:\Program Files\iisnodeand put them in this.zipfile.Because I created my test AppService in the Shared tier (D1) it was running the 32-bit version of Node. I've also included the 64-bit files from
C:\Program Files\iisnode- (what's interesting is that the x64 files include thewwwfiles but the 32-bit version does not - I assume becausenode.exeitself runs as a 64-bit process so it won't need different filesystem paths).2024-06-17 - Azure iisnode 2.27.0 exfiltration - x86 and x64.zip