Troubleshoot Your Clients
Troubleshoot All Clients
"403 Forbidden Error" When a Client Attempts to Connect to the Gateway
Cause: A "403 Forbidden" error displays in the log after launching the Gateway and a client attempts to connect to it. This error can happen if the realm-name
element for a service is set, but the authorization-constraint
element for the same service is not properly configured in the Gateway configuration.
Solution: A service protected by user authentication and authorization must have both the realm and authorization-constraint configured. See the documentation for realm-name
and authorization-constraint
. Alternatively, if you do not want to configure security on the service, you can omit or comment out both the realm-name
and authorization-constraint
elements from the service.
Troubleshoot Specific Clients
The following topics describe how to troubleshoot clients built using the Kaazing WebSocket Gateway Client APIs:
Client Platform | Troubleshooting and Logging Resources |
---|---|
JavaScript | Display Logs for the JavaScript Client |
Objective-C | Troubleshoot Your Objective-C Client Display Logs for the Objective-C Client |
Android | Display Logs for the Android Client |
Flash | Troubleshoot Your Flash Client Display Logs for the Flash Client |
.NET and Silverlight | Troubleshoot Your Microsoft .NET and Silverlight Clients Display Logs for .NET and Silverlight Clients |
Java | Troubleshoot Your Java Client Display Logs for the Java Client |
Google Web Toolkit | Google Web Toolkit: Troubleshooting |
Also, see Checklist: Troubleshoot Kaazing WebSocket Gateway for troubleshooting help with your configuration, clusters, and security.