The problem for the API side has been solved. Was a really stupid mistake on my side. If anyone ever gets this problem remember to change the app pool to unmanaged code instead of .net 4.0.
Hi,
I had a look at the config file and this is the part that is confusing me a bit with the ASP.Net Core side with the deployment.
The config file contains almost no data as the config is done in the appsettings.json file.
Within both the web.config and the appsettings.json i could not find any specific invalid char or anything that is blocking access.
Since all the config is done in the appsettings.json file, should there be IIS config to handle the reroute to the appsettings file or something in that line.
This is so far just trying to get the API hosted.
<span style="color:#FF0000"><ins>Please see below the web.config file data:</ins></span>
<?xml version="1.0" encoding="utf-8"?> <configuration>
<system.webServer> <handlers> <add name="aspNetCore" path="" verb="" modules="AspNetCoreModule" resourceType="Unspecified"/> </handlers> <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"/> </system.webServer> </configuration>
<ins><span style="color:#FF0000">Please see below the appsettings.json data:</span></ins>
{ "ConnectionStrings": { "Default": "Server=Server Database=Database;User Id=User; Password=Password;" }, "Abp": { "RedisCache": { "ConnectionString": "localhost", "DatabaseId": -1 } }, "App": { "ServerRootAddress": "http://localhost:22742/", "ClientRootAddress": "http://localhost:4200/", "CorsOrigins": "http://localhost:4200,http://localhost:49152" }, "Authentication": { "Facebook": { "IsEnabled": "false", "AppId": "", "AppSecret": "" }, "Google": { "IsEnabled": "false", "ClientId": "", "ClientSecret": "" }, "Microsoft": { "IsEnabled": "false", "ConsumerKey": "", "ConsumerSecret": "" }, "JwtBearer": { "IsEnabled": "true", "SecurityKey": "HostingTemplate_8CFB2EC534E14D56", "Issuer": "HostingTemplate", "Audience": "HostingTemplate" } }, "Recaptcha": { "SiteKey": "6LfD-wUTAAAAACULAVXvL61K0w02RIsjhI8EyiS-", "SecretKey": "6LfD-wUTAAAAADm3h7vomd9FtaAlAwexki29BtXC" } }
I redownloaded the later template now to use a clean version for deployment as a test with the same result.
I also went through all of the guides for this specific template regarding config and setup to make sure i did not mis anything for the API and could not find anything that might cause problems.
Thank you,
Regards, Gideon Badenhorst.