We Keep Coding

Server Error 403 Forbidden on Blazor server app published to Linux hosting

I want to deploy a Hello World Blazor Server App created with the Blazor App Source Template 3.1.11 in VS2019 C#
The app is created in VS2019 on Windows 10
The docs show how to create the /bin/Release/{TARGET FRAMEWORK}/publish folder
I copied the files here to the domain folder in my hosting package, but do not know the next step.
web.config is for windows hosting.
What do I need to do for Linux?
At the moment I get a 403 error if I go to the site.
I can publish the app to a windows hosted site.
[Update]
It turns out that the Linux server does not have DotNet installed.

By default, dotnet publish publishes the entire application for running on the current operating system. When that does not match where you intend to run the application you can specify the runtime to publish for with -r|--runtime.
Something like this should work: dotnet publish -r linux-x64

A 403 error would lie somewhere in the IIS/web server configuration. Look at the config file or the IIS settings.

ASP.NET Core: A dependency package was not found in the production

I have an ASP.NET Core project targeting .NET Core 2.0. The problem is that when I publish my project to IIS (through Visual Studio Publish Wizard) server and browser the site I face with below error page.
I enabled error logs and found below error in the logs:
Error:
An assembly specified in the application dependencies manifest (RubyVAS.deps.json) was not found:
package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
aspnetcore-store-2.0.3.xml
Also here is the same problem as me, but none of the solutions worked.
https://github.com/dotnet/coreclr/issues/13542
But when I publish it with dotnet publish the error disappears but another strange thing happens. That is the [Authorize] filter stops working in this case. That means I can browse all controller actions as anonymous without login, while it should redirect me to login page. However this works without any problem when I run the project from within the Visual Studio. I have searched a lot for this problem and it is not a mis-configuration in my startup.cs.
I hope someone would know what is going on here?

Unable to run ASP.NET Core rc2 in IIS

So, I've been trying to publish my Core App to local IIS server but whatever I do it just doesn't want to run.
What I do is find the project in windows explorer and open a command window there, and write the following:
dotnet publish --framework netcoreapp1.0 --output "C:/ReleaseWebsite" --configuration Release
Which well executes without any errors, and finally says that it published the project correctly.
After that I go to IIS and Add New Website, set it to port 80 or 8080, I even tried with 8088, and after set the path to the published files, I edit the Application Pool and set it to No Managed Code. Start the website but all I get it 500 error An error occurred while starting the application.
If I go manually to the published files and open GST.Web.exe it starts without any issues, and rusn on port 5000 and I can access it without any problems. But I want to run it in IIS. Any help?

Refer Publishing to IIS article.
I think you must have done all the steps from this article except installing .NET Core Windows Server Hosting bundle on the server.
Install the .NET Core Windows Server Hosting bundle on the server.
This bundle will install the .NET Core Runtime, .NET Core Library, and the ASP.NET Core Module. The module creates the reverse-proxy between IIS and the Kestrel server.
See if this helps.

Running ASP.NET MVC 6 Web API from IIS

I create a MVC 6 Web API project that is running as expected from Visual Studio, when I'm however deploying to production I'm getting a
An error occured while starting the application
error.
I did the following on the production machine
Installed ASP.NET 5 from https://get.asp.net
Made sure that the production environment is running the same dnx version
that the application was published with
Installed HttpPlatformHandler 1.2
Set the application pool .NET CLR Version to No Managed Code
Pointed the root location to the wwwroot folder
Is there anything else that I'm missing?

When you run into 500 errors, remember that ASP.NET 5 application can be self hosted,
Open a command prompt
Browse to the application directory
Type in web.cmd
I had some reference problems within my application that was listed in my command prompt which I subsequently fixed and everything worked as expected.

500 can be thrown by different failures. Take a look on http://docs.asp.net/en/latest/publishing/iis.html what u've missed in your configuration.
And you should call it ASP.NET Core 1

Error CS0006: Application runs locally but not from server

I have an application that is built from a TFS Build server into a drop folder. The application builds with no errors reported. The application is in C# using .NET 4.5.1.
When I copy the deployment folder to my local desktop, the application runs fine.
However, when I copy the deployment folder to our internal server, I get the following error when trying to run:
error CS0006: Metadata file
'file:\NNNNSERVER\YourEXEFolder\log4net.DLL' could not be found
This error is repeated for all DLL's in the project and for the executable itself.
Other applications with similar profiles (C#, .NET 4.5.1) run fine on the same server. It seems to me to be pretty clear that its not the build or the code but something with the server or permissions, but I need to find something to tell our systems people.