Connect:Direct® Web Services Troubleshooting
Use the following table to help troubleshoot problems with Connect:Direct Web Services:
Problem | Possible Cause | Solution |
---|---|---|
Connect:Direct Web Console fails to load | Cookies disabled in your browser settings and/or browser's local storage is persistent. | Enable browser cookie, local storage, clear the cache, and reload the page. |
Web Services Database service cannot be reached or a Jedis connection could not be established with the database. | Failed Redis connection |
|
Upgrade fails |
A previous attempt to uninstall Connect:Direct version was unsuccessful. |
Cleanup the registry settings in the .com.zero.registry.xml:
|
Connect:Direct Web Console fails to load | Web Services is not accessible | Ensure firewall rules have been added for inbound and outbound connections between Web Services and Connect Direct Server. Firewall rules must allow inbound connections to the specified Web Services port. Connect Direct server must also have its API port open for web service. |
Connect:Direct Web Services is not accessible | A network or firewall restriction | Ensure firewall rules are added on all the machines hosting Connect:Direct server(s). |
There are no nodes visible under the User Function tab in the Web Console | The Web Console could be experiencing delay in loading the nodes. If the problem persists, it could be because the Connect:Direct Web Services/Redis database service has stopped. | Attempt to stop and start the Redis and Web Services. |
Connect:Direct server stops with the following error message:
CD
server is in stop state . |
|
Ensure that the Connect:Direct Server is running and verify:
|
Web Admin user account is locked. |
|
Execute the Password Reset utility,
ResetDefaultCDWSAdminPassword . For more information see, Password Reset for a Web Administrator. |
Certificate-based authentication fails | This possibly occurred due to domain name and the Subject Alternative Name (SAN) or common name mismatch of the SSL certificate. |
|
Reference to PostgreSQL database may remain in the Registry after Connect:Direct Web Services for Windows is successfully uninstalled. |
|
|
All services were up and running but unable to access Connect:Direct Web Console. | This possibly occurred due to firewall settings. The settings are blocking connection attempts to Web services application. | Contact your system administrator. |
RESTful APIs logs display the following
error:
org.postgresql.util |
This issue occurs when you execute the PostgreSQL password reset procedures for Connect:Direct Web Services running zLinux and AIX platforms. |
|
Reset PostgreSQL Database using old password. | Follow Reset PostgreSQL Database connection password procedure using old password described here, PostgreSQL database Password management. | |
Change PostgreSQL Database in case of forgotten password | Follow Reset PostgreSQL database connection in case of forgotten password described here, PostgreSQL database Password management. |