Hello Am 13.11.18 um 11:03 schrieb Rene Schroth ([email protected]): > Hi SOGo Admins and Developers! > > From the SOGo Integrator customizing section of the guide > > https://sogo.nu/files/docs/SOGoMozillaThunderbirdConfigurationGuide.html > > <QUOTE> > Note that if you changed the x-webobjects-server-url configuration > setting from your HTTP server configuration file for SOGo, the value > must match the one you specify in isi:updateURL - even the port number. > The Add-On's extensions.rdf file looks like this: > </QUOTE> > > My webserver's (Nginx) SOGo configuration file is > /etc/nginx/templates/sogo.tmpl > > Its x-webobjects-server-url by default is: > > proxy_set_header x-webobjects-server-url https://$host; > > The related value of SOGo Integrator's extension.rdf file is: > > isi:updateURL="https://myIRMserver.myDomain.myTLD/plugins/updates.php?plugin=%ITEM_ID%&version=%ITEM_VERSION%&platform=%PLATFORM%";> > > > So I changed the sogo.tmpl's x-webobjects-server-url to: > > proxy_set_header x-webobjects-server-url > https://irm.mmlab.de/plugins/updates.php?plugin=%ITEM_ID%&\;version=%ITEM_VERSION%&\;platform=%PLATFORM%; >
This is not the server URL! It is the URL of the update page. Change that either to proxy_set_header x-webobjects-server-url https://irm.mmlab.de/ or leave it at proxy_set_header x-webobjects-server-url https://$host; if your hostname is set correct. > Result: The Nginx Web Server even doesn't start anymore. Claims about > the manipulated line. > > Did I misunderstand anything in the manual stating: > > <QUOTE> > ...the value must match the one you specify in isi:updateURL... > </QUOTE> > Match, not equal. What that basically means: You only can get updates from the same server, where your SOGo is running on. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
