deploying asp.net core 2.1 web application on window hosting receiving 403
up vote
0
down vote
favorite
I have deployed my newly created web app developed in Asp.net core 2.1 on a windows based shared plesk hosting.
When i tried to browse the site, it give me this error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
I have searched it on google but all the help is coming for .net framework not for the .net core framework. Existing solution has suggested me to put this code in web config
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
but in .net core 2.1 there is no web.config in the project..
Bottom line issue is still there, don't know what to do.
asp.net asp.net-core-2.0 asp.net-core-mvc-2.0
asked Nov 10 at 14:14
Shahjahan KK
42211
add a comment |
up vote
0
down vote
favorite
I have deployed my newly created web app developed in Asp.net core 2.1 on a windows based shared plesk hosting.
When i tried to browse the site, it give me this error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
I have searched it on google but all the help is coming for .net framework not for the .net core framework. Existing solution has suggested me to put this code in web config
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
but in .net core 2.1 there is no web.config in the project..
Bottom line issue is still there, don't know what to do.
asp.net asp.net-core-2.0 asp.net-core-mvc-2.0
asked Nov 10 at 14:14
Shahjahan KK
42211
1
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related withplesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.
– Tao Zhou
Nov 13 at 6:19
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have deployed my newly created web app developed in Asp.net core 2.1 on a windows based shared plesk hosting.
When i tried to browse the site, it give me this error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
I have searched it on google but all the help is coming for .net framework not for the .net core framework. Existing solution has suggested me to put this code in web config
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
but in .net core 2.1 there is no web.config in the project..
Bottom line issue is still there, don't know what to do.
asp.net asp.net-core-2.0 asp.net-core-mvc-2.0
asked Nov 10 at 14:14
Shahjahan KK
42211
I have deployed my newly created web app developed in Asp.net core 2.1 on a windows based shared plesk hosting.
When i tried to browse the site, it give me this error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
I have searched it on google but all the help is coming for .net framework not for the .net core framework. Existing solution has suggested me to put this code in web config
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
but in .net core 2.1 there is no web.config in the project..
Bottom line issue is still there, don't know what to do.
asp.net asp.net-core-2.0 asp.net-core-mvc-2.0
asp.net asp.net-core-2.0 asp.net-core-mvc-2.0
asked Nov 10 at 14:14
Shahjahan KK
42211
asked Nov 10 at 14:14
Shahjahan KK
42211
asked Nov 10 at 14:14
Shahjahan KK
42211
asked Nov 10 at 14:14
Shahjahan KK
42211
asked Nov 10 at 14:14
Shahjahan KK
42211
42211
1
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related withplesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.
– Tao Zhou
Nov 13 at 6:19
add a comment |
1
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related withplesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.
– Tao Zhou
Nov 13 at 6:19
1
1
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related with
plesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.– Tao Zhou
Nov 13 at 6:19
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related with
plesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.– Tao Zhou
Nov 13 at 6:19
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
First of all ensure that the your shared hosting provider support .NET Core hosting as it requires .NETCore Hosting Bundle installed and .NET CLR Version set to No Managed Code
Next publish your ASP.NET Core web app which will generate web.config file and then upload the published files on the server.
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
add a comment |
up vote
0
down vote
You may need to look at hosting's website or get in contact with them to determine whether they support .NET Core, at what runtime version and what needs to be done to have it set up for a website. They may need to do it manually and you may need to downgrade to their version.
The simplest way to handle this with shared hostings is to publish fresh template that works locally, copy it over to hosting (or use Web Deploy to do this directly from Visual Studio) and if it errors, write a ticket that your .NET Core site isn't working and it's up to them to install and set up everything that is necessary.
If they can't get it working, then you won't be able to either. Nothing else you can do, but to change hosting provider.
answered Nov 10 at 16:01
Xeevis
2,1541417
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
First of all ensure that the your shared hosting provider support .NET Core hosting as it requires .NETCore Hosting Bundle installed and .NET CLR Version set to No Managed Code
Next publish your ASP.NET Core web app which will generate web.config file and then upload the published files on the server.
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
add a comment |
up vote
0
down vote
First of all ensure that the your shared hosting provider support .NET Core hosting as it requires .NETCore Hosting Bundle installed and .NET CLR Version set to No Managed Code
Next publish your ASP.NET Core web app which will generate web.config file and then upload the published files on the server.
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
add a comment |
up vote
0
down vote
up vote
0
down vote
First of all ensure that the your shared hosting provider support .NET Core hosting as it requires .NETCore Hosting Bundle installed and .NET CLR Version set to No Managed Code
Next publish your ASP.NET Core web app which will generate web.config file and then upload the published files on the server.
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
First of all ensure that the your shared hosting provider support .NET Core hosting as it requires .NETCore Hosting Bundle installed and .NET CLR Version set to No Managed Code
Next publish your ASP.NET Core web app which will generate web.config file and then upload the published files on the server.
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
answered Nov 10 at 15:33
Mohsin Mehmood
2,0762513
2,0762513
add a comment |
add a comment |
up vote
0
down vote
You may need to look at hosting's website or get in contact with them to determine whether they support .NET Core, at what runtime version and what needs to be done to have it set up for a website. They may need to do it manually and you may need to downgrade to their version.
The simplest way to handle this with shared hostings is to publish fresh template that works locally, copy it over to hosting (or use Web Deploy to do this directly from Visual Studio) and if it errors, write a ticket that your .NET Core site isn't working and it's up to them to install and set up everything that is necessary.
If they can't get it working, then you won't be able to either. Nothing else you can do, but to change hosting provider.
answered Nov 10 at 16:01
Xeevis
2,1541417
add a comment |
up vote
0
down vote
You may need to look at hosting's website or get in contact with them to determine whether they support .NET Core, at what runtime version and what needs to be done to have it set up for a website. They may need to do it manually and you may need to downgrade to their version.
The simplest way to handle this with shared hostings is to publish fresh template that works locally, copy it over to hosting (or use Web Deploy to do this directly from Visual Studio) and if it errors, write a ticket that your .NET Core site isn't working and it's up to them to install and set up everything that is necessary.
If they can't get it working, then you won't be able to either. Nothing else you can do, but to change hosting provider.
answered Nov 10 at 16:01
Xeevis
2,1541417
add a comment |
up vote
0
down vote
up vote
0
down vote
You may need to look at hosting's website or get in contact with them to determine whether they support .NET Core, at what runtime version and what needs to be done to have it set up for a website. They may need to do it manually and you may need to downgrade to their version.
The simplest way to handle this with shared hostings is to publish fresh template that works locally, copy it over to hosting (or use Web Deploy to do this directly from Visual Studio) and if it errors, write a ticket that your .NET Core site isn't working and it's up to them to install and set up everything that is necessary.
If they can't get it working, then you won't be able to either. Nothing else you can do, but to change hosting provider.
answered Nov 10 at 16:01
Xeevis
2,1541417
You may need to look at hosting's website or get in contact with them to determine whether they support .NET Core, at what runtime version and what needs to be done to have it set up for a website. They may need to do it manually and you may need to downgrade to their version.
The simplest way to handle this with shared hostings is to publish fresh template that works locally, copy it over to hosting (or use Web Deploy to do this directly from Visual Studio) and if it errors, write a ticket that your .NET Core site isn't working and it's up to them to install and set up everything that is necessary.
If they can't get it working, then you won't be able to either. Nothing else you can do, but to change hosting provider.
answered Nov 10 at 16:01
Xeevis
2,1541417
answered Nov 10 at 16:01
Xeevis
2,1541417
answered Nov 10 at 16:01
Xeevis
2,1541417
answered Nov 10 at 16:01
Xeevis
2,1541417
2,1541417
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239825%2fdeploying-asp-net-core-2-1-web-application-on-window-hosting-receiving-403%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
If you publish your APP and no web.config is present, the build process creates one for you. That means you can just add a web.config with all the settings you need.
– Marco
Nov 10 at 14:20
by default in asp.net core they don't use web.config in there projects and we never do any configuration what we use to do in web.config in .net framework. Should i still have to create web.config manually even .net core don't support it?
– Shahjahan KK
Nov 10 at 14:23
It is a misunderstanding, that .net core does not support xml configuration. IIS still relies on those configs and if you use one, those settings will be used and override the more generic settings on the server.
– Marco
Nov 10 at 15:41
@ShahjahanKK Have you publish your files properly? Maybe you can take a look at this tutorial, dotnet4hosting.asphostportal.com/post/…
– Douglas Thomas
Nov 12 at 4:11
Try to add web.config to your project and publish it, you could enable stdoutLogEnabled to check whether there is any error. Try to check whether it is related with
plesk hosting, refer similiar error Plesk on Windows is not accessible from certain locations or for certain clients: 403 Forbidden.– Tao Zhou
Nov 13 at 6:19