proxy65 behind NAT: Proxy returns the local ip as host and NOT the domain name -> no access to proxy from the outside world

Hi all!

I am struggling with the proxy65 configuration. My ejabberd sits behind a nat firewall. So when I want to use the internal socks proxy it will return the ip address of it's local interface as it's host address to clients and not the domain name. That way the proxy isnt reachable from the outside world.

The problem seems to be known quite a while since I could find two one year old tickets (EJAB-838, EJAB-924) concerning that behaviour with patches to fix the problem but there hasnt been a change in code...

https://support.process-one.net/browse/EJAB-838
https://support.process-one.net/browse/EJAB-924

Anyone know if there already is a solution I have missed or when the code will get patched?

Thanks
Zubasu

UPDATE: For everyone with

UPDATE:

For everyone with the same problem:

I compiled the proxy module with the patch from https://support.process-one.net/browse/EJAB-924 and it works. For instructions how to do so under windows look at http://www.ejabberd.im/compile-module-windows.

Still interested if this patch will find its way into trunk. Maybe someone can answer this...

Thanks
Zubasu

Re: proxy65 behind NAT

The patch is accepted and will be introduced in upcoming 2.1.3 release.

Syndicate content