How to Configure HTTP Proxy Settings for Turbine 26.x and Later
This guide explains how to configure HTTP proxy settings for Turbine environments version 26.x and later. In these versions, proxy configurations are managed directly through the dedicated HTTP proxy settings option in the Admin Console, which securely stores proxy credentials as secrets instead of using legacy Beta Configuration settings.
Follow this procedure for new installations or upgrades on 26.x or later whenever your deployment requires outbound network connectivity through an HTTP/HTTPS proxy.
Overview & Impact
In earlier Turbine releases, proxy parameters were provided under Beta Configuration settings. Starting in version 26.x, the platform introduced a fully supported method using the dedicated HTTP proxy settings panel.
Relying solely on legacy Beta Configuration settings in 26.x+ environments can cause tenant provisioning workflows to fail or stall, often leaving tenant creation indefinitely in the Creating state.
To ensure smooth tenant provisioning and proper service communication, always configure your proxy parameters using the standard HTTP proxy settings workflow.
When to Apply This Configuration
- New Turbine installations on 26.x or later that require a proxy
- Upgraded environments on 26.x or later where tenant creation does not complete
- Environments where proxy values were previously added only through Beta Configuration settings
Configuration Procedure
- Log in to the Admin Console.
- Go to Config.
- Locate and enable the HTTP proxy settings option.
- Enter the following values:
- HTTP proxy
- HTTPS proxy
- No proxy
- Save the configuration.
- Deploy the changes.
Important: Carefully review all three settings before deploying changesβespecially the No proxy list. Incorrect exclusions can disrupt internal microservice communication or route unexpected traffic through the proxy. |
|---|
No Proxy Format Reference
Specify the No proxy entry formatted as a JSON array of strings:
["value1", "value2", "value3", "value4"]Include all IP addresses, hostname aliases, domains, or internal service names that must bypass proxy routing.
Verification & Expected Results
After saving and deploying the configuration, the environment should use the proxy settings provided through the dedicated HTTP proxy settings configuration path. In proxy-enabled deployments, this helps ensure tenant provisioning can complete successfully.
Troubleshooting Common Symptoms
- Tenant creation remains stuck in Creating
- Newly installed or upgraded 26.x environments cannot provision tenants behind a proxy
- Proxy-enabled environments continue using outdated Beta Configuration values that are no longer sufficient for tenant creation workflows
Best Practices & FAQs
Always manage proxy configurations exclusively through Admin Console > Config > HTTP proxy settings on Turbine 26.x and higher deployments.
Tip: If tenant creation becomes stuck in a proxy-enabled 26.x system, first verify that settings under Admin Console > Config > HTTP proxy settings are active and were fully saved and deployed. |
|---|
Frequently Asked Questions
Can I still use Beta Configuration settings for proxy values?
For 26.x and later, proxy settings should be configured through the dedicated HTTP proxy settings section. The older Beta Configuration method should not be used as the primary proxy configuration path for tenant creation in these versions.
What should I check if tenant creation is stuck?
Verify that the environment requires a proxy, confirm the HTTP proxy settings box is enabled, review the HTTP, HTTPS, and no proxy values, then save and deploy the configuration.
Why is the No Proxy list critical?
The no proxy list ensures internal addresses or services bypass the proxy. If required internal endpoints are not excluded, platform components may fail to communicate correctly.