`502 Bad Gateway` response

Issues during installation, usage and configuring
Post Reply
PascalB
Posts: 3
Joined: Mon Oct 21, 2019 7:29 am

`502 Bad Gateway` response

Post by PascalB » Mon Oct 21, 2019 7:44 am

Hello,

i have just installed Nextcloud 16 with Centos 7.6 (fresh install) and i have an issue with Onlyoffice integration (installed on another machine), error message :
Server error: 

HealthcheckRequest on check error: Server error: `GET https://onlyoffice.local.lan/healthcheck` resulted in a `502 Bad Gateway` response: <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>ngin (truncated...)

Do you have an idea ?
i'm working on this issue since 1 week and i'm going to become crazy :) :)

tell me if you need some of my config files to help me !

Thanks to all

Carl
Posts: 316
Joined: Thu Apr 12, 2018 10:00 am

Re: `502 Bad Gateway` response

Post by Carl » Mon Oct 21, 2019 2:24 pm

Hello PascalB,

Please check if all DS services function correctly:

Code: Select all

supervisorctl status all
Also check the accessibility of NC and DS to each other:
  • run

    Code: Select all

    wget https://nextcloud-address
    on the server with DS (if it is a docker installation, run the command inside the container)
  • run

    Code: Select all

    wget https://document-server-address
    on the server with NC.

PascalB
Posts: 3
Joined: Mon Oct 21, 2019 7:29 am

Re: `502 Bad Gateway` response

Post by PascalB » Mon Oct 21, 2019 3:37 pm

Hello Carl,
supervisorctl status all :

ds:converter FATAL Exited too quickly (process log may have details)
ds:docservice FATAL Exited too quickly (process log may have details)
ds:gc FATAL Exited too quickly (process log may have details)
ds:metrics RUNNING pid 4871, uptime 1:24:58
ds:spellchecker FATAL Exited too quickly (process log may have details)

From DS to NC :

wget https://infocloud.local.lan
--2019-10-21 17:34:27-- https://infocloud.local.lan/
Connexion vers 10.0.0.40:3128...connecté.
requête Proxy transmise, en attente de la réponse...302 Found
Emplacement: https://infocloud.local.lan/index.php/login [suivant]
--2019-10-21 17:34:28-- https://infocloud.local.lan/index.php/login
Connexion vers 10.0.0.40:3128...connecté.
requête Proxy transmise, en attente de la réponse...200 OK
Longueur: 5813 (5,7K) [text/html]
Sauvegarde en : «index.html»

100%[=====================================================================================================================================================================>] 5 813 --.-K/s ds 0s

2019-10-21 17:34:28 (186 MB/s) - «index.html» sauvegardé [5813/5813]

From NC to DS :
wget https://onlyoffice.local.lan
--2019-10-21 17:35:15-- https://onlyoffice.local.lan/
Résolution de proxy-smtp.local.lan (proxy-smtp.local.lan)... 10.10.0.6
Connexion vers proxy-smtp.local.lan (proxy-smtp.local.lan)|10.10.0.6|:3128...connecté.
requête Proxy transmise, en attente de la réponse...302 Moved Temporarily
Emplacement: https://onlyoffice.local.lan/welcome/ [suivant]
--2019-10-21 17:35:20-- https://onlyoffice.local.lan/welcome/
Connexion vers proxy-smtp.local.lan (proxy-smtp.local.lan)|10.10.0.6|:3128...connecté.
requête Proxy transmise, en attente de la réponse...502 Bad Gateway
2019-10-21 17:35:20 ERREUR 502: Bad Gateway.

Thanks for you help !

Carl
Posts: 316
Joined: Thu Apr 12, 2018 10:00 am

Re: `502 Bad Gateway` response

Post by Carl » Thu Oct 24, 2019 3:17 pm

Hello PascalB,

Your Document Server is not working at all. Please try to restart its services:

Code: Select all

supervisorctl restart all
Also check if logs contain any error entries: /var/log/onlyoffice/documentserver/

Post Reply