My web api app works fine locally and gets consumed fine by client app. After deployment to remote IIS 7.5 server however client app can't consume API and a '500 - Internal server error' is returned. The relevant IIS log is given below at the
end. I can access API just fine using url http://my-api.mydomain.com/swagger/.
Apart from IIS folder permissions what else could be the reason for this issue and how can I resolve it?
This is not a routing issue. A 500 error means there is an exception on the server. There can be many reasons for 500 errors.; configuration like an incorrect connection string and unexpected or missing data. On the client, it could be an unexpected
response from Web API.
The solution is adding better logging and exception handling to find the bug.
Member
20 Points
165 Posts
API routing not working in production
Jun 23, 2020 01:30 PM|yahya01|LINK
Hi
My web api app works fine locally and gets consumed fine by client app. After deployment to remote IIS 7.5 server however client app can't consume API and a '500 - Internal server error' is returned. The relevant IIS log is given below at the end. I can access API just fine using url http://my-api.mydomain.com/swagger/.
Apart from IIS folder permissions what else could be the reason for this issue and how can I resolve it?
Thanks
Regards
All-Star
53041 Points
23612 Posts
Re: API routing not working in production
Jun 23, 2020 01:53 PM|mgebhard|LINK
This is not a routing issue. A 500 error means there is an exception on the server. There can be many reasons for 500 errors.; configuration like an incorrect connection string and unexpected or missing data. On the client, it could be an unexpected response from Web API.
The solution is adding better logging and exception handling to find the bug.
Member
20 Points
165 Posts
Re: API routing not working in production
Jun 23, 2020 09:46 PM|yahya01|LINK
Thanks.