[email protected] wrote:
Hello,
SOGo nightly build is installed and works fine so far but it can't be reached
from the internet because it is on a private ip class. I have another server
which is gateway and of course which can be reached from internet.
Say the gateway is the A machine with ip 192.168.8.1 and B machine containing
SOGo is 192.168.2.32
I configured vhost and added properly proxypass and proxyreverse on the A
machine to forward requests to the B machine and to get results from B to A.
I also modified the httpd/mod.d/proxy.conf to allow requests from all so i'm
sure the A apache's proxy is not clogging something.
It seems to work and from the A machine i can reach the B machine.
When i ask for simple html page like the default one from the apache,
everything is ok.
When i make a request to reach B/SOGo i have the SOGO's login page displayed
but all CSS are missing and i can't login when i enter user name and password.
Is looks like the displayed page is not able to interact with B server.
Is SOGo able to work in this kind of context or must it be directly accessible
from the internet ?
Didn't found any example about this kind of configuration.
Without evidence, it's hard to know exactly what's going on.
Nonetheless, look at:
http://www.sogo.nu/english/support/faq/article/my-sogod-daemons-are-only-accessible-on-localhost-2.html
Regards,
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
--
[email protected]
https://inverse.ca/sogo/lists
