Skip to main content

Resolving Connection Issues in Workbench Due to HTTP Proxy Changes

Posit Support
  • Updated

Issue Overview

Users behind a proxy server may experience session connection failures due to missing HTTP Proxy configurations after upgrading to 2024.12.0

Error Message

Affected users may see the following error in the logs:

system error 111 (Connection refused) [description: Proxy connection failed, host: example.host.corp

The primary symptom is that users are unable to connect to their Workbench session.

Cause

As of Workbench 2024.12.0, HTTP Proxy variables are supported in rserver and rsession. If Workbench environments are behind a proxy server, it is essential to configure the NO_PROXY list to include local addresses for Job Launcher sessions and other internal services.

Resolution

To resolve this issue, ensure that local addresses are properly included in the NO_PROXY list.

Steps to Fix

  1. Edit the environment variables configuration file:

    sudo vi /etc/rstudio/env-vars

  2. Add the appropriate no_proxy values:

    no_proxy=example.host.corp,host.corp

  3. Save the file and restart the Workbench services:

    sudo systemctl restart rstudio-server
    sudo systemctl restart rstudio-launcher

For additional details, refer to the Outgoing Proxies section of the Posit Workbench Administration Guide.

Workaround

If users are still encountering issues, an alternative is to use an IP address instead of a fully qualified domain name (FQDN) in the no_proxy configuration.

Example:

no_proxy=10.10.10.5

Known Bug

There is an issue where an extra period (.) is appended to subdomains in proxy settings. This is tracked under issue #7261 and has been addressed in the 2024.12.1 patch release.

Additional Resources

If issues persist, submit a support ticket with relevant log details.

Related articles