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
Related
I am trying to find a way to deploy a ASP.Net Core (version 6.0) Website onto a server provided by a domain provider.
The server is Debian and as far as I can understand I cant change things on the server except uploading the files required for the Website.
I have created a simple website in Visual Studio 2022, using MVC Framework. It has no database as it is not required.
So the issue is how would I go about deploying the website onto the server, I understand I have to change my files to be Debian compatible but also I read up on the documents from Microsoft, and they insist I need to install .Net onto the server. Which I cant seem to do.
I tried reading through other solutions but there doesn't seem to be any updated answers.
I am new to this so sorry if this has been asked before. but any help would be welcome.
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 have configure orchard 1.8 with IIS 8 using windows platform installer on Windows Server 2012 r2
but showing me Http 500 page can not be displayed.. not loading the orchard CMS setup page.
I have given full permission with orchard in IIS as per mentioned steps online. but still not succeed. please help me on it.
Regards
Check the StaticFileModule is in IIS, something like this happened to me too in Window 8.1 and running on IIS Local.
but for the looks of it you might be missing more config stuff. Check your Windows Server IIS and make sure you have everything you need enabled and install. StaticFileModule was not installed in IIS in Windows 8.1.
We have an ASP.Net website running under the 4.0 framework in IIS 7.5 on a Windows Server 2008 R2 box. A portion of the web site functionality utilizes WCF and has a "standardEndpoints" section in the web.config.
The website works fine and everything works fine if we want to use the IIS Management Console GUI to do things.
We would like to use powershell to make changes to the web.site but when we run "Set-WebConfigurationProperty" an error is generated indicating that the "standardEndpoints" section of the web.config can't be processed.
The hotfix referenced here is not the solution. The website works, the hotfix appears to be only for Server 2008 (not R2), and when you try to install it, it says "not applicable for this server".
We did discover by running $PSVersionTable that PowerShell was referencing version 2.0 of the CLR. We installed Powershell 3.0 and now Powershell is referencing version 4.0 of the CLR but the problem persists.
We are looking to see if there is a simple solution to this. I suspect we may not have the right version of the IIS management script dll but can't find a different one to use. If the solution gets to complicated, we will just wipe the server and start from scratch.
Thanks for any suggestions,
John
Hi i'm trying to host an mvc4 web application on a web server and it is not working. Do i need to install something in particular so that it works? And what type of web server is the best for this type of situation?
You will need:
IIS, preferably IIS 7+
.Net installed on the server
make sure the framework is set correctly
Take a look here
if you have all this set up, let us know the error you are seeing.
1)IIS 7.5
2) MVC4 and Framework 4.5 should be installed
3) Also check that in ApplicationPools you set framawork 4.0 for your site (default is 2.0)
It would be better if you show a certain error you receive.
See the following Question... How to deploy an MVC 4 application to a Windows Web Server based dedicated hosting?
It seems incredabily relevant to what you are asking.
Also for future reference read https://stackoverflow.com/questions/how-to-ask before asking questions