We were able to get sogo working over ssl on nginx with port 444 (meaning that to log into the sogo web client we could do that over part 444). The browser complains, but it did work. We were even able to get Thunderbird working, but had trouble getting integrator working because it wasn't connecting and wouldn't offer to add an exception (from what I can remember). We gave up, bought a ssl cert and just used 443 in the end and had help from Inverse setting it up.
On Friday, February 21, 2014 5:02 PM, Kevin Brault <[email protected]> wrote: Hello everyone, I am trying to configure SOGo to run on an alternate SSL port but I am having to success. Does anyone have any experience with doing this? Will it break any functionality with the Thunderbird plugin. I am only interested in changing ports for the SOGo connection and webmail. IMAPS and STMPS will stay the same. Thank you in advance for your help. -- [email protected] https://inverse.ca/sogo/lists-- [email protected] https://inverse.ca/sogo/lists
