-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to deploy custom-server-express to Azure Web App #5043
Comments
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!! |
I'm not sure what to do with this. I guess you'll have to ask support from Azure. All Next.js needs is |
Feel free to contribute an example back when you figure this out. |
@timneutkens thanks! but when run "next build" and "next start", will the server.js read the client code from the ".next" folder? |
|
@timneutkens still doesn't work, seems no good solution yet.....I'll have to implement these features for React myself... |
If it doesn't work with Next.js I doubt it'd be any different when you implement your own custom server. |
@timneutkens it works perfectly in local, also works good in Linux, but failed with Azure PaaS |
Were you able to deploy next with custom server on Azure App Service? |
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:
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
The text was updated successfully, but these errors were encountered: