Hi Sim,
I can see both your Web Server and .NET Server are not working as expected.
1) For the Web Server issue: if you are fresh about IIS setup, I suggest that you can only follow this tutorial step by step, it can make sure your IIS setup is correct.
I haven't ever encountered this Web Server error, but you can also refer to this article to learn more about this error: 5 Ways to fix Server Error in ‘/’ Application Runtime Error (windowsreport.com)
2) For the .NET Server issue: '500 - Internal server error.'
We need to know more detail about this error. There is an easy way to write an IIS log file. Please find the web.Config file under the root of your Web API application site, change stdoutLogEnabled="false" to true, then check the logs at stdoutLogFile=".\logs\stdout".
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath=".\ServerAPIs.exe" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
</system.webServer>
</location>
</configuration>
Then restart the website and verify the Web API again: Verifying the Web APIs - - PowerServer 2022 Help (appeon.com)
Check the log file generated by IIS.
Alternatively, you can also enable PowerServer log, refer to: PowerServer logs - - PowerServer 2022 Help (appeon.com)
Regards, Logan
1) when you run http://[ip_of_net_server]:8889, did you see the page saying that the ASP.NET core app is successfully started?
2) when you run http://[ip_of_web_server]/datatrak_cloud_kl, did you go through the process of downloading and installing launcher?
3) At what point did you get the error 500?
3) you can also test by using localhost instead of ip address in the local server to verify that it is not a firewall problem.