You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell the issues relates to the Zulip smokescreen proxy and requests to the SOCIAL_AUTH servers getting caught up there. The issue was resolved by adding SOCIAL_AUTH_PROXIES = {"http": None, "https": None}
to the settings.py file in /etc/zulip/settings.py.
When running docker-zulip, you can add the following to the docker-compose.yml to automatically add this line to settings.py in every build (as I have also done in the zulip-deployment docker-compose.yml in branch #18 ): ZULIP_CUSTOM_SETTINGS: SOCIAL_AUTH_PROXIES={"http":None,"https":None}
If one is running multiple social auth setups, you can allegedly also use specific auth-proxy settings, like: SOCIAL_AUTH_OIDC_PROXIES etc., but I did not test this.
@nicolas-semaphor
You can describe the bug here.
The text was updated successfully, but these errors were encountered: