extern/egroupware_official
1
0
Fork 0
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-21 23:43:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

typos

Ralf Becker 2019-09-15 11:45:59 +02:00
parent ad043b5c28
commit 617c21bf2e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Update-recommendations-and-troubleshooting.md

@ -63,7 +63,7 @@ egroupware | [06-Sep-2019 10:41:13] NOTICE: ready to handle connections
egroupware | [06-Sep-2019 10:41:13] NOTICE: systemd monitor interval set to 10000ms
egroupware-watchtower | time="2019-09-15T07:11:12Z" level=info msg="Waiting for running update to be finished..."
```
If you don't see the line ```fpm is running, pid 1``` you will will only get a 503 from Nginx, when you try to connect to EGroupware. The startup of the egroupware container might take a little longer then you expect, as it has to copy the EGroupware sources into a volume with is shared with Nginx, so the webserver can deliver static files (CSS, JavaScript, images, ...).
If you don't see the line ```fpm is running, pid 1``` you will will only get a 503 from Nginx, when you try to connect to EGroupware. The startup of the egroupware container might take a little longer then you expect, as it has to copy the EGroupware sources into a volume which is shared with Nginx, so the webserver can deliver the static content (CSS, JavaScript, images, ...).
3. Try to connect to EGroupware container without using the proxy running on the host webserver. We use a tool called ```curl``` for these kind of checks. Install it with ```apt install -y curl``` (or yum or zypper instead of apt depending on your distribution):
```