Onlyoffice behind reverse proxy won't work (502 Bad Gateway) #711

artemis-mike · 2020-02-16T17:28:02Z

artemis-mike
Feb 16, 2020

Do you want to request a feature or report a bug?
It seems like a bug, but mostly I'd just like some help.

My setup

Ubuntu 18.04.4 LTS (Bionic Beaver) running
docker version 19.03.5, build 633a0ea838 running several containers
jwilder/nginx-proxy:0.7.0
jrcs/letsencrypt-nginx-proxy-companion:v1.12
nextcloud:18.01
onlyoffice/documentserver:5.4.2.46
and some other containers e.g. wordpress, db-servers, ...

What is the current behavior?
Except onlyoffice everything works like a charm. I got a sub-domain for every outgoing service (wordpress, nextcloud) handled by nginx-proxy. Now I wanted to add the onlyoffice-documentserver to my nextcloud.
I added a block to my docker-compose.yml-file stating
VIRTUAL_HOST=office.my-domain.tld
LETSENCRYPT_HOST=office.my-domain.tld
When I try to connect to onlyoffice in nextcloud it throws
Server error: GET https://office.my-domain.tld/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...)...

What is the expected behavior?
If I'm using purely the docker-compose-block of the onlyoffice/documentserver:latest omitting certificates and using plain HTTP it works perfectly and shows the beautiful page stating "Thank you for choosing ONLYOFFICE! Document Server is running [...]"
But including it into the reverse-proxy-environment results in that 502-Error.

DocumentServer Docker tag:
5.4.2.46

Host Operating System:
Ubuntu 18.04.4 LTS (Bionic Beaver) running docker 19.03.5

Docker-Compose-File Entry

#ONLYOffice
  onyloffice:
    restart: always
    stdin_open: true
    tty: true
    depends_on:
      - nginx-proxy
      - encryption-companion
    image: onlyoffice/documentserver:latest
    volumes:
      - './onlyoffice/var/log/onyloffice:/var/log/onyloffice'
      - './onlyoffice/var/www/onyloffice/data:/var/www/onyloffice/data'
    environment:
      - VIRTUAL_HOST=${ONLYOFFICE_HOST}
      - LETSENCRYPT_HOST=${ONLYOFFICE_HOST}
      - JWT_ENABLE=true
      - JWT_SECRET=${ONLYOFFICE_JWT_SECRET}
      - JWT_HEADER=Authorization
    networks:
      - mynetwork

I would prefer to run the documentserver within the single machine hosting everything else over docker. Instead of starting a separate server just for hosting onlyoffice.

ShockwaveNN · 2020-02-17T08:19:17Z

ShockwaveNN
Feb 17, 2020

@agolybev could you take a look?

0 replies

effatee · 2021-03-07T20:38:10Z

effatee
Mar 7, 2021

Hi there, did you ever solve this ? (running into the same issue...)

0 replies

artemis-mike · 2021-03-07T20:49:51Z

artemis-mike
Mar 7, 2021
Author

"Unfortunately" not. I eventually gave up and switched to collabora. It works like a charme.
I host a own Collabora CODE instance as container and connected it to my nextcloud.
The possibilities of collabora are a bit limited compared to onlyoffice. Well, of what I expected of Onlyoffice. I couldn't tell for sure, as I never got it to work at all.

0 replies

effatee · 2021-03-07T20:51:27Z

effatee
Mar 7, 2021

Thanks for your feedback. Damn frustrating... ;-)

0 replies

socram70 · 2022-09-09T05:49:04Z

socram70
Sep 9, 2022

I did experience the same issues here. I did figure out that the issue is not because of the reverse proxy, but because the server does not seem to listen to all IP addresses. I did map my docker-network-IP-Port 8081 to port 80 of the container (172.20.0.3:8081). However, that does only lead to connection refused if I do use wget in the shell to test it. It is working fine with 127.0.0.1:8081, but this address is somehow not reachable via my nginx-reverse-proxy-container on the same server.

Maybe someone has an idea here? I did change the env-variable for REDIS_SERVER_HOST to 172.20.0.3 already, but this does not help :-(

0 replies

agusdomin · 2023-03-15T16:40:58Z

agusdomin
Mar 15, 2023

Hi, same problem here.
I'm testing a onlyoffice document server hosted in my pc (Ubuntu 20). And i have a nextcloud server in a remote server (Centos 7)

I don't know if the problem come from onlyoffice server (nginx) or nextcloud server.

Someone solved it?

0 replies

agusdomin · 2023-03-16T11:12:22Z

agusdomin
Mar 16, 2023

I solved it, i cant belive what it was.

It was the default port of onlyoffice server, that is 8000, defined in /etc/onlyoffice/documentserver/default.json

"services": { "CoAuthoring": { "server": { "port": 8000, ...

EDIT:

A way to show document server port, on nextcloud server:

sudo -u apache php /var/www/html/nextcloud/occ onlyoffice:documentserver

0 replies

just-in-tech · 2023-09-08T01:09:26Z

just-in-tech
Sep 8, 2023

i am having the same issue
i have figure out when i access http://mydomain/healthcheck in a web browser it works no problem but when i use wget it just says server returned error: HTTP/1.1 502 Bad Gateway and same with nextcloud i was think it could be something like http versions but i don't know

edit just confirmed web browser is using HTTP/2 but wget is using HTTP/1.1

1 reply

just-in-tech Feb 15, 2024

i solved my issue by changing my dns setup what was happening was for some reason nextcloud was unable to resolve the domain onlyoffice was on and this was with traefik

thesorskod · 2023-12-20T03:45:54Z

thesorskod
Dec 20, 2023

I solved it, i cant belive what it was.

It was the default port of onlyoffice server, that is 8000, defined in /etc/onlyoffice/documentserver/default.json

"services": { "CoAuthoring": { "server": { "port": 8000, ...

EDIT:

A way to show document server port, on nextcloud server:

sudo -u apache php /var/www/html/nextcloud/occ onlyoffice:documentserver

how did you solve it?

0 replies

socram70 · 2023-12-20T07:11:24Z

socram70
Dec 20, 2023

@thesorskod you can do this by either mounting the config file and place your own file there (I wouldn't recommend this) or just map the port 8000 to anything you like via Docker.

0 replies

mwneuendorf · 2024-02-15T01:22:34Z

mwneuendorf
Feb 15, 2024

I'm not sure what update changed things. My nginx-proxy config was working before but now it's required to turn on Websockets Support in nginx-proxy.

0 replies

igwyd · 2024-02-15T08:50:20Z

igwyd
Feb 15, 2024

Hello, we have some examples for the reverse proxy settings, we recomend use it https://helpcenter.onlyoffice.com/installation/docs-community-proxy.aspx

0 replies

Rita-Bubnova · 2024-02-15T10:22:07Z

Rita-Bubnova
Feb 15, 2024
Collaborator

This doesn't look like an issue, so I'll convert to a discussion.

1 reply

mwneuendorf Feb 15, 2024

so why would it be a nginx proxy manager issue? if I see the behind ip healthecheck work and the forward ip work after a websocket update, is that not onlyoffice?

thesorskod · 2024-02-22T17:13:17Z

thesorskod
Feb 22, 2024

turns out for me it was cloudflare.

i had a Transform Rule that was modifying the reponse Header which was causing the issue.

i remove that rule and solve my issue.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Onlyoffice behind reverse proxy won't work (502 Bad Gateway) #711

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 14 comments 2 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Onlyoffice behind reverse proxy won't work (502 Bad Gateway) #711

Replies: 14 comments · 2 replies

artemis-mike Mar 7, 2021 Author

Rita-Bubnova Feb 15, 2024 Collaborator

Replies: 14 comments 2 replies

artemis-mike
Mar 7, 2021
Author

Rita-Bubnova
Feb 15, 2024
Collaborator