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.

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

Closed
jaykijay opened this issue Jul 24, 2017 · 5 comments
Closed

Don't use Proxy on localhost Address. #1292

jaykijay opened this issue Jul 24, 2017 · 5 comments
Assignees
Labels
Milestone

Comments

@jaykijay
Copy link
Contributor

jaykijay commented Jul 24, 2017

Infos:

  • Used Zammad version: 1.6.1
  • Used Zammad installation source: (source, package, ...) debian repo
  • Operating system: Debian
  • Browser + version: irrelevant

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

@monotek
Copy link
Member

monotek commented Jul 24, 2017

Sorry, i don't understand whats your problem?
Using Elasticsearch on 127.0.0.1 is the default.

@jaykijay
Copy link
Contributor Author

Hi,
yes i've installed everything like described in your docs. But before installing Elasticsearch i've written my Proxy in the Config under network.
After i did this, i couldn't use zammad run rake searchindex:rebuild
anymore, because it always tried to connect to my local installed ( http://localhost:9200)
elasticsearch engine via the Proxy, which it mustn't. The proxy setting in Zammad should have an exceptions which is either configureasble as you like: Something like "don't use proxy on this Adresses:" or at least should never use proxy when trying to connect to something which is on localhost.
You can easily reproduce this if you write in a Proxy before running configuring elasticsearch.

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.
Hope you understand now, if not please let me know then i'll try to explain it in greater detail.
Thanks

@hanneshal
Copy link
Contributor

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
Johannes

@jaykijay
Copy link
Contributor Author

You can either enable Proxy via Console, described here (Enable Proxy): https://docs.zammad.org/en/latest/admin-console.html
Or via the Webinterface under
System->Network
both will result in the same.
I've entered my Http Proxy Adress there, and after i did this every traffic was send to proxy, connections to localhost, too . Which i mean is very bad.

@martini martini self-assigned this Jul 25, 2017
@martini martini added the bug label Jul 25, 2017
@martini martini added this to the 1.5.1 milestone Jul 27, 2017
@martini
Copy link
Collaborator

martini commented Jul 27, 2017

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:

screen shot 2017-07-27 at 11 48 08

Thanks a lot!

-Martin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants