I've finally come to publish one of my hobby projects, but the visual studio publish through FTP will not work, FileZilla on the other hand will.
Which left me with the question.. what do i upload?
The whole thing? thats what i tried first, uploading all to the root folder of my webhotel, and all i get is:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Detailed Error Information
Module DirectoryListingModule
Notification ExecuteRequestHandler
Handler HS-StaticFile
Error Code 0x00000000
Requested URL http://d32023759.u207.surf-town.net:80/
Physical Path D:\hshome\hb944222072\domain.dk
Logon Method Anonymous
Logon User Anonymous
Things that could have an effect:
The domain is not transfered yet, so i have a temp url?
(only time or stackoverflow will tell me)
The project is 4.5.1 .net and the Server version is 4.0?
(I cant imagine that throwing this error)
The configuration of the website?
For simplicity i have tried uploading a fresh Visual Studio ASP.NET 4.5.1 SPA with Web API template.
Which i hoped was configured to work out of the box.
And i really feel i've hit a wall googling for any guides or info while googling, so any help, pointers, hints or links to resources are very welcome.
In my Webhotel management, i had an option to set the ASP.NET Version and its Pipelinemode
Pipeline Modes:
Classic For instructions on enabling IIS6 or IIS7 classic mode
Integrated include the System.Web.Mvc assembly and everything just works
Copied from comment on this question, Thanks to Jon Erickson
Related
I have deployed my website developed in Asp net core 2.2 on Godaddy server.
After deploying I received error 500. As discussed with the Godaddy support I removed Web.config file.
Then it started throwing error 403. There is full permission to all folders and subfolders. I have searched a lot but unable to find any solution also Godaddy support is also not satisfactory.
I can't comment yet, otherwise I would. However:
Removing the web.config may not have been the correct move. My guess is now IIS has no idea that it should be running a .Net Core app, and instead tries to directory browse, which is disallowed so you receive a 403.
I'd also be wary now if you went and added full permissions on everything.
I would suggest re-deploying it from scratch and turning on the 'stdoutLogEnabled' in the web.config temporarily. Then the site should at least attempt to run again, and record an error log in the folder specified by the 'stdoutLogFile' path in the web.config.
More about stdoutLog here:
https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-2.2
I am trying to deploy a simple ASP.NET web application over the Internet, using the google cloud platform. I followed the tutorial on this page : https://cloud.google.com/dotnet/docs/getting-started/hello-world (I uploaded a slightly more complex app though). So basically everything went well from the creation of the ASP.NET framework virtual machine to the deployment from my computer to the VM since I've been able to reach for the web app home page through the VM IP address.
Starting Web deployment task from source: manifest(C:\Users...\obj\Release\netcoreapp2.2\PubTmp\myApp.SourceManifest.xml) to Destination: auto().
Updating file (Default Web Site\MyApp.deps.json).
Updating file (Default Web Site\MyApp.runtimeconfig.json).
Updating file (Default Web Site\web.config).
Successfully executed Web deployment task.
Problem is that the home page won't display as it did when I would deploy it locally (with IIS express) but rather throw an
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
I found some interesting subjects raising the same issue :
Deploying website: 500 - Internal server error : suggests to enable detailed errors and/or to change a few lines in the web.config file but I do not have a web.config file at my side of the process in my project (only a Startup.cs which does some of the work) and I cannot manipulate the one in the google virtual machine.
I noticed that before uploading the web app to the VM, the output displayed errors similar to these : https://github.com/dotnet/sdk/issues/1897 (message NETSDK1041) so I thought that the discrepancies between referenced/platform assemblies might be the origin of these errors but then, why wouldn't they impact the local deployment of the web-app too ?
I would like my web application to run on google cloud's VM (based on the generic Google Compute Engine ASP.NET framework), the web app is 'correctly' deployed to the host VM but raises a wild 500 - internal error. Anybody has any idea as to how I could at least identify the source of this error ? (Helping me find the web.config would also help greatly, I understand that everybody has this file somewhere, but I can't find it and don't have a clue on its whereabouts because I just used a random template MVC application on Visual Studio Community 2017 which did all the configuration work
I have built my first ASP.NET web API in MVC, when I debug the application from Visual Studio everything works perfectly.
Now I need to get these API's on my server...
I have tried copying the project files to the website root which usually works for normal MVC apps with views, and I have also built the project and copies the file full of DLL's and an exe to the IIS root.
Obviously, neither of these worked, anyone know what I am missing? Perhaps something I have to do with IIS?
I have now tried "publishing" the project and when I try to access the site this happens...
Thanks in advance!
Build the application then publish it. Copy the published files to a favorite IIS folder. Ensure you select the right version of ASP.NET in the server for your application in the application pool.
When you publish and get an error such as this it is often related to a configuration issue, or other non-supported .NET Runtime issue.
For best results, if you can get to the Event Viewer for the server a detailed error should appear there outlining the root cause of the issue.
If you don't have access to the server directly, updating the <system.webServer> section with the below should get you a detailed error.
<httpErrors errorMode="Detailed" />
Just please note DO NOT LEAVE THAT LINE IN PRODUCTION!
I seem to be having noob level errors here Publishing an ASP.NET app locally.
The site is:
Published to an ApplicationPool with No Managed Code per suggestions here
Is literally just the template code app from Microsoft specified in this article - no extra stuff.
I'm just trying to test settings here on my local machine before seeing how it works on another machine but perhaps I'm missing something? Everything I've read I can on the subject and simply can't seem to get this going - any step-by-step walkthroughs about doing this?
In my case, the answer was staring me right in the face - I was missing the AspNETCore Module. I thought I had it when enabling everything else with IIS but apparently, I didn't.
i publish my website and install iis on windows 7, and add my website into this address :
c --> inetpub --> wwwroot
and add permission to my folder (IIS_IUSRS , IUSR) but now when type this address (http://localhost/publish/default.aspx)(Publish folder is in wwwroot folder) in address bar of browser see this error :
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
plz help me!!
First a bit of googling may help you a lot (i heve seen this answer on Google before), second, this error is more likely because you don't have ASP.NET enabled in IIS, to enable open the Control Panel, go to Programs and Features, then go to Internet Information Services-> World Wide Web Services-> Application Development Features and enable ASP.NET, then click Ok and wait for the features to be enabled, also be sure you have installed the .NET Framework.