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
Don't use Proxy on localhost Address. #1292
Comments
Sorry, i don't understand whats your problem? |
Hi, The problem here is not in elasticsearch but in the way Zammad uses Proxy. It uses Proxy for every connection even if they're going to localhost. |
Where did you entered your Proxy config? There is only the NGINX Config, which needs the upstream for the rails and websocket server. Can you paste an example what and where modified proxy settings? I never configured a proxy on local instances. regards |
You can either enable Proxy via Console, described here (Enable Proxy): https://docs.zammad.org/en/latest/admin-console.html |
Hi @jaykijay Thanks for your pull request. We did a small rework. For upcoming Zammad 2.0 we added a config option in UI to set the hosts where no proxy is used: Thanks a lot! -Martin |
Infos:
Expected behavior:
In example of running elasticsearch on localhost and using localhost or 127.0.0.1 as Adress, no proxy should be used because localhost mustn't be connected over Proxy.
Actual behavior:
It connects via my Proxy Server from which i got errors, because 127.0.0.1 is not a good Ip for using Proxy.
*
Steps to reproduce the behavior:
Set Proxy under System -> Proxy and try something on localhost via zammad, e.g. using elasticsearch or setting up elasticsearch
The text was updated successfully, but these errors were encountered: