404 Error

[barnesb8]

I was able to successfully get the application running locally, but am struggling to get it deployed to IIS. I've followed the directions provided to configure leaf with IIS, but continue to receive a 404 error when I try to browse to the API which I believe causes me to see the "Hmm... No Leaf server was found. Please notify your Leaf administrator." message in the UI. When I check the windows event viewer, I get an "Application '...\leafapi\api' started successfully." message. However, in the leaf-api log file I am getting a StatusCode 404 error. I do also have fatal errors shown in the log indicating that Leaf is not secured by authorization, but I've compiled the API with the -Debug flag. I've also checked the IIS log, but it did not provide any further details. Anyone have suggestions on other ways to debug this error to determine the issue?

[ndobb]

Hi @barnesb8, are you able to post the full contents of the Leaf API log file? That should help us debug.

[ndobb]

Comparing to my local dev .log file and one of our deployed servers, I see the first log entry for "HostingRequestStartingLog" appears to consistently be /leafapi/api/config, which is called when the user logs in, as opposed to /leafapi, which I see in your file.

Following https://leafdocs.rit.uw.edu/installation/installation_steps/8b_configure_iis/, can you confirm that:

1. The IIS path to the Leaf 'site' is "/"?

2. You've added the rewrite rule to /leafapi?

Your configuration in IIS should look like this:

Basically, "/" should return the Leaf client web app, while "/leafapi/..." should be rewritten by IIS to "/api/..." and return API calls.

[barnesb8]

I can confirm that I followed the directions from the link you mentioned. The application path to the leaf site is "/" and the rewrite rule was added to /leafapi. I did have to relocate the rewrite rule to the root leaf site instead of being directly on the leafapi application, which I had previously misconfigured. After making this update and restarting the app pool, I'm still receiving the same log messages, but let me know if I can provide any other information.

[ndobb]

That sounds right. In your browser, can you go in the Network tab while starting the app and take a screenshot? I'm looking for some kind of sequence like the example below from which we can determine what calls the app is making to the API and what the point of failure is.

[barnesb8]

I think this is what you're looking for

[ndobb]

Hi @barnesb8, just checking in. Were you able to get this sorted out?

We can optionally do a Zoom debug with you if that would be helpful.