While working with the application you may sometimes encounter issues such as misaligned elements, application not opening on a particular browser, abrupt dynamic behavior of the page, etc. These are client-side UI issues that you can try to troubleshoot by following the instruction given in the section that follows.
Server-side issues typically occur when the server either returns an erroneous response or doesn't respond at all to a request. There's a dedicated section on this page that helps troubleshoot the server-side UI issues.
The section to follow also discusses some common UI issues you may come across while working with the application.
Client-side UI issues
A component is not rendering properly on the browser.
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 1 | Browser cache may not be working properly. | Clear the browser cache then retry again. | If not solved, follow the step 2. |
| 2 | The browser or its version is not supported. | Try to open in a different version of the same browser, or in another browser altogether. | If it is working fine, get the browser name and version on which it not working so that developer can debug it. |
| 3 | It may be a JavaScript issue. | A developer can debug such an error. | On the top-right corner, click the icon  , and then More tools > Developer tools > Console, and download the Console logs. This log would help Adeptia Connect debug the error. |
Server-side UI issues
HTTP request fails.
You can troubleshoot the server-side UI issues by investigating the HTTP status codes, Headers details, and the Response returned by the server.
If server is not responding to your request, for example, you're unable to create a Template, you would need to go to the browser's More tools > Developer tools >Network. On this page, you'll find the URLs and their status codes under Status column, which would help you diagnose or fix the issue.
HTTP Status Code | Possible reason(s) | Possible solution(s) | Remarks |
400 (Bad Request) | Your request path parameters or query parameters may not be valid. | Check the query and path parameters of your request. | For more details, you need to check your Webrunner logs. |
401 (Unauthorized) | - User session may have expired on the Connect Server either because you have been idle for a long time or the Webrunner has restarted.
- JWT token may have expired or you may have been idle for log time on the Connect Portal.
| Collect the Webrunner logs and provide it to Adeptia Connect for debugging the error. | For more details need to get the the Webrunner logs. |
403 (Forbidden) | You may not have the access to the resource or action in context. | Check if the role assigned to you has the required permissions. | For more details need to check the Webrunner logs. |
404 (Not Found) | The requested resource (image/CSS/JavaScript/HTML) may not be available or couldn't be found on the server. | Check if: - The Application(Portal /Server) is deployed properly or not.
- Patch has been applied properly on the Connect Server or not. Also check if you've performed the post deployment steps (if any) or not .
- Patch has been applied properly on the Connect Portal or not. Also check if every Connect Portal component has its own folders in "../ConnectPortal/webapps/wars” folder.
|
|
500 (Internal Server Error) | An error may have occurred on the Connect Server. | - Collect the Webrunner logs and provide it to Adeptia Connect for debugging the error.
- Download the HAR file, and provide it to Adeptia Connect for debugging the error.
|
|
502 (Bad Gateway) | The Proxy/Load Balancer/Gateway may not be able to handle the response. | Check and correct the Load Balancer/Proxy/Gateway configuration. |
|
503 (Service Unavailable) | You may not have installed Adeptia Connect properly, and the Connect Server may not be ready to handle any request. | Check if: - The application(Portal /Server) is deployed properly or not.
- Patch has been applied properly on the Connect Server or not. Also check if you've performed the post deployment steps (if any) or not.
- Patch has been applied properly on the Connect Portal or not. Also check if every Connect Portal component has its own folders in "../ConnectPortal/webapps/wars” folder.
- The Webrunner and Portal logs have any relevant information.
|
|
504 (Gateway Timeout) | The Connect Server/Portal may not be able to respond within the stipulated time interval configured in the Proxy/Load Balancer/Gateway. | Increase the request time-out value in Load Balancer/Proxy/Gateway configuration. |
|
- You can also get detailed information about the issue by clicking a URL – this takes you to Headers tab wherein you can find if there's a problem with any of the following headers.
- General
- Response Headers
- Request Headers
- Request Payload (if the used method is PUT or POST)
Expand each of the headers to see and verify the details. You can also export these details to an HAR file and send it to a developer to analyze and fix the issue. Refer to this page to know how to export or save the details to an HAR file.
- To see if there's a problem with the response, go to the Response tab.
Common UI issues
This section discusses some common UI issues you may come across while working with the application.
Connect Server and Portal are running, but the Portal UI is inaccessible.
- Check if the URL (app.adeptia.host.url) of the Connect Server is mentioned correctly in the application.properties file located at the Connect Portal.
- In case you're using HTTPS scheme, you need to check if the certificates are configured properly as per the deployment guidelines.
Connect Portal is accessible, but Connect Server UI is not accessible.
Check if the Kernel is running or not. You can check the Kernel status from the system console (Portal).
Some of the services (eg: file target) are not visible in Connect UI at configure page.
Check if your Adeptia Connect license supports the service. You can check the supported services in your license details at System Console > Report > License >Details >View > BASE SERVICES /ADD-ON COMPONENTS.
Unable to access any other web components such as Web PD, Schema Builder, etc.
Check if the WAR file of the corresponding component is deployed correctly or not. You can check the WAR files of the respective components at the location .../ConnectPortal/webapps/wars
