Open topic with navigation

TIBCO ActiveSpaces® - Enterprise Edition 5.0.0

# Configuration Options when the Proxy and Client are on Different Subnets

When the realm service and proxy are running on a subnet that is different from the one on which the client application is running, the proxy might need additional configuration. This is a requirement when you are dealing with a Network Address Translation (NAT) setup as is common with cloud environments or Docker.

For example, if the realm service and proxy are on the subnet `10.0.75.0/24` and the ActiveSpaces client application is on the subnet `192.168.1.0/24`, the client application often cannot route to the `10.0.75.0/24` subnet (the proxy's subnet). In such a situation, in addition to `proxy_client_listen_port`, configure the `proxy_client_listen_external_host` option.

If the port that the proxy is listening on is mapped to a different external port, use `proxy_client_listen_external_port` to specify the correct external port.

Note: If you are in a dynamic environment, use the `-e <ip:port>` command-line parameter when you run the `tibdgproxy` process. For more information, see Starting a Proxy with an External Host and Port.
Subtopics

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO ActiveSpaces® - Enterprise Edition

Copyright © 2009-2025. Cloud Software Group, Inc. All Rights Reserved.