failed to deploy custom-server-express to Azure Web App

[JeryLu2020]

Bug report

Describe the bug

when deploying the project to Azure, in the CMD of Kudu, run "npm start" can see the success message "Ready on http://localhost:3000"
However the website still shows 500.
I already run "npm run build" and generated the .next folder, but how can I set the web.config so that the IIS can find the access for the project??
https://jery-nextjs.azurewebsites.net/

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Download and build "custom-server-express" locally
2. Use FTP to deploy the code to Azure or directly drag the files to Azure Kudu
3. Add web.config file and set the entrance to "server.js"
4. See error 500

Expected behavior

the website should be running OK like local environment

Screenshots

error page

file directory

web.config

so where is the entrance for the next JS in IIS? in the .next folder?

System information

• OS: Windows
• Browser (if applies) chrome
• Version of Next.js: latest

[JeryLu2020]

for react app the "index.html" is the entry point in the web.config, but fot Next, it is not, so I wonder how can this be achieved? thanks in advance!!

[timneutkens]

I'm not sure what to do with this. I guess you'll have to ask support from Azure. All Next.js needs is next build and next start (or NODE_ENV=production node server.js when using a custom server) to boot up.

[timneutkens]

Feel free to contribute an example back when you figure this out.

[JeryLu2020]

@timneutkens thanks! but when run "next build" and "next start", will the server.js read the client code from the ".next" folder?

[timneutkens]

next start doesn't use your custom server. NODE_ENV=production node server.js will. .next holds the build output that is needed to boot up the production application.

[JeryLu2020]

@timneutkens still doesn't work, seems no good solution yet.....I'll have to implement these features for React myself...

[timneutkens]

If it doesn't work with Next.js I doubt it'd be any different when you implement your own custom server.

[JeryLu2020]

@timneutkens it works perfectly in local, also works good in Linux, but failed with Azure PaaS

[chcepe]

Were you able to deploy next with custom server on Azure App Service?