Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot connect standalone gateway with brokers behind a reverse proxy #9342

Closed
npepinpe opened this issue May 10, 2022 · 0 comments · Fixed by #9572
Closed

Cannot connect standalone gateway with brokers behind a reverse proxy #9342

npepinpe opened this issue May 10, 2022 · 0 comments · Fixed by #9572
Assignees
@npepinpe
Labels
area/observability Marks an issue as observability related area/security Marks an issue as security related kind/bug Categorizes an issue or PR as a bug severity/mid Marks a bug as having a noticeable impact but with a known workaround version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Milestone
8.1

Comments

@npepinpe
Copy link
Member

Describe the bug

When the standalone gateway is behind a reverse proxy, it cannot properly communicate with the other brokers - it can talk to them, but it will not reverse replies correctly, as the address it advertises in the cluster is not the one of the reverse proxy but rather the one it has locally bound to.

To Reproduce

Set up the standalone gateway behind a reverse proxy, then try to join a cluster of brokers.

Expected behavior

Like the brokers, the gateway can also be set up behind a reverse proxy, making it compatible with service meshes.

Environment:

  • OS: Linux
  • Zeebe Version: 8.1.0-SNAPSHOT and prior
  • Configuration: using a reverse proxy in front of the gateway
@npepinpe npepinpe added kind/bug Categorizes an issue or PR as a bug severity/mid Marks a bug as having a noticeable impact but with a known workaround area/security Marks an issue as security related area/observability Marks an issue as observability related team/distributed labels May 10, 2022
@npepinpe npepinpe added this to the 8.1 milestone May 10, 2022
@npepinpe npepinpe self-assigned this Jun 21, 2022
@npepinpe npepinpe mentioned this issue Jun 22, 2022
Merged
10 tasks
@lenaschoenburg lenaschoenburg added the version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 label Jul 5, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@npepinpe npepinpe

Labels
area/observability Marks an issue as observability related area/security Marks an issue as security related kind/bug Categorizes an issue or PR as a bug severity/mid Marks a bug as having a noticeable impact but with a known workaround version:8.1.0-alpha3 Marks an issue as being completely or in parts released in 8.1.0-alpha3 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Milestone
8.1
Development

Successfully merging a pull request may close this issue.

Enable gateway to use reverse proxy for cluster communication camunda/camunda
3 participants
@npepinpe @lenaschoenburg @Zelldon