Has anyone ever sucsessfully run SOGo in a docker image?
I tried but failed miserably... not knowing anything about docker and sogo at the same time.
So far i believe I would have to access SOGo through port 80.
As port 80 is already in use i would probably have to reconfigure the standard port for SOGo inside the docker image?
I don't use it but you could change the OMV web interface to a different port to free up port 80.
I want SOGo to use my host systems nginx server. SOGo manual advises to add a site for it with a specific site configuration.
When i add this manually via shell i always get an error when starting up nginx. This is probably due to OMV interfering with my manual configuration.
How would i add the suggested configuration in OMV?
Here is what they suggest me to add: https://wiki.ubuntuusers.de/Archiv/SOGo/#Nginx
or
http://wiki.sogo.nu/nginxSettings
It seems strange to me to have another web serve those pages but ...
I would install the nginx the plugin. Create a server in the server tab.
Select none for directory.
Select name-based for Host type and enter sogo fqdn.
Enable ssl
select ssl cert created on cert page
Then paste all of the location sections in extra options.
location = /
{
rewrite ^ `https://$server_name/SOGo`;
allow all;
}
# For iOS 7
location = /principals/
{
rewrite ^ `https://$server_name/SOGo/dav`;
allow all;
}
location ^~/SOGo
{
proxy_pass `http://127.0.0.1:20000`;
proxy_redirect `http://127.0.0.1:20000` default;
# forward user's IP address
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $server_name;
proxy_set_header x-webobjects-server-url $scheme://$host;
proxy_set_header x-webobjects-server-port $server_port;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
break;
}
location /SOGo.woa/WebServerResources/
{
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location /SOGo/WebServerResources/
{
alias /usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location (^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$)
{
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
location (^/SOGo/so/ControlPanel/Products/[^/]*UI/Resources/.*\.(jpg|png|gif|css|js)$)
{
alias /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
They may need some tweaking.
I agree and i had the same idea in the meantime
Although my guess was i would have to add the servername and root directory as well.
This is what i had put but no luck:
server_name debNAS;
root /var/lib/docker/aufs/mnt/efa068d13517ecc5bbbc49d41d7b41d4be722c83bfba22645e9728b18c74a6ac/usr/lib/GNUstep/SOGo/WebServerResources/;
location = /
{
rewrite ^ https://$server_name/SOGo;
allow all;
}
location ^~/SOGo {
proxy_pass http://127.0.0.1:20000;
proxy_redirect http://127.0.0.1:20000 default;
# forward user's IP address
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header x-webobjects-server-protocol HTTP/1.0;
proxy_set_header x-webobjects-remote-host 127.0.0.1;
proxy_set_header x-webobjects-server-name $server_name;
proxy_set_header x-webobjects-server-url $scheme://$host;
proxy_connect_timeout 90;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 4k;
proxy_buffers 4 32k;
proxy_busy_buffers_size 64k;
proxy_temp_file_write_size 64k;
client_max_body_size 50m;
client_body_buffer_size 128k;
break;
}
location /SOGo.woa/WebServerResources/ {
alias /var/lib/docker/aufs/mnt/efa068d13517ecc5bbbc49d41d7b41d4be722c83bfba22645e9728b18c74a6ac/usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location /SOGo/WebServerResources/ {
alias /var/lib/docker/aufs/mnt/efa068d13517ecc5bbbc49d41d7b41d4be722c83bfba22645e9728b18c74a6ac/usr/lib/GNUstep/SOGo/WebServerResources/;
allow all;
}
location ^/SOGo/so/ControlPanel/Products/([^/]*)/Resources/(.*)$ {
alias /var/lib/docker/aufs/mnt/efa068d13517ecc5bbbc49d41d7b41d4be722c83bfba22645e9728b18c74a6ac/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}
location ^/SOGo/so/ControlPanel/Products/[^/]*UI/Resources/.*\.(jpg|png|gif|css|js)$
{
alias /var/lib/docker/aufs/mnt/efa068d13517ecc5bbbc49d41d7b41d4be722c83bfba22645e9728b18c74a6ac/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2;
}I get either error 400 or bad gateway 502
There is already a server name and root field in the server section of the nginx plugin. Try what I posted and look at the logs that the nginx plugin allows you to view.
Ok. I have tried both configs and the result is the same.
Here is what the error log says:
2016/03/28 10:19:15 [error] 7051#0: *108 upstream prematurely closed connection while reading response header from upstream, client: ::ffff:192.168.1.39, server: debnas.beerbeach, request: "GET /SOGo HTTP/1.1", upstream: "http://127.0.0.1:20000/SOGo", host: "debnas.beerbeach"Does this ring any bell for you? Might be an issue with the SOGO backend...
Here is what the sogo.log says:
Mar 28 14:58:20 sogod [24]: version 2.3.9 (build @shiva.inverse 201603161352) -- starting
Mar 28 14:58:20 sogod [24]: vmem size check enabled: shutting down app when vmem > 384 MB
Mar 28 14:58:20 sogod [24]: <0x0x7f8742d880f8[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo':
Mar 28 14:58:20 sogod [24]: <0x0x7f8742d880f8[SOGoProductLoader]> MainUI.SOGo, MailPartViewers.SOGo, PreferencesUI.SOGo, Contacts.SOGo, CommonUI.SOGo, Mailer.SOGo, SchedulerUI.SOGo, Appointments.SOGo, ContactsUI.SOGo, MailerUI.SOGo, AdministrationUI.SOGo
Mar 28 14:58:20 sogod [24]: <0x0x7f8742e35578[WOWatchDog]> listening on 127.0.0.1:20000
Mar 28 14:58:20 sogod [24]: <0x0x7f8742e35578[WOWatchDog]> watchdog process pid: 24
Mar 28 14:58:20 sogod [24]: <0x0x7f87404196a0[WOWatchDogChild]> watchdog request timeout set to 10 minutes
Mar 28 14:58:20 sogod [24]: <0x0x7f8742e35578[WOWatchDog]> preparing 1 children
Mar 28 14:58:20 sogod [24]: <0x0x7f8742e35578[WOWatchDog]> child spawned with pid 50
2016-03-28 14:58:20.294 sogod[24] ERROR: could not open MySQL4 connection to database 'sogo': Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Mar 28 14:58:20 sogod [50]: [ERROR] <0x0x7f8742e7d718[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x7f8742bf36d8] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile
Mar 28 14:58:20 sogod [50]: [WARN] <0x0x7f8742e7d718[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2016-03-28 14:58:20 +0000
Mar 28 14:58:40 sogod [50]: <0x0x7f8742dca788[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
Mar 28 14:58:40 sogod [50]: <0x0x7f8742dca788[SOGoCache]> Using host(s) 'localhost' as server(s)
Mar 28 14:58:40 sogod [50]: [ERROR] <0x0x7f8742c69a28[NGBundleManager]> could not create bundle for path: '/usr/share/GNUstep/Libraries/gnustep-base/Versions/1.24/Resources/SSL.bundle'
Mar 28 14:58:40 sogod [50]: [WARN] <0x0x7f874043a3c0[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder
EXCEPTION: <NSException: 0x7f87431d2658> NAME:NSInvalidArgumentException REASON:Can not determine type information for -[GSMutableString (null)] INFO:(null)
Mar 28 14:58:40 sogod [24]: <0x0x7f8742e68488[WOWatchDogChild]> child 50 exited
Mar 28 14:58:40 sogod [24]: <0x0x7f8742e68488[WOWatchDogChild]> (terminated due to signal 6)
Mar 28 14:58:40 sogod [24]: <0x0x7f8742e35578[WOWatchDog]> child spawned with pid 164Seems it cannot connect to MySQL. Although i checked and the mysql account is there. Also the socket path is correct and the socket file exists...
Also the socket seems to be open:
I have solved the mysql error messages on the sogo backend. The sogo log looks good now.
Unfortunately i still cannot access the sogo web frontend. Error stays the same as described above.
Mar 28 15:36:01 sogod [25]: version 2.3.9 (build @shiva.inverse 201603161352) -- starting
Mar 28 15:36:01 sogod [25]: vmem size check enabled: shutting down app when vmem > 384 MB
Mar 28 15:36:01 sogod [25]: <0x0x7f19126600f8[SOGoProductLoader]> SOGo products loaded from '/usr/lib/GNUstep/SOGo':
Mar 28 15:36:01 sogod [25]: <0x0x7f19126600f8[SOGoProductLoader]> MainUI.SOGo, MailPartViewers.SOGo, PreferencesUI.SOGo, Contacts.SOGo, CommonUI.SOGo, Mai$
Mar 28 15:36:01 sogod [25]: <0x0x7f191270d578[WOWatchDog]> listening on 127.0.0.1:20000
Mar 28 15:36:01 sogod [25]: <0x0x7f191270d578[WOWatchDog]> watchdog process pid: 25
Mar 28 15:36:01 sogod [25]: <0x0x7f1910ca96a0[WOWatchDogChild]> watchdog request timeout set to 10 minutes
Mar 28 15:36:01 sogod [25]: <0x0x7f191270d578[WOWatchDog]> preparing 1 children
Mar 28 15:36:01 sogod [25]: <0x0x7f191270d578[WOWatchDog]> child spawned with pid 51I don't know anything about sogo. So, not much help here.
Ok. I have another question for you then...maybe you can help there.
This sogo docker container comes with sogo and an integrated apache2 webserver. As I am using NGINX now i don't want the container to start the Apache2 server. How can i prevent the docker container from doing that?
Not sure about docker since I don't use it but update-rc.d -f apache2 remove usually does it. Not sure where you execute that either.
You don't want to execute that on the OMV box. I know that for sure.
Thanks for your support. I will keep trying to get this running. If anyone else might have some ideas for me...i would be glad.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!