Internal connection errors are described here:

CodeNameDescription
0SUCCESS

The operation succeeded. No error.

256UNSUPPORTED

The requested operation is unsupported.

512SERVER_ERROR

An internal error occurred, and the operation could not be performed.

513SERVER_BUSY

The operation could not be performed because the server is busy.

514UPSTREAM_TIMEOUT

The upstream server is not responding. In most cases, the upstream server is the remote desktop server.

515UPSTREAM_ERROR

The upstream server encountered an error. In most cases, the upstream server is the remote desktop server.

516RESOURCE_NOT_FOUND

An associated resource, such as a file or stream, could not be found, and thus the operation failed.

517RESOURCE_CONFLICT

A resource is already in use or locked, preventing the requested operation.

518RESOURCE_CLOSED

The requested operation cannot continue because the associated resource has been closed.

519UPSTREAM_NOT_FOUND

Authentication error.

520UPSTREAM_UNAVAILABLE

The upstream server is refusing to service connections. In most cases, the upstream server is the remote desktop server.

521SESSION_CONFLICT

The session within the upstream server has ended because it conflicts with another session. In most cases, the upstream server is the remote desktop server.

522SESSION_TIMEOUT

The session within the upstream server has ended because it appeared to be inactive. In most cases, the upstream server is the remote desktop server.

523SESSION_CLOSED

The session within the upstream server has been forcibly closed. In most cases, the upstream server is the remote desktop server.

768CLIENT_BAD_REQUEST

The parameters of the request are illegal or otherwise invalid.

769CLIENT_UNAUTHORIZED

Permission was denied, because the user is not logged in. Note that the user may be logged into Guacamole, but still not logged in with respect to the remote desktop server.

771CLIENT_FORBIDDEN

Permission was denied, and logging in will not solve the problem.

776CLIENT_TIMEOUT

The client (usually the user of Guacamole or their browser) is taking too long to respond.

781CLIENT_OVERRUN

The client has sent more data than the protocol allows.

783CLIENT_BAD_TYPE

The client has sent data of an unexpected or illegal type.

797CLIENT_TOO_MANY

The client is already using too many resources. Existing resources must be freed before further requests are allowed.