| |
| <!DOCTYPE html> |
| |
| |
| <html lang="en" data-content_root="./" > |
| |
| <head> |
| <meta charset="utf-8" /> |
| <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" /> |
| |
| <title>Troubleshooting — Apache Guacamole Manual v1.6.0</title> |
| |
| |
| |
| <script data-cfasync="false"> |
| document.documentElement.dataset.mode = localStorage.getItem("mode") || ""; |
| document.documentElement.dataset.theme = localStorage.getItem("theme") || ""; |
| </script> |
| |
| <!-- Loaded before other Sphinx assets --> |
| <link href="_static/styles/theme.css?digest=dfe6caa3a7d634c4db9b" rel="stylesheet" /> |
| <link href="_static/styles/bootstrap.css?digest=dfe6caa3a7d634c4db9b" rel="stylesheet" /> |
| <link href="_static/styles/pydata-sphinx-theme.css?digest=dfe6caa3a7d634c4db9b" rel="stylesheet" /> |
| |
| |
| <link href="_static/vendor/fontawesome/6.5.2/css/all.min.css?digest=dfe6caa3a7d634c4db9b" rel="stylesheet" /> |
| <link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.2/webfonts/fa-solid-900.woff2" /> |
| <link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.2/webfonts/fa-brands-400.woff2" /> |
| <link rel="preload" as="font" type="font/woff2" crossorigin href="_static/vendor/fontawesome/6.5.2/webfonts/fa-regular-400.woff2" /> |
| |
| <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=8f2a1f02" /> |
| <link rel="stylesheet" type="text/css" href="_static/styles/sphinx-book-theme.css?v=eba8b062" /> |
| <link rel="stylesheet" type="text/css" href="_static/copybutton.css?v=76b2166b" /> |
| <link rel="stylesheet" type="text/css" href="_static/tabs.css?v=4c969af8" /> |
| <link rel="stylesheet" type="text/css" href="_static/gug.css?v=475feb7f" /> |
| |
| <!-- Pre-loaded scripts that we'll load fully later --> |
| <link rel="preload" as="script" href="_static/scripts/bootstrap.js?digest=dfe6caa3a7d634c4db9b" /> |
| <link rel="preload" as="script" href="_static/scripts/pydata-sphinx-theme.js?digest=dfe6caa3a7d634c4db9b" /> |
| <script src="_static/vendor/fontawesome/6.5.2/js/all.min.js?digest=dfe6caa3a7d634c4db9b"></script> |
| |
| <script src="_static/documentation_options.js?v=9eb32ce0"></script> |
| <script src="_static/doctools.js?v=9bcbadda"></script> |
| <script src="_static/sphinx_highlight.js?v=dc90522c"></script> |
| <script src="_static/clipboard.min.js?v=a7894cd8"></script> |
| <script src="_static/copybutton.js?v=c136e461"></script> |
| <script src="_static/tabs.js?v=3ee01567"></script> |
| <script src="_static/scripts/sphinx-book-theme.js?v=887ef09a"></script> |
| <script>DOCUMENTATION_OPTIONS.pagename = 'troubleshooting';</script> |
| <link rel="index" title="Index" href="genindex.html" /> |
| <link rel="search" title="Search" href="search.html" /> |
| <link rel="next" title="LDAP authentication" href="ldap-auth.html" /> |
| <link rel="prev" title="Importing connections from CSV, JSON, or YAML" href="batch-import.html" /> |
| <meta name="viewport" content="width=device-width, initial-scale=1"/> |
| <meta name="docsearch:language" content="en"/> |
| </head> |
| |
| |
| <body data-bs-spy="scroll" data-bs-target=".bd-toc-nav" data-offset="180" data-bs-root-margin="0px 0px -60%" data-default-mode=""> |
| |
| |
| |
| <div id="pst-skip-link" class="skip-link d-print-none"><a href="#main-content">Skip to main content</a></div> |
| |
| <div id="pst-scroll-pixel-helper"></div> |
| |
| <button type="button" class="btn rounded-pill" id="pst-back-to-top"> |
| <i class="fa-solid fa-arrow-up"></i>Back to top</button> |
| |
| |
| <input type="checkbox" |
| class="sidebar-toggle" |
| id="pst-primary-sidebar-checkbox"/> |
| <label class="overlay overlay-primary" for="pst-primary-sidebar-checkbox"></label> |
| |
| <input type="checkbox" |
| class="sidebar-toggle" |
| id="pst-secondary-sidebar-checkbox"/> |
| <label class="overlay overlay-secondary" for="pst-secondary-sidebar-checkbox"></label> |
| |
| <div class="search-button__wrapper"> |
| <div class="search-button__overlay"></div> |
| <div class="search-button__search-container"> |
| <form class="bd-search d-flex align-items-center" |
| action="search.html" |
| method="get"> |
| <i class="fa-solid fa-magnifying-glass"></i> |
| <input type="search" |
| class="form-control" |
| name="q" |
| id="search-input" |
| placeholder="Search..." |
| aria-label="Search..." |
| autocomplete="off" |
| autocorrect="off" |
| autocapitalize="off" |
| spellcheck="false"/> |
| <span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd>K</kbd></span> |
| </form></div> |
| </div> |
| |
| <div class="pst-async-banner-revealer d-none"> |
| <aside id="bd-header-version-warning" class="d-none d-print-none" aria-label="Version warning"></aside> |
| </div> |
| |
| |
| <header class="bd-header navbar navbar-expand-lg bd-navbar d-print-none"> |
| </header> |
| |
| |
| <div class="bd-container"> |
| <div class="bd-container__inner bd-page-width"> |
| |
| |
| |
| <div class="bd-sidebar-primary bd-sidebar"> |
| |
| |
| |
| <div class="sidebar-header-items sidebar-primary__section"> |
| |
| |
| |
| |
| </div> |
| |
| <div class="sidebar-primary-items__start sidebar-primary__section"> |
| <div class="sidebar-primary-item"> |
| |
| |
| |
| |
| |
| <a class="navbar-brand logo" href="index.html"> |
| |
| |
| |
| |
| |
| |
| <p class="title logo__title">Apache Guacamole Manual v1.6.0</p> |
| |
| </a></div> |
| <div class="sidebar-primary-item"> |
| |
| <script> |
| document.write(` |
| <button class="btn search-button-field search-button__button" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip"> |
| <i class="fa-solid fa-magnifying-glass"></i> |
| <span class="search-button__default-text">Search</span> |
| <span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd class="kbd-shortcut__modifier">K</kbd></span> |
| </button> |
| `); |
| </script></div> |
| <div class="sidebar-primary-item"><nav class="bd-links bd-docs-nav" aria-label="Main"> |
| <div class="bd-toc-item navbar-nav active"> |
| <p aria-level="2" class="caption" role="heading"><span class="caption-text">Getting Started</span></p> |
| <ul class="nav bd-sidenav"> |
| <li class="toctree-l1"><a class="reference internal" href="introduction.html">Introduction</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="guacamole-architecture.html">Implementation and architecture</a></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="installing-guacamole.html">Installing Guacamole</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="guacamole-native.html">Native installation</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="guacamole-docker.html">Containerized (Docker) installation</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="jdbc-auth.html">Database setup</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="mysql-auth.html">MariaDB / MySQL</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="postgresql-auth.html">PostgreSQL</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="sqlserver-auth.html">SQL Server</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="security.html">Securing a Guacamole install</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="reverse-proxy.html">SSL termination</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="auth-ban.html">Blocking brute-force attacks</a></li> |
| </ul> |
| </details></li> |
| </ul> |
| <p aria-level="2" class="caption" role="heading"><span class="caption-text">Using Guacamole</span></p> |
| <ul class="current nav bd-sidenav"> |
| <li class="toctree-l1"><a class="reference internal" href="configuring-guacamole.html">Configuration</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="using-guacamole.html">General usage</a></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="administration.html">Administration</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="batch-import.html">Importing connections</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1 current active"><a class="current reference internal" href="#">Troubleshooting</a></li> |
| </ul> |
| <p aria-level="2" class="caption" role="heading"><span class="caption-text">Extensions</span></p> |
| <ul class="nav bd-sidenav"> |
| <li class="toctree-l1"><a class="reference internal" href="ldap-auth.html">Active Directory / LDAP</a></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="mfa.html">Multi-factor authentication</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="duo-auth.html">Duo</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="totp-auth.html">TOTP</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="sso.html">Single sign-on</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="cas-auth.html">CAS</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="openid-auth.html">OpenID Connect</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="saml-auth.html">SAML</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="ssl-auth.html">Smart cards / Certificates</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1"><a class="reference internal" href="vault.html">Retrieving secrets from a vault</a></li> |
| <li class="toctree-l1 has-children"><a class="reference internal" href="external-auth.html">External authentication</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul> |
| <li class="toctree-l2"><a class="reference internal" href="json-auth.html">Encrypted, signed JSON</a></li> |
| <li class="toctree-l2"><a class="reference internal" href="header-auth.html">HTTP header</a></li> |
| </ul> |
| </details></li> |
| <li class="toctree-l1"><a class="reference internal" href="radius-auth.html">RADIUS</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="adhoc-connections.html">Ad-hoc connections</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="auth-restrict.html">Login / Connection restrictions</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="recording-playback.html">Session recording player</a></li> |
| </ul> |
| <p aria-level="2" class="caption" role="heading"><span class="caption-text">Developer's Guide</span></p> |
| <ul class="nav bd-sidenav"> |
| <li class="toctree-l1"><a class="reference internal" href="guacamole-protocol.html">The Guacamole protocol</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="libguac.html">libguac</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="guacamole-common.html">guacamole-common</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="guacamole-common-js.html">guacamole-common-js</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="guacamole-ext.html">guacamole-ext</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="custom-protocols.html">Adding new protocols</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="custom-auth.html">Custom authentication</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="event-listeners.html">Event listeners</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="writing-you-own-guacamole-app.html">Writing your own Guacamole application</a></li> |
| </ul> |
| <p aria-level="2" class="caption" role="heading"><span class="caption-text">Appendices</span></p> |
| <ul class="nav bd-sidenav"> |
| <li class="toctree-l1"><a class="reference internal" href="protocol-reference.html">Guacamole protocol reference</a></li> |
| <li class="toctree-l1"><a class="reference internal" href="jdbc-auth-schema.html">Database schema reference</a></li> |
| </ul> |
| |
| </div> |
| </nav></div> |
| </div> |
| |
| |
| <div class="sidebar-primary-items__end sidebar-primary__section"> |
| </div> |
| |
| <div id="rtd-footer-container"></div> |
| |
| |
| </div> |
| |
| <main id="main-content" class="bd-main" role="main"> |
| |
| |
| |
| <div class="sbt-scroll-pixel-helper"></div> |
| |
| <div class="bd-content"> |
| <div class="bd-article-container"> |
| |
| <div class="bd-header-article d-print-none"> |
| <div class="header-article-items header-article__inner"> |
| |
| <div class="header-article-items__start"> |
| |
| <div class="header-article-item"><button class="sidebar-toggle primary-toggle btn btn-sm" title="Toggle primary sidebar" data-bs-placement="bottom" data-bs-toggle="tooltip"> |
| <span class="fa-solid fa-bars"></span> |
| </button></div> |
| |
| </div> |
| |
| |
| <div class="header-article-items__end"> |
| |
| <div class="header-article-item"> |
| |
| <div class="article-header-buttons"> |
| |
| |
| |
| <button onclick="toggleFullScreen()" |
| class="btn btn-sm btn-fullscreen-button" |
| title="Fullscreen mode" |
| data-bs-placement="bottom" data-bs-toggle="tooltip" |
| > |
| |
| |
| <span class="btn__icon-container"> |
| <i class="fas fa-expand"></i> |
| </span> |
| |
| </button> |
| |
| |
| |
| <script> |
| document.write(` |
| <button class="btn btn-sm nav-link pst-navbar-icon theme-switch-button" title="light/dark" aria-label="light/dark" data-bs-placement="bottom" data-bs-toggle="tooltip"> |
| <i class="theme-switch fa-solid fa-sun fa-lg" data-mode="light"></i> |
| <i class="theme-switch fa-solid fa-moon fa-lg" data-mode="dark"></i> |
| <i class="theme-switch fa-solid fa-circle-half-stroke fa-lg" data-mode="auto"></i> |
| </button> |
| `); |
| </script> |
| |
| |
| <script> |
| document.write(` |
| <button class="btn btn-sm pst-navbar-icon search-button search-button__button" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip"> |
| <i class="fa-solid fa-magnifying-glass fa-lg"></i> |
| </button> |
| `); |
| </script> |
| <button class="sidebar-toggle secondary-toggle btn btn-sm" title="Toggle secondary sidebar" data-bs-placement="bottom" data-bs-toggle="tooltip"> |
| <span class="fa-solid fa-list"></span> |
| </button> |
| </div></div> |
| |
| </div> |
| |
| </div> |
| </div> |
| |
| |
| |
| <div id="jb-print-docs-body" class="onlyprint"> |
| <h1>Troubleshooting</h1> |
| <!-- Table of contents --> |
| <div id="print-main-content"> |
| <div id="jb-print-toc"> |
| |
| <div> |
| <h2> Contents </h2> |
| </div> |
| <nav aria-label="Page"> |
| <ul class="visible nav section-nav flex-column"> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#it-isnt-working">It isn’t working</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#no-graphics-appear">No graphics appear</a></li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#connections-involving-unicode-dont-work">Connections involving Unicode don’t work</a></li> |
| </ul> |
| </li> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#syslog">syslog</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#guacd-errors">guacd errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-bind-socket-to-any-addresses">Unable to bind socket to any addresses.</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-start-input-thread">Unable to start input thread</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#client-finished-abnormally">Client finished abnormally</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-fork-parent">Could not fork() parent</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-change-working-directory-to">Unable to change working directory to /</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-redirect-standard-file-descriptors-to-dev-null">Unable to redirect standard file descriptors to /dev/null</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-parsing-given-address-or-port-hostname">Error parsing given address or port: HOSTNAME</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-opening-socket">Error opening socket</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-resolve-host">Unable to resolve host</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-become-a-daemon">Could not become a daemon</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-write-pid-file">Could not write PID file</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-listen-on-socket">Could not listen on socket</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-accept-client-connection">Could not accept client connection</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-forking-child-process">Error forking child process</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-closing-daemon-reference-to-child-descriptor">Error closing daemon reference to child descriptor</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-sending-sync-instruction">Error sending “sync” instruction</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-flushing-output">Error flushing output</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-handling-server-messages">Error handling server messages</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-reading-instruction">Error reading instruction</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#client-instruction-handler-error">Client instruction handler error</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-reading-opcode">Error reading OPCODE</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-sending-args">Error sending “args”</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-loading-client-plugin">Error loading client plugin</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-instantiating-client">Error instantiating client</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#libguac-client-vnc-errors">libguac-client-vnc errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-waiting-for-vnc-message">Error waiting for VNC message</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-handling-vnc-server-message">Error handling VNC server message</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#wrong-argument-count-received">Wrong argument count received</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#libguac-client-rdp-errors">libguac-client-rdp errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#invalid-parameter">Invalid PARAMETER</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#support-for-the-cliprdr-channel-clipboard-redirection-could-not-be-loaded">Support for the CLIPRDR channel (clipboard redirection) could not be loaded</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#cannot-create-static-channel-name-failed-to-load-guac-common-svc-plugin-for-freerdp">Cannot create static channel “NAME”: failed to load “guac-common-svc” plugin for FreeRDP</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#server-requested-unsupported-clipboard-data-type">Server requested unsupported clipboard data type</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#clipboard-data-missing-null-terminator">Clipboard data missing null terminator</a></li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#servlet-container-logs">Servlet container logs</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#user-mapping-xml-errors"><code class="docutils literal notranslate"><span class="pre">user-mapping.xml</span></code> errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#attribute-name-required-for-connection-tag">Attribute “name” required for connection tag</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#attribute-name-required-for-param-tag">Attribute “name” required for param tag</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unexpected-character-data">Unexpected character data</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#invalid-encoding-type">Invalid encoding type</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#user-mapping-could-not-be-read">User mapping could not be read</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#guacamole-properties-errors"><code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code> errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#property-property-is-required">Property PROPERTY is required</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#authentication-errors">Authentication errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#cannot-connect-user-not-logged-in">Cannot connect - user not logged in</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#requested-configuration-is-not-authorized">Requested configuration is not authorized</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#user-has-no-session">User has no session</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-errors">Tunnel errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-such-tunnel">No such tunnel</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-tunnel-created">No tunnel created</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-query-string-provided">No query string provided</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-reached-end-of-stream">Tunnel reached end of stream</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-is-closed">Tunnel is closed</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#end-of-stream-during-initial-handshake">End of stream during initial handshake</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#element-terminator-of-instruction-was-not-nor">Element terminator of instruction was not ‘;’ nor ‘,’</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#non-numeric-character-in-element-length">Non-numeric character in element length</a></li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </nav> |
| </div> |
| </div> |
| </div> |
| |
| |
| |
| <div id="searchbox"></div> |
| <article class="bd-article"> |
| |
| <section id="troubleshooting"> |
| <h1>Troubleshooting<a class="headerlink" href="#troubleshooting" title="Link to this heading">#</a></h1> |
| <section id="it-isnt-working"> |
| <span id="not-working"></span><h2>It isn’t working<a class="headerlink" href="#it-isnt-working" title="Link to this heading">#</a></h2> |
| <p>If Guacamole isn’t working, chances are something isn’t configured properly, or |
| something is wrong with the network. Thankfully, Guacamole and all its |
| components log errors thoroughly, so the problem can usually be traced down |
| fairly easily if you know where to look. Troubleshooting Guacamole usually |
| boils down to checking either syslog or your servlet container’s logs (likely |
| Tomcat).</p> |
| <p>Failing all that, you can always post a question on <a class="reference external" href="http://guacamole.apache.org/support/#mailing-lists">one of the project mailing |
| lists</a>, or if you truly |
| feel you’ve discovered a bug, you can <a class="reference external" href="https://issues.apache.org/jira/browse/GUACAMOLE/">create a new ticket in |
| JIRA</a>. Beware that if |
| something isn’t working, and there are errors in the logs describing the |
| problem, <a class="reference external" href="http://guacamole.apache.org/faq/#probably-not-a-bug">it is usually not a |
| bug</a>, and the best place |
| to handle such things is through consulting this guide or the mailing lists.</p> |
| <section id="no-graphics-appear"> |
| <h3>No graphics appear<a class="headerlink" href="#no-graphics-appear" title="Link to this heading">#</a></h3> |
| <p>If you <em>never</em> see any graphics appear, or you see “Connecting, waiting for |
| first update…” for a while and then are disconnected, the most likely cause |
| is a proxy.</p> |
| <p>Guacamole relies on streaming data to you over a persistent connection. If |
| software between Guacamole and your browser is buffering all incoming data, |
| such as a proxy, this data never makes it to your browser, and you will just |
| see it wait indefinitely. Eventually, thinking the client has disconnected, |
| Guacamole closes the connection, at which point the proxy finally flushes its |
| buffer and you see graphics! … just in time to see it disconnect.</p> |
| <p>The solution here is to either modify your proxy settings to flush packets |
| immediately as they are received, or to use HTTPS. Proxies are required to pass |
| HTTPS through untouched, and this usually solves the problem.</p> |
| <p>Even if you aren’t aware of any proxy, there may be one in place. Corporate |
| firewalls very often incorporate proxies. Antivirus software may buffer |
| incoming data until the connection is closed and the data is scanned for |
| viruses. Virtualization software may detect HTTP data and buffer the connection |
| just like a proxy. If all else fails, try HTTPS - it’s the only secure way to |
| do this anyway.</p> |
| </section> |
| <section id="connections-involving-unicode-dont-work"> |
| <h3>Connections involving Unicode don’t work<a class="headerlink" href="#connections-involving-unicode-dont-work" title="Link to this heading">#</a></h3> |
| <p>If you are using Tomcat, beware that you <em>must</em> set the <code class="docutils literal notranslate"><span class="pre">URIEncoding="UTF-8"</span></code> |
| attribute on all connectors in your <code class="docutils literal notranslate"><span class="pre">server.xml</span></code>. If you are using a different |
| servlet container, you need to find out whether it requires special options to |
| support UTF-8 in URIs, and change the required settings to enable such support.</p> |
| <p>Without UTF-8 support enabled for URIs, Unicode characters in connection names |
| will not be received properly when connecting, and Guacamole will think the |
| connection you requested does not exist. Similarly, if you are using the |
| built-in administration interface, parameters involving Unicode characters will |
| not save properly without these options enabled.</p> |
| </section> |
| </section> |
| <section id="syslog"> |
| <h2>syslog<a class="headerlink" href="#syslog" title="Link to this heading">#</a></h2> |
| <p>guacd and libguac-based programs (such as all client plugins) log informational |
| messages and errors to syslog. Specifically, guacd uses syslog, and it exposes |
| this logging facility to everything it loads (client plugins), thus if the VNC |
| or RDP support plugins encounter errors, they log those errors over the logging |
| facilities exposed by guacd, in this case syslog.</p> |
| <p>Once you guacd is started, you’ll see entries like the following in syslog:</p> |
| <div class="highlight-none notranslate"><div class="highlight"><pre><span></span>guacd[19663]: Guacamole proxy daemon (guacd) version 0.7.0 |
| guacd[19663]: Unable to bind socket to host ::1, port 4823: Address family |
| not supported by protocol |
| guacd[19663]: Successfully bound socket to host 127.0.0.1, port 4823 |
| guacd[19663]: Exiting and passing control to PID 19665 |
| guacd[19665]: Exiting and passing control to PID 19666 |
| guacd[19666]: Listening on host 127.0.0.1, port 4823 |
| </pre></div> |
| </div> |
| <p>Each entry relevant to Guacamole has the prefix “guacd”, denoting the program |
| that produced the entry, followed by the process ID, followed by the message. |
| The entries above show guacamole starting successfully and listening on a |
| non-default port 4823.</p> |
| <section id="guacd-errors"> |
| <h3>guacd errors<a class="headerlink" href="#guacd-errors" title="Link to this heading">#</a></h3> |
| <section id="unable-to-bind-socket-to-any-addresses"> |
| <h4>Unable to bind socket to any addresses.<a class="headerlink" href="#unable-to-bind-socket-to-any-addresses" title="Link to this heading">#</a></h4> |
| <p>This means that guacd failed to start up at all because the port it wants to |
| listen on is already taken at all addresses attempted. The details of what |
| guacd tried will be listed in the log entries above this. To solve the problem, |
| find what port guacd was trying to listen on (the default is 4822) and check if |
| any other service is listening on that port.</p> |
| <p>If another service is listening on the default port, you can always specify a |
| non-standard port for guacd by using the <code class="docutils literal notranslate"><span class="pre">-l</span> <span class="pre">PORT</span></code> option (that’s a lowercase |
| “L”, not a number “1”), where <PORT> is the number of the port to listen on. |
| Beware that you will likely have to modify <code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code> so that |
| Guacamole knows how to connect to guacd.</p> |
| </section> |
| <section id="unable-to-start-input-thread"> |
| <h4>Unable to start input thread<a class="headerlink" href="#unable-to-start-input-thread" title="Link to this heading">#</a></h4> |
| <p>guacd creates two threads for each connection: one that receives input from the |
| connected client, and the other that produces output for the client. If either |
| of these fails to start, the above error will be logged along with the cause.</p> |
| <p>If it is the output thread that fails to start, the message will instead read: |
| “Unable to start output thread”.</p> |
| </section> |
| <section id="client-finished-abnormally"> |
| <h4>Client finished abnormally<a class="headerlink" href="#client-finished-abnormally" title="Link to this heading">#</a></h4> |
| <p>If the client plugin ever returns an error code, this will cause the connection |
| to immediately terminate, with the cause of the error specific to the plugin in |
| use. The cause should be detailed in the log messages above the error. If those |
| log messages don’t make sense, you may have found a bug.</p> |
| </section> |
| <section id="could-not-fork-parent"> |
| <h4>Could not fork() parent<a class="headerlink" href="#could-not-fork-parent" title="Link to this heading">#</a></h4> |
| <p>When guacd starts up, it immediately attempts to “fork” into the background |
| (unless instructed otherwise). The word “fork()” above is a reference to the C |
| function call that does this. There are several calls to this function, each of |
| which might fail if system resources are lacking or something went wrong at a |
| low level. If you see this message, it is probably not a bug in Guacamole, but |
| rather a problem with the load level of your system.</p> |
| <p>This message may also appear as “Could not fork() group leader”.</p> |
| </section> |
| <section id="unable-to-change-working-directory-to"> |
| <h4>Unable to change working directory to /<a class="headerlink" href="#unable-to-change-working-directory-to" title="Link to this heading">#</a></h4> |
| <p>One of the duties of guacd as it starts up is to change its working directory |
| to the root directory. This is to prevent locking the current directory in case |
| it needs to be unmounted, etc. If guacd cannot do this, this error will be |
| logged, along with the cause.</p> |
| </section> |
| <section id="unable-to-redirect-standard-file-descriptors-to-dev-null"> |
| <h4>Unable to redirect standard file descriptors to /dev/null<a class="headerlink" href="#unable-to-redirect-standard-file-descriptors-to-dev-null" title="Link to this heading">#</a></h4> |
| <p>As guacd starts, it also has to redirect STDOUT, STDERR, and STDIN to |
| <code class="docutils literal notranslate"><span class="pre">/dev/null</span></code> such that attempts to use these output mechanisms do not pollute |
| the active console. Though guacd and client plugins will use the exposed |
| logging facilities (and thus syslog) rather than STDOUT or STDERR, libraries |
| used by client plugins are often written only from the mindset of a typical |
| client, and use standard output mechanisms for debug logging. Not redirecting |
| these would result in undesired output to the console.</p> |
| <p>If guacd cannot redirect these file descriptors for any reason, this error will |
| be logged, along with the cause.</p> |
| </section> |
| <section id="error-parsing-given-address-or-port-hostname"> |
| <h4>Error parsing given address or port: HOSTNAME<a class="headerlink" href="#error-parsing-given-address-or-port-hostname" title="Link to this heading">#</a></h4> |
| <p>If you specified a host or port to listen on via commandline options, and that |
| host or port is actually invalid, you will see this error. Fix the |
| corresponding option and try again.</p> |
| </section> |
| <section id="error-opening-socket"> |
| <h4>Error opening socket<a class="headerlink" href="#error-opening-socket" title="Link to this heading">#</a></h4> |
| <p>When guacd starts up, it needs to open a socket and then listen on that socket. |
| If it can’t even open the socket, this error will be logged, and guacd will |
| exit. The cause is most likely related to permissions, and is logged along with |
| the error.</p> |
| </section> |
| <section id="unable-to-resolve-host"> |
| <h4>Unable to resolve host<a class="headerlink" href="#unable-to-resolve-host" title="Link to this heading">#</a></h4> |
| <p>If the hostname you specified on the commandline cannot be found, you will see |
| this error. Note that this error is from guacd, and does not relate to whatever |
| remote desktop servers you may be trying to use; it relates only to the host |
| guacd is trying to listen on. Check the hostname or IP address specified on the |
| commandline. If that checks out, there may be a problem with your DNS or your |
| network.</p> |
| </section> |
| <section id="could-not-become-a-daemon"> |
| <h4>Could not become a daemon<a class="headerlink" href="#could-not-become-a-daemon" title="Link to this heading">#</a></h4> |
| <p>In order to become a “daemon” (that is, in order to run in the background as a |
| system process), guacd must create and exit from several processes, redirect |
| file descriptors, etc. If any of these steps fails, guacd will not become a |
| daemon, and it will log this message and exit. The reason guacd could not |
| become a daemon will be in the previous error message in the logs.</p> |
| </section> |
| <section id="could-not-write-pid-file"> |
| <h4>Could not write PID file<a class="headerlink" href="#could-not-write-pid-file" title="Link to this heading">#</a></h4> |
| <p>guacd offers a commandline option that lets you specify a file that it should |
| write its process ID into, which is useful for init scripts. If you see this |
| error, it likely means the user guacd is running as does not have permission to |
| write this file. The true cause of the error will be logged in the same entry. |
| Check which user guacd is running as, and then check that it has write |
| permission to the file in question.</p> |
| </section> |
| <section id="could-not-listen-on-socket"> |
| <h4>Could not listen on socket<a class="headerlink" href="#could-not-listen-on-socket" title="Link to this heading">#</a></h4> |
| <p>When guacd starts up, it needs to listen on the socket it just opened in order |
| to accept connections. If it cannot listen on the socket, clients will be |
| unable to connect. If, for any reason, guacd is unable to listen on the socket, |
| guacd will exit and log this message along with the cause, which is most likely |
| a low-level system resource problem.</p> |
| </section> |
| <section id="could-not-accept-client-connection"> |
| <h4>Could not accept client connection<a class="headerlink" href="#could-not-accept-client-connection" title="Link to this heading">#</a></h4> |
| <p>When a client connects to guacd, it must accept the connection in order for |
| communication to ensue. If it cannot even accept the connection, no |
| communication between server and client will happen, and this error will be |
| logged. The cause of the error will be logged in the same entry. Possible |
| causes include permissions problems, or lack of server resources.</p> |
| </section> |
| <section id="error-forking-child-process"> |
| <h4>Error forking child process<a class="headerlink" href="#error-forking-child-process" title="Link to this heading">#</a></h4> |
| <p>When a client connects to guacd, it must create a new process to handle the |
| connection while the old guacd process continues to listen for new connections. |
| If, for any reason, guacd cannot create this process, the connection from that |
| client will be denied, and the cause of the error will be logged. Possible |
| causes include permissions problems, or lack of server resources.</p> |
| </section> |
| <section id="error-closing-daemon-reference-to-child-descriptor"> |
| <h4>Error closing daemon reference to child descriptor<a class="headerlink" href="#error-closing-daemon-reference-to-child-descriptor" title="Link to this heading">#</a></h4> |
| <p>When guacd receives a connection, and it creates a new process to handle that |
| connection, it gains a copy of the file descriptor that the client will use for |
| communication. As this connection can never be closed unless all references to |
| the descriptor are closed, the server must close its copy such that the client |
| is the only remaining holder of the file descriptor. If the server cannot close |
| the descriptor, it will log this error message along with the cause.</p> |
| </section> |
| <section id="error-sending-sync-instruction"> |
| <h4>Error sending “sync” instruction<a class="headerlink" href="#error-sending-sync-instruction" title="Link to this heading">#</a></h4> |
| <p>During the course of a Guacamole session, guacd must occasionally “ping” the |
| client to make sure it is still alive. This ping takes the form of a “sync” |
| instruction, which the client is obligated to respond to as soon as it is |
| received. If guacd cannot send this instruction, this error will be logged, |
| along with the cause. Chances are the connection has simply been closed, and |
| this error can be ignored.</p> |
| </section> |
| <section id="error-flushing-output"> |
| <h4>Error flushing output<a class="headerlink" href="#error-flushing-output" title="Link to this heading">#</a></h4> |
| <p>After the client plugin is finished (for the time being) with handling server |
| messages, the socket is automatically flushed. If the server cannot flush this |
| socket for some reason, such as the connection already being closed, you will |
| see this error. Normally, this error does not indicate a problem, but rather |
| that the client has simply closed the connection.</p> |
| </section> |
| <section id="error-handling-server-messages"> |
| <h4>Error handling server messages<a class="headerlink" href="#error-handling-server-messages" title="Link to this heading">#</a></h4> |
| <p>While the client plugin is running, guacd will occasionally ask the plugin to |
| check and handle any messages that it may have received from the server it |
| connected to. If the client plugin fails for some reason while doing this, this |
| error will be logged, and the cause of the error will likely be logged in |
| previous log entries by the client plugin.</p> |
| </section> |
| <section id="error-reading-instruction"> |
| <h4>Error reading instruction<a class="headerlink" href="#error-reading-instruction" title="Link to this heading">#</a></h4> |
| <p>During the course of a Guacamole session, instructions are sent from client to |
| server which are to be handled by the client plugin. If an instruction cannot |
| be read, this error will be logged. Usually this means simply that the |
| connection was closed, but it could also indicate that the version of the |
| client in use is so old that it doesn’t support the current Guacamole protocol |
| at all. If the cause looks like the connection was closed (end of stream |
| reached, etc.), this log entry can be ignored. Otherwise, if the first two |
| numbers of the version numbers of all Guacamole components match, you have |
| probably found a bug.</p> |
| </section> |
| <section id="client-instruction-handler-error"> |
| <h4>Client instruction handler error<a class="headerlink" href="#client-instruction-handler-error" title="Link to this heading">#</a></h4> |
| <p>This error indicates that a client plugin failed inside the handler for a |
| specific instruction. When the server receives instructions from the client, it |
| then invokes specific instruction handlers within the client plugin. In |
| general, this error is not useful to a user or system administrator. If the |
| cause looks benign, such as reaching the end of a stream (the connection |
| closed), it can be ignored as normal. Otherwise, this error can indicate a bug |
| either in the client plugin or in a library used by the client plugin.</p> |
| <p>It can also indicate a problem in the remote desktop server which is causing |
| the client plugin to fail while communicating with it.</p> |
| </section> |
| <section id="error-reading-opcode"> |
| <h4>Error reading OPCODE<a class="headerlink" href="#error-reading-opcode" title="Link to this heading">#</a></h4> |
| <p>During the handshake of the Guacamole protocol, the server expects a very |
| specific sequence of instructions to be received. If the wrong instructions are |
| received, or the connection is abruptly closed during the handshake, the above |
| error will occur.</p> |
| <p>In the case that the cause is the connection closing, this is normal, and |
| probably just means that the client disconnected before the initial handshake |
| completed.</p> |
| <p>If the connection was not closed abruptly, but instead the wrong instruction |
| was received, this could mean either that the connecting client is from an |
| incompatible version of Guacamole (and thus does not know the proper handshake |
| procedure) or you have found a bug. Check whether all installed components came |
| from the same upstream release bundle.</p> |
| </section> |
| <section id="error-sending-args"> |
| <h4>Error sending “args”<a class="headerlink" href="#error-sending-args" title="Link to this heading">#</a></h4> |
| <p>During the handshake of the Guacamole protocol, the server must expose all |
| parameters used by the client plugin via the args instruction. If this cannot |
| be sent, you will see this error in the logs. The cause will be included in the |
| error message, and usually just indicates that the connection was closed during |
| the handshake, and thus the handshake cannot continue.</p> |
| </section> |
| <section id="error-loading-client-plugin"> |
| <h4>Error loading client plugin<a class="headerlink" href="#error-loading-client-plugin" title="Link to this heading">#</a></h4> |
| <p>When the client connects, it sends an instruction to guacd informing it what |
| protocol it wishes to use. If the corresponding client plugin cannot be found |
| or used for any reason, this message will appear in the logs. Normally this |
| indicates that the corresponding client plugin is not actually installed. The |
| cause listed after the error message will indicate whether this is the case.</p> |
| </section> |
| <section id="error-instantiating-client"> |
| <h4>Error instantiating client<a class="headerlink" href="#error-instantiating-client" title="Link to this heading">#</a></h4> |
| <p>After the client plugin is loaded, an initialization function provided by the |
| client plugin is invoked. If this function fails, then the client itself cannot |
| be created, and this error will be logged. Usually this indicates that one or |
| more of the parameters given to the client plugin are incorrect or malformed. |
| Check the configuration of the connection in use at the time.</p> |
| </section> |
| </section> |
| <section id="libguac-client-vnc-errors"> |
| <h3>libguac-client-vnc errors<a class="headerlink" href="#libguac-client-vnc-errors" title="Link to this heading">#</a></h3> |
| <section id="error-waiting-for-vnc-message"> |
| <h4>Error waiting for VNC message<a class="headerlink" href="#error-waiting-for-vnc-message" title="Link to this heading">#</a></h4> |
| <p>The VNC client plugin must wait for messages sent by the VNC server, and handle |
| them when they arrive. If there was an error while waiting for a message from |
| the VNC server, this error message will be displayed. Usually this means that |
| the VNC server closed the connection, or there is a problem with the VNC server |
| itself, but the true cause of the error will be logged.</p> |
| </section> |
| <section id="error-handling-vnc-server-message"> |
| <h4>Error handling VNC server message<a class="headerlink" href="#error-handling-vnc-server-message" title="Link to this heading">#</a></h4> |
| <p>When messages are received from the VNC server, libvncclient must handle them |
| and then invoke the functions of libguac-client-vnc as necessary. If |
| libvncclient fails during the handling of a received message, this error will |
| be logged, along with (hopefully) the cause. This may indicate a problem with |
| the VNC server, or a lack of support within libvncclient.</p> |
| </section> |
| <section id="wrong-argument-count-received"> |
| <h4>Wrong argument count received<a class="headerlink" href="#wrong-argument-count-received" title="Link to this heading">#</a></h4> |
| <p>The connecting client is required to send exactly the same number of arguments |
| as requested by the client plugin. If you see this message, it means there is a |
| bug in the client connecting to guacd, most likely the web application.</p> |
| </section> |
| </section> |
| <section id="libguac-client-rdp-errors"> |
| <h3>libguac-client-rdp errors<a class="headerlink" href="#libguac-client-rdp-errors" title="Link to this heading">#</a></h3> |
| <section id="invalid-parameter"> |
| <h4>Invalid PARAMETER<a class="headerlink" href="#invalid-parameter" title="Link to this heading">#</a></h4> |
| <p>If one of the parameters given, such as “width”, “height”, or “color-depth”, is |
| invalid (not an integer, for example), you will receive this error. Check the |
| parameters of the connection in use and try again.</p> |
| </section> |
| <section id="support-for-the-cliprdr-channel-clipboard-redirection-could-not-be-loaded"> |
| <h4>Support for the CLIPRDR channel (clipboard redirection) could not be loaded<a class="headerlink" href="#support-for-the-cliprdr-channel-clipboard-redirection-could-not-be-loaded" title="Link to this heading">#</a></h4> |
| <p>FreeRDP provides a plugin which provides clipboard support for RDP. This plugin |
| is typically built into FreeRDP, but some distributions may bundle this |
| separately. libguac-client-rdp loads this plugin in order to support clipboard, |
| as well. If this plugin could not be loaded, then clipboard support will not be |
| available, and the reason will be logged.</p> |
| </section> |
| <section id="cannot-create-static-channel-name-failed-to-load-guac-common-svc-plugin-for-freerdp"> |
| <h4>Cannot create static channel “NAME”: failed to load “guac-common-svc” plugin for FreeRDP<a class="headerlink" href="#cannot-create-static-channel-name-failed-to-load-guac-common-svc-plugin-for-freerdp" title="Link to this heading">#</a></h4> |
| <p>RDP provides support for much of its feature set through static virtual |
| channels. Sound support, for example is provided through the “RDPSND” channel. |
| Device redirection for printers and drives is provided through “RDPDR”. To |
| support these and other static virtual channels, libguac-client-rdp builds a |
| plugin for FreeRDP called “guac-common-svc” which allows Guacamole to hook into |
| the parts of FreeRDP that support virtual channels.</p> |
| <p>If libguac-client-rdp cannot load this plugin, support for any features which |
| leverage static virtual channels will not work, and the reason will be logged. |
| A likely explanation is that libguac-client-rdp was built from source, and the |
| directory specified for FreeRDP’s installation location was incorrect. For |
| FreeRDP to be able to find plugins, those plugins must be placed in the |
| <code class="docutils literal notranslate"><span class="pre">freerdp2/</span></code> subdirectory of whichever directory contains the <code class="docutils literal notranslate"><span class="pre">libfreerdp2.so</span></code> |
| library.</p> |
| </section> |
| <section id="server-requested-unsupported-clipboard-data-type"> |
| <h4>Server requested unsupported clipboard data type<a class="headerlink" href="#server-requested-unsupported-clipboard-data-type" title="Link to this heading">#</a></h4> |
| <p>When clipboard support is loaded, libguac-client-rdp informs the RDP server of |
| all supported clipboard data types. The RDP server is required to send only |
| those types supported by the client. If the server decides to send an |
| unsupported type anyway, libguac-client-rdp ignores the data sent, and logs |
| this message.</p> |
| </section> |
| <section id="clipboard-data-missing-null-terminator"> |
| <h4>Clipboard data missing null terminator<a class="headerlink" href="#clipboard-data-missing-null-terminator" title="Link to this heading">#</a></h4> |
| <p>When text is sent via a clipboard message, it is required to have a terminating |
| null byte. If this is not the case, the clipboard data is invalid, and |
| libguac-client-rdp ignores it, logging this error message.</p> |
| </section> |
| </section> |
| </section> |
| <section id="servlet-container-logs"> |
| <h2>Servlet container logs<a class="headerlink" href="#servlet-container-logs" title="Link to this heading">#</a></h2> |
| <p>Your servlet container will have logs which the web application side of |
| Guacamole will log errors to. In the case of Tomcat, this is usually |
| <code class="docutils literal notranslate"><span class="pre">catalina.out</span></code> or <code class="docutils literal notranslate"><span class="pre">HOSTNAME.log</span></code> (for example, <code class="docutils literal notranslate"><span class="pre">localhost.log</span></code>).</p> |
| <section id="user-mapping-xml-errors"> |
| <span id="id1"></span><h3><code class="docutils literal notranslate"><span class="pre">user-mapping.xml</span></code> errors<a class="headerlink" href="#user-mapping-xml-errors" title="Link to this heading">#</a></h3> |
| <p>Errors in the relating to the <code class="docutils literal notranslate"><span class="pre">user-mapping.xml</span></code> file usually indicate that |
| either the XML is malformed, or the file itself cannot be found.</p> |
| <section id="attribute-name-required-for-connection-tag"> |
| <h4>Attribute “name” required for connection tag<a class="headerlink" href="#attribute-name-required-for-connection-tag" title="Link to this heading">#</a></h4> |
| <p>If you specify a connection with a <code class="docutils literal notranslate"><span class="pre"><connection></span></code> tag, it must have a |
| corresponding name set via the <code class="docutils literal notranslate"><span class="pre">name</span></code> attribute. If it does not, then the XML |
| is malformed, and this error will be logged. No users will be able to login.</p> |
| </section> |
| <section id="attribute-name-required-for-param-tag"> |
| <h4>Attribute “name” required for param tag<a class="headerlink" href="#attribute-name-required-for-param-tag" title="Link to this heading">#</a></h4> |
| <p>Each parameter specified with a <code class="docutils literal notranslate"><span class="pre"><param></span></code> tag must have a corresponding name |
| set via the <code class="docutils literal notranslate"><span class="pre">name</span></code> attribute. If it does not, then the XML is malformed, and |
| this error will be logged. No users will be able to login.</p> |
| </section> |
| <section id="unexpected-character-data"> |
| <h4>Unexpected character data<a class="headerlink" href="#unexpected-character-data" title="Link to this heading">#</a></h4> |
| <p>Character data (text not within angle brackets) can only exist within the |
| <code class="docutils literal notranslate"><span class="pre"><param></span></code> tag. If it exists elsewhere, then the XML is malformed, and this |
| error will be logged. No users will be able to login.</p> |
| </section> |
| <section id="invalid-encoding-type"> |
| <h4>Invalid encoding type<a class="headerlink" href="#invalid-encoding-type" title="Link to this heading">#</a></h4> |
| <p>There are only two legal values for the <code class="docutils literal notranslate"><span class="pre">encoding</span></code> attribute of the |
| <code class="docutils literal notranslate"><span class="pre"><authorize></span></code> tag: <code class="docutils literal notranslate"><span class="pre">plain</span></code> (indicating plain text) and <code class="docutils literal notranslate"><span class="pre">md5</span></code> (indicating a |
| value hashed with the MD5 digest). If any other value is used, then the XML is |
| malformed, and this error will be logged. No users will be able to login.</p> |
| </section> |
| <section id="user-mapping-could-not-be-read"> |
| <h4>User mapping could not be read<a class="headerlink" href="#user-mapping-could-not-be-read" title="Link to this heading">#</a></h4> |
| <p>If for any reason the user mapping file cannot be read (the servlet container |
| lacks read permission for the file, the file does not exist, etc.), this error |
| will be logged. Check <code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code> to see where the user mapping file |
| is specified to exist, and then check that is both exists and is readable by |
| your servlet container.</p> |
| </section> |
| </section> |
| <section id="guacamole-properties-errors"> |
| <span id="id2"></span><h3><code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code> errors<a class="headerlink" href="#guacamole-properties-errors" title="Link to this heading">#</a></h3> |
| <p>If a property is malformed or a required property is missing, an error |
| describing the problem will be logged.</p> |
| <section id="property-property-is-required"> |
| <h4>Property PROPERTY is required<a class="headerlink" href="#property-property-is-required" title="Link to this heading">#</a></h4> |
| <p>If Guacamole or an extension of Guacamole requires a specific property in |
| <code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code>, but this property is not defined, this error will be |
| logged. Check which properties are required by the authentication provider (or |
| other extensions) in use, and then compare that against the properties within |
| <code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code>.</p> |
| </section> |
| </section> |
| <section id="authentication-errors"> |
| <span id="guacamole-auth-errors"></span><h3>Authentication errors<a class="headerlink" href="#authentication-errors" title="Link to this heading">#</a></h3> |
| <p>If someone attempts to login with invalid credentials, or someone attempts to |
| access a resource or connection that does not exist or they do not have access |
| to, errors regarding the invalid attempt will be logged.</p> |
| <section id="cannot-connect-user-not-logged-in"> |
| <h4>Cannot connect - user not logged in<a class="headerlink" href="#cannot-connect-user-not-logged-in" title="Link to this heading">#</a></h4> |
| <p>A user attempted to connect using the HTTP tunnel, and while the tunnel does |
| exist and is attached to their session, they are not actually logged in. |
| Normally, this isn’t strictly possible, as a user has to have logged in for a |
| tunnel to be attached to their session, but as it isn’t an impossibility, this |
| error does exist. If you see this error, it could mean that the user logged out |
| at the same time that they made a connection attempt.</p> |
| </section> |
| <section id="requested-configuration-is-not-authorized"> |
| <h4>Requested configuration is not authorized<a class="headerlink" href="#requested-configuration-is-not-authorized" title="Link to this heading">#</a></h4> |
| <p>A user attempted to connect to a configuration with a given ID, and while that |
| configuration does exist, they are not authorized to use it. This could mean |
| that the user is trying to access things they have no privileges for, or that |
| they are trying to access configurations they legitimately should, but are |
| actually logged out.</p> |
| </section> |
| <section id="user-has-no-session"> |
| <h4>User has no session<a class="headerlink" href="#user-has-no-session" title="Link to this heading">#</a></h4> |
| <p>A user attempted to access a page that needs data from their session, but their |
| session does not actually exist. This usually means the user has not logged in, |
| as sessions are created through the login process.</p> |
| </section> |
| </section> |
| <section id="tunnel-errors"> |
| <span id="guacamole-tunnel-errors"></span><h3>Tunnel errors<a class="headerlink" href="#tunnel-errors" title="Link to this heading">#</a></h3> |
| <p>The tunnel frequently returns errors if guacd is killed, the connection is |
| closed, or the client abruptly closes the connection.</p> |
| <section id="no-such-tunnel"> |
| <h4>No such tunnel<a class="headerlink" href="#no-such-tunnel" title="Link to this heading">#</a></h4> |
| <p>An attempt was made to use a tunnel which does not actually exist. This is |
| usually just the JavaScript client sending a leftover message or two while it |
| hasn’t realized that the server has disconnected. If this error happens |
| consistently and is associated with Guacamole generally not working, it could |
| be a bug.</p> |
| </section> |
| <section id="no-tunnel-created"> |
| <h4>No tunnel created<a class="headerlink" href="#no-tunnel-created" title="Link to this heading">#</a></h4> |
| <p>A connection attempt for a specific configuration was made, but the connection |
| failed, and no tunnel was created. This is usually because the user was not |
| authorized to use that connection, and thus no tunnel was created for access to |
| that connection.</p> |
| </section> |
| <section id="no-query-string-provided"> |
| <h4>No query string provided<a class="headerlink" href="#no-query-string-provided" title="Link to this heading">#</a></h4> |
| <p>When the JavaScript client is communicating with the HTTP tunnel, it <em>must</em> |
| provide data in the query string describing whether it wants to connect, read, |
| or write. If this data is missing as the error indicates, there is a bug in the |
| HTTP tunnel.</p> |
| </section> |
| <section id="tunnel-reached-end-of-stream"> |
| <h4>Tunnel reached end of stream<a class="headerlink" href="#tunnel-reached-end-of-stream" title="Link to this heading">#</a></h4> |
| <p>An attempt to read from the tunnel was made, but the tunnel in question has |
| already reached the end of stream (the connection is closed). This is mostly an |
| informative error, and can be ignored.</p> |
| </section> |
| <section id="tunnel-is-closed"> |
| <h4>Tunnel is closed<a class="headerlink" href="#tunnel-is-closed" title="Link to this heading">#</a></h4> |
| <p>An attempt to read from the tunnel was made, but the tunnel in question is |
| already closed. This can happen if the client or guacd have closed the |
| connection, but the client has not yet settled down and is still making read |
| attempts. As there can be lags between when connections close and when the |
| client realizes it, this can be safely ignored.</p> |
| </section> |
| <section id="end-of-stream-during-initial-handshake"> |
| <h4>End of stream during initial handshake<a class="headerlink" href="#end-of-stream-during-initial-handshake" title="Link to this heading">#</a></h4> |
| <p>If guacd closes the connection suddenly without allowing the client to complete |
| the initial handshake required by the Guacamole protocol, this error will |
| appear in the logs. If you see this error, you should check syslog for any |
| errors logged by guacd to determine why it closed the connection so early.</p> |
| </section> |
| <section id="element-terminator-of-instruction-was-not-nor"> |
| <h4>Element terminator of instruction was not ‘;’ nor ‘,’<a class="headerlink" href="#element-terminator-of-instruction-was-not-nor" title="Link to this heading">#</a></h4> |
| <p>The Guacamole protocol imposes a strict format which requires individual parts |
| of instructions (called “elements”) to end with either a “;” or “,” character. |
| If they do not, then something has gone wrong during transmission. This usually |
| indicates a bug in the client plugin in use, guacd, or libguac.</p> |
| </section> |
| <section id="non-numeric-character-in-element-length"> |
| <h4>Non-numeric character in element length<a class="headerlink" href="#non-numeric-character-in-element-length" title="Link to this heading">#</a></h4> |
| <p>The Guacamole protocol imposes a strict format which requires each element of |
| an instruction to have a length prefix, which must be composed entirely of |
| numeric characters (digits 0 through 9). If a non-numeric character is read, |
| then something has gone wrong during transmission. This usually indicates a bug |
| in the client plugin in use, guacd, or libguac.</p> |
| </section> |
| </section> |
| </section> |
| </section> |
| |
| |
| </article> |
| |
| |
| |
| |
| |
| |
| <footer class="prev-next-footer d-print-none"> |
| |
| <div class="prev-next-area"> |
| <a class="left-prev" |
| href="batch-import.html" |
| title="previous page"> |
| <i class="fa-solid fa-angle-left"></i> |
| <div class="prev-next-info"> |
| <p class="prev-next-subtitle">previous</p> |
| <p class="prev-next-title">Importing connections from CSV, JSON, or YAML</p> |
| </div> |
| </a> |
| <a class="right-next" |
| href="ldap-auth.html" |
| title="next page"> |
| <div class="prev-next-info"> |
| <p class="prev-next-subtitle">next</p> |
| <p class="prev-next-title">LDAP authentication</p> |
| </div> |
| <i class="fa-solid fa-angle-right"></i> |
| </a> |
| </div> |
| </footer> |
| |
| </div> |
| |
| |
| |
| <div class="bd-sidebar-secondary bd-toc"><div class="sidebar-secondary-items sidebar-secondary__inner"> |
| |
| |
| <div class="sidebar-secondary-item"> |
| <div class="page-toc tocsection onthispage"> |
| <i class="fa-solid fa-list"></i> Contents |
| </div> |
| <nav class="bd-toc-nav page-toc"> |
| <ul class="visible nav section-nav flex-column"> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#it-isnt-working">It isn’t working</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#no-graphics-appear">No graphics appear</a></li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#connections-involving-unicode-dont-work">Connections involving Unicode don’t work</a></li> |
| </ul> |
| </li> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#syslog">syslog</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#guacd-errors">guacd errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-bind-socket-to-any-addresses">Unable to bind socket to any addresses.</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-start-input-thread">Unable to start input thread</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#client-finished-abnormally">Client finished abnormally</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-fork-parent">Could not fork() parent</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-change-working-directory-to">Unable to change working directory to /</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-redirect-standard-file-descriptors-to-dev-null">Unable to redirect standard file descriptors to /dev/null</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-parsing-given-address-or-port-hostname">Error parsing given address or port: HOSTNAME</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-opening-socket">Error opening socket</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unable-to-resolve-host">Unable to resolve host</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-become-a-daemon">Could not become a daemon</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-write-pid-file">Could not write PID file</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-listen-on-socket">Could not listen on socket</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#could-not-accept-client-connection">Could not accept client connection</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-forking-child-process">Error forking child process</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-closing-daemon-reference-to-child-descriptor">Error closing daemon reference to child descriptor</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-sending-sync-instruction">Error sending “sync” instruction</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-flushing-output">Error flushing output</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-handling-server-messages">Error handling server messages</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-reading-instruction">Error reading instruction</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#client-instruction-handler-error">Client instruction handler error</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-reading-opcode">Error reading OPCODE</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-sending-args">Error sending “args”</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-loading-client-plugin">Error loading client plugin</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-instantiating-client">Error instantiating client</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#libguac-client-vnc-errors">libguac-client-vnc errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-waiting-for-vnc-message">Error waiting for VNC message</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#error-handling-vnc-server-message">Error handling VNC server message</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#wrong-argument-count-received">Wrong argument count received</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#libguac-client-rdp-errors">libguac-client-rdp errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#invalid-parameter">Invalid PARAMETER</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#support-for-the-cliprdr-channel-clipboard-redirection-could-not-be-loaded">Support for the CLIPRDR channel (clipboard redirection) could not be loaded</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#cannot-create-static-channel-name-failed-to-load-guac-common-svc-plugin-for-freerdp">Cannot create static channel “NAME”: failed to load “guac-common-svc” plugin for FreeRDP</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#server-requested-unsupported-clipboard-data-type">Server requested unsupported clipboard data type</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#clipboard-data-missing-null-terminator">Clipboard data missing null terminator</a></li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#servlet-container-logs">Servlet container logs</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#user-mapping-xml-errors"><code class="docutils literal notranslate"><span class="pre">user-mapping.xml</span></code> errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#attribute-name-required-for-connection-tag">Attribute “name” required for connection tag</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#attribute-name-required-for-param-tag">Attribute “name” required for param tag</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#unexpected-character-data">Unexpected character data</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#invalid-encoding-type">Invalid encoding type</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#user-mapping-could-not-be-read">User mapping could not be read</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#guacamole-properties-errors"><code class="docutils literal notranslate"><span class="pre">guacamole.properties</span></code> errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#property-property-is-required">Property PROPERTY is required</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#authentication-errors">Authentication errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#cannot-connect-user-not-logged-in">Cannot connect - user not logged in</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#requested-configuration-is-not-authorized">Requested configuration is not authorized</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#user-has-no-session">User has no session</a></li> |
| </ul> |
| </li> |
| <li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-errors">Tunnel errors</a><ul class="nav section-nav flex-column"> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-such-tunnel">No such tunnel</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-tunnel-created">No tunnel created</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#no-query-string-provided">No query string provided</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-reached-end-of-stream">Tunnel reached end of stream</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#tunnel-is-closed">Tunnel is closed</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#end-of-stream-during-initial-handshake">End of stream during initial handshake</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#element-terminator-of-instruction-was-not-nor">Element terminator of instruction was not ‘;’ nor ‘,’</a></li> |
| <li class="toc-h4 nav-item toc-entry"><a class="reference internal nav-link" href="#non-numeric-character-in-element-length">Non-numeric character in element length</a></li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </nav></div> |
| |
| </div></div> |
| |
| |
| </div> |
| <footer class="bd-footer-content"> |
| |
| <div class="bd-footer-content__inner container"> |
| |
| <div class="footer-item"> |
| |
| <p class="component-author"> |
| By The Apache Software Foundation |
| </p> |
| |
| </div> |
| |
| <div class="footer-item"> |
| |
| |
| <p class="copyright"> |
| |
| © Copyright 2025 The Apache Software Foundation. |
| <br/> |
| |
| </p> |
| |
| </div> |
| |
| <div class="footer-item"> |
| |
| </div> |
| |
| <div class="footer-item"> |
| |
| </div> |
| |
| </div> |
| </footer> |
| |
| |
| </main> |
| </div> |
| </div> |
| |
| <!-- Scripts loaded after <body> so the DOM is not blocked --> |
| <script src="_static/scripts/bootstrap.js?digest=dfe6caa3a7d634c4db9b"></script> |
| <script src="_static/scripts/pydata-sphinx-theme.js?digest=dfe6caa3a7d634c4db9b"></script> |
| |
| <footer class="bd-footer"> |
| </footer> |
| </body> |
| </html> |
