Frequently Asked Questions

1. Rule name conflicts in URL Rewrite:

When you want to run a second Frontend under a Frontend (Virtual Application), it may cause an error when the URL Rewrite rule has the same name in the web config settings of each Frontend. In this case, you can fix the error by changing the URL Rewrite rule name of the internal or external application.

• Go to the IIS folder on your computer.
• Open the “Web Config” file from the Frontend folder.
• Change the Rule Name > React Router Routes name. Thus, it will work when the two names are not the same.

2. Folder authorization problem:

If IIS was installed later when the server was first installed, access to the “inetpub” folder may be missing.

• To fix this, right click on the Frontend and Backend folders.
• Properties > Security > IIS > IIS > Users, add the IIS User and grant “Full Control” permission.

3. Backend 500.30 error:

• Connection String related errors:
  • Navigate to the IIS backend folder on your computer.
  • Check the “Kuikaappdb and Kuikacommondb” fields from the Appsetting.json file and fix the missing fields.
• Server communication problems:
  • Make sure that your application server has access permissions to your database server.
• Incorrect .NET 6 package:
  • Download ASP.NET Core Runtime - Windows - Hosting Bundle from https://dotnet.microsoft.com/en-us/download/dotnet/6.0.
• Incorrect application pool setting:

• Open the Application Pools area on IIS.
• Right click on the Application Pool used for your backend and open Basic Settings.
• Select “No Managed Code” for the “.NET CLR Version” value.

4. “Network Error” error:

• Make sure you enter the correct URL in Configuration Manager - Backend URL field when publishing your application.
• For Backend URL change after Publish:
  • Press F12 and open the Developer Tool to see which Backend URL the Frontend is requesting.
  • Switch to the Network area. Check the URL from the header field in failed requests.
  • If you notice that the frontend is not accessing the backend URL correctly, go to the frontend folder on your computer.
  • Edit the “ENV_TEST” section in the env-config.js file by entering BACKEND_URL: “https://the domain name you want/v1/api” and the swagger URL directory.
  • Go back to IIS. Restart the frontend's application pool.

If it still does not go to the correct URL, make sure that the updates made on the browser are reflected by performing Cache Cleanup.