SOGO webpage error

Hi. In NS 7 I have installed SOGO and afer tring to login, this error become:

What’s wrong?

Hi @Miko what is the IP Address of your Nethserver ?

Here is my configuration:

Soho isn’t running

Check the service status with

systemctl status sogo

Also check sogo.log

hm…
systemctl status sogo
â sogo.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

systemctl restart sogo
Failed to restart sogo.service: Unit sogo.service failed to load: No such file or directory.

SOGo is installed.

And in sogo.log not found any error.

systemctl status sogod.service

Check these logs:

  • /var/log/httpd/error_log
  • /var/log/httpd/ssl_error_log

Can you access from green zone using the private IP? and with the FQDN?

No I can’t access from green zone.

[root@server1 ~]# systemctl status sogod.service
â sogod.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2016-08-09 08:47:45 CEST; 5 days ago
Main PID: 9110 (sogod)
CGroup: /system.slice/sogod.service
ââ 9110 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
ââ17982 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
ââ17985 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log
ââ17988 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

/var/log/httpd/error_log:
[Mon Aug 15 03:34:07.868695 2016] [auth_digest:notice] [pid 2009] AH01757: generating secret for digest authentication …
[Mon Aug 15 03:34:07.885050 2016] [lbmethod_heartbeat:notice] [pid 2009] AH02282: No slotmem from mod_heartmonitor
[Mon Aug 15 03:34:07.952430 2016] [ssl:warn] [pid 2009] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Mon Aug 15 03:34:11.219357 2016] [mpm_prefork:notice] [pid 2009] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 configured – resuming normal operations
[Mon Aug 15 03:34:11.219398 2016] [core:notice] [pid 2009] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[Mon Aug 15 07:00:54.657636 2016] [autoindex:error] [pid 20523] [client 194.28.115.233:59315] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and se$
[Mon Aug 15 07:56:13.146899 2016] [core:error] [pid 20525] [client 81.89.62.62:19855] AH00126: Invalid URI in request \xdcI\x06oC\xd0\xfc\xb9\x0c4{\xba\xc3\xb0\xf6m\xb4\xa9eTRX\x1a

/var/log/httpd/ssl_error_log:
[Mon Aug 15 03:34:07.951983 2016] [ssl:warn] [pid 2009] AH01906: RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Aug 15 03:34:07.952020 2016] [ssl:warn] [pid 2009] AH01909: RSA certificate configured for server1.maxcomputers.sk:443 does NOT include an ID which matches the server name
[Mon Aug 15 03:34:07.952326 2016] [ssl:warn] [pid 2009] AH01906: RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Aug 15 03:34:07.952337 2016] [ssl:warn] [pid 2009] AH01909: RSA certificate configured for server1.maxcomputers.sk:443 does NOT include an ID which matches the server name
[Mon Aug 15 08:02:12.534593 2016] [proxy_http:error] [pid 20526] (20014)Internal error: [client 192.168.3.169:25799] AH01102: error reading status line from remote server 127.0.0.1:20000
[Mon Aug 15 08:02:12.646729 2016] [proxy_http:error] [pid 20522] (20014)Internal error: [client 192.168.3.169:25800] AH01102: error reading status line from remote server 127.0.0.1:20000
[Mon Aug 15 08:02:12.646795 2016] [proxy:error] [pid 20522] [client 192.168.3.169:25800] AH00898: Error reading from remote server returned by /SOGo/
[Mon Aug 15 08:02:25.778233 2016] [proxy_http:error] [pid 20523] (20014)Internal error: [client 192.168.3.169:25816] AH01102: error reading status line from remote server 127.0.0.1:20000
[Mon Aug 15 08:02:25.778299 2016] [proxy:error] [pid 20523] [client 192.168.3.169:25816] AH00898: Error reading from remote server returned by /SOGo/

Did you edit the Self-Signed Certificate according to your server settings?

No. Edit nothing in certificates.

Edit your CA and then verify /var/log/httpd/ssl_error_log, as @dnutan said, to be no errors regarding CA.

After that, import it in your browser and try again.

I have edited certificate, but there is still error. What can I do?

[Mon Aug 15 09:09:05.925200 2016] [proxy_http:error] [pid 2152] (20014)Internal error: [client 192.168.3.169:6098] AH01102: error reading status line from remote server 127.0.0.1:20000
[Mon Aug 15 09:09:06.003956 2016] [proxy_http:error] [pid 2148] (20014)Internal error: [client 192.168.3.169:6100] AH01102: error reading status line from remote server 127.0.0.1:20000
[Mon Aug 15 09:09:06.004047 2016] [proxy:error] [pid 2148] [client 192.168.3.169:6100] AH00898: Error reading from remote server returned by /SOGo/

Please check your firewall rules.
Make a temporary rule like this: Allow all from green to anywhere or Allow all from anywhere to anywhere to see if you can access from GREEN.

(Sorry, I don’t have access now to a NethServer installation to be more precisely.)

Let’s recap (please correct me where I’m wrong):

  1. Your RED IP is 212.5.194.230
  2. Your GREEN IP is 192.168.3.1
  3. SOGo is installed on NS as local (127.0.0.1)
  4. You cannot access / reach SOGo from RED - to do this, you must use Reverse Proxy
  5. You cannot access / reach SOGo from GREEN - try this: https://127.0.0.1/SOGo

@GG_jr configuration is as you write. But how can I try https://127.0.0.1/SOGo ? I don’t have gui installed on server…

Sorry!
You are absolutely right! Zentyal …

FYI… the same configuration I used on NS6.7 and SOGO was working

Not the best method, but you could try if you get a response from CLI (either with curl or with a text browser like lynx).

Example using curl to get connection details (discarding the html output):

curl -kvIL https://127.0.0.1/SOGo/

isn’t it an alias of GREEN interface?

You are right!

That IP should be on RED.
I have looked only on browser.
Something is wrong there, isn’t?

Hi @Miko10,

You should make the corrections, as @dnutan has observed:

  1. RED IP: 212.5.194.230
  2. GREEN IP: 192.168.3.1

After that, please try again to access SOGo.

1 Like