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.

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

[Portals] Double proxy issue in /portal URLs when Cerb itself is behind a proxy #822

jstanden opened this Issue Nov 20, 2018 · 1 comment


1 participant
Copy link

jstanden commented Nov 20, 2018

The DevblocksProxyHost: header is being set from a cnames proxy (e.g. Openresty) when accessing Cerb. This prevents the self-hosted /portal URLs from working on the same host.

In Cerb Cloud, using the * hosts for these portals works fine since they aren't behind a proxy. Using a vanity CNAME to access Cerb triggers the issue.

@jstanden jstanden created this issue from a note in 9.1.3 (In Development) Nov 20, 2018

@jstanden jstanden added the bug label Nov 20, 2018

@jstanden jstanden modified the milestones: 9.0.8, 9.0.9 Nov 20, 2018


This comment has been minimized.

Copy link

jstanden commented Dec 1, 2018

Fixed in 9.0.9

@jstanden jstanden closed this Dec 1, 2018

9.1.3 automation moved this from In Development to Completed! Dec 1, 2018

jstanden added a commit to wgm/cerb that referenced this issue Dec 12, 2018

* [Portals] Fixed an issue with the built-in `/portal` hosting when C…
…erb itself is already behind a proxy. This is more common in Cerb Cloud when an instance uses a personalized domain rather than the `*` domains. In these double-proxy situations, portal links and forms weren't working properly, and most redirected to the Cerb login form.

Fixes jstanden#822
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment