I developed an asp.net 5 application that works in local IIS.
I installed .net dnx via dnvm
httpplatformhandler 1.2 for IIS
But in server there is plesk. I create the domain from plesk and try to publish the site in there.
After creating the domain I setted root folder to "wwwroot" of my published project. When I try to open the website in browser it just wait for connection. Does not return anything at all.
When I put index.html file only it works.
Plesk creates a user for application pool. I also gave it to read write permissions to all directories.
If I change the application pool user to something else like network service it just gives 500 internal error with no decription.
Any suggestions?
Related
I'm attempting to get IIS to serve our ASP.NET 6 web application, but every time it complains of needing a default document. If I run the exe (kestrel) one it will serve it, but we want it to be hosted by IIS with the other components of the site.
I installed the 6.0.10 runtime w/ hosting package and these are the results when listing runtimes:
When looking at the site modules, I think it should have what is needed (think the AspNetCoreModuleV2 one handles the compiled routing scenario?):
Have rebooted the server and the app pool specifically, set to No Managed Code, and whenever I attempt to load the page at the localhost level, I get:
The views are compiled so I don't think I even need IIS to open views locally in any capacity.
Everything you've posted ticks off the major deployment steps for hosting a .NET 6 project on IIS:
Installed the .NET Core 6.0 Runtime Windows Hosting Bundle
Set up the IIS app pool with "No Managed Code"
Rebooted the server: "Have you turned it off and on again?"
After our exchange in the comments, the only thing that appeared to be missing is to use the .NET publish command; not the build command.
When deploying to IIS, you'll want to run the dotnet publish command and then deploy those artifacts to your IIS server. From the docs:
The dotnet publish command's output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution. It's the only officially supported way to prepare the application for deployment. Depending on the type of deployment that the project specifies, the hosting system may or may not have the .NET shared runtime installed on it.
You also may want to review: Publish .NET apps with the .NET CLI.
I can't get my IIS site to run and I've tried most of the solutions I've seen. I started with a clean IIS server for testing this. If I try to access via the DNS name I get a 503. If instead I get on the webserver and run dotnet path\to\app.dll it starts without issue, and I can then curl localhost:5000/weatherforecast and get back the default JSON. So the app itself is clearly fine and working, it's something in the IIS config. Here's what I did:
Installed the .NET Core Hosting Bundle on my Windows Server 2019 system, then rebooted.
Ran Computer Management and in System Tools -> Local Users and Group -> Groups I added the domain account to both Users and IIS_IUSRS groups.
In IIS Manager I created a new site and set the binding to my DNS name on port 80.
Set the application pool for that new site to No Managed Code for the CLR version and set the identity to the domain account.
Created a default VS 2019 ASP.NET Core API, set the target framework to .NET 5.0
Published, via a Folder Profile, with a target framework of net5.0 and a runtime of win-x64.
Restarted the IIS site then went to http://my.domain.name/weatherforecast and got a 503.
I'm not even remotely close to being an IIS administrator, so at this point I don't know how to further debug the issue.
I know how to install and setup nopCommerce.
However this is specific to hosting it on Godaddy Windows Plesk account, I have searched, looked and read many threads, documents on nopCommerce 4.0 and hosting it or installing it. However I am unable to successfully install nopCommerce 4.0 on Godaddy Windows Plesk (not VPS) Hosting.
I get 500 internal server error, looks like .NET Core is not supported on Windows Plesk hosting on Godaddy, on VPS hosting it works.
So is any one able to successfully do it on Plesk?
As mentioned in my comment above:
You will need .net framework 4.61+ and .net core 2.0+ runtime to successfully run nopCommerce 4.0.
And as mentioned by you
GoDaddy with Plesk does not support .NET Core yet.
See https://in.godaddy.com/help/software-versions-on-hosting-accounts-897
In .net core, iis is not really used as a web service, its just use to point users to application. Application is a exe file so actually windows will run it, so i dont think that its a issue of plex or something like that.
I hade same error for nop4 on vps, but i cant tell you any advice if you don't check logs.
Try see the logs,application set logs automatically as a text file.
You may solve when check that file or create another question so we can help you and others who had the same error
When trying to launch solution, I receive the following error:
error : The Web Application Project MyApp is configured to use IIS. The Web server 'http://localhost:64646/' could not be found.
How do I resolve this issue?
I opened IIS and set the TCP port on the Default Web Site to 64646 and the project loaded without error.
You need to install IIS on your development machine.
Using IIS you'll also need to run Visual Studio in Admin Mode as well.
It is recommended that you use IIS Express since it will allow you to run VS without Admin privileges.
You have to install IIS and create the web site in IIS with the matching port number. Someone else created the visual studio web project to use IIS and configured it on their computer. Each person who opens the solution has to have all the websites configured in IIS manually.
You might consider creating a script that auto-creates them in the source repository. You can do it using AppCmd.exe (ADD SITE, ADD APPPOOL, LIST APPPOOL, LIST SITE) (%windir%\system32\inetsrv\AppCmd.exe).
Using Web Deploy I am having problems creating a import server or site package. There appears to be no documentation on this. I am using Windows 7 and IIS 7.5, Web Deploy 2.0.
I want to be able to create a deployment package to include the App Pool and Website information so can be installed at the root of IIS without having to manually create anything.
The article Synchronizing by using Packages details the basic Web Deploy steps for creating a site or server package and then importing it on another server. If you want to package and deploy an IIS 7 Web server, you'd use the webServer provider. If you want to package and deploy an IIS 7 website, you'd use the appHostConfig provider.
To include the app pool in the operation, you'll need to use the -enableLink:AppPoolExtension switch, like this:
msdeploy -verb:sync -source:appHostConfig="Default Web Site" -dest:appHostConfig="Default Web Site",computerName=Server2 -enableLink:AppPoolExtension
For more on the enableLink setting, see Web Deploy Operation Settings. For more on link extensions, see the Web Deploy Link Extensions page.