[GH-ISSUE #80] nginx: failed (99: Cannot assign requested address ←→ Unknown error: Press "OK" to return to document list. #42

Closed
opened 2026-02-26 09:35:29 +03:00 by kerem · 8 comments
Owner

Originally created by @roboto-cloud on GitHub (Nov 13, 2017).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/80

Hi, I get this error and use the examples:

https://github.com/ONLYOFFICE/document-server-proxy/blob/master/nginx/proxy-to-virtual-path.conf
https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud

Unknown error: Press "OK" to return to document list.

my nginx log:

[crit] 443#0: *14 connect() to [::1]:8080 failed (99: Cannot assign requested address) while connecting to upstream, client: 172.19.0.2, server: , request: "GET /2017-10-28-08-40/spellchecker/doc/93_1510537868/c/203/bot2j4ew/websocket HTTP/1.1", upstream: "http://[::1]:8080/doc/93_1510537868/c/203/bot2j4ew/websocket", host: "drive.roboto.cloud"

my scenario is:

onlyoffice←→nextcloud←→loadbalancer←→internet
nginx(80)←→nginx(80)←→traefik(443)←→internet
failed ←→ 200 ←→ 200
thanks in advance,
32689941-411b50be-c6ee-11e7-9d84-d9c2772f3ae4

Originally created by @roboto-cloud on GitHub (Nov 13, 2017). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/80 Hi, I get this error and use the examples: https://github.com/ONLYOFFICE/document-server-proxy/blob/master/nginx/proxy-to-virtual-path.conf https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud ### Unknown error: Press "OK" to return to document list. **my nginx log:** ` [crit] 443#0: *14 connect() to [::1]:8080 failed (99: Cannot assign requested address) while connecting to upstream, client: 172.19.0.2, server: , request: "GET /2017-10-28-08-40/spellchecker/doc/93_1510537868/c/203/bot2j4ew/websocket HTTP/1.1", upstream: "http://[::1]:8080/doc/93_1510537868/c/203/bot2j4ew/websocket", host: "drive.roboto.cloud"` **my scenario is:** onlyoffice←→nextcloud←→loadbalancer←→internet nginx(80)←→nginx(80)←→traefik(443)←→internet failed ←→ 200 ←→ 200 thanks in advance, ![32689941-411b50be-c6ee-11e7-9d84-d9c2772f3ae4](https://user-images.githubusercontent.com/32390825/32706716-76a88cd8-c81f-11e7-85cb-79921a46bc79.png)
kerem closed this issue 2026-02-26 09:35:29 +03:00
Author
Owner

@agolybev commented on GitHub (Nov 13, 2017):

Hi @roboto-cloud, I think it is proxying related issue. I'm not sure that proxying is fully supported by our nextcloud installation.
Could you verify whether docker-onlyoffice-owncloud work properly without proxying?

<!-- gh-comment-id:343858991 --> @agolybev commented on GitHub (Nov 13, 2017): Hi @roboto-cloud, I think it is proxying related issue. I'm not sure that proxying is fully supported by [our](https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud) nextcloud installation. Could you verify whether docker-onlyoffice-owncloud work properly without proxying?
Author
Owner

@roboto-cloud commented on GitHub (Nov 13, 2017):

Hi, thanks @agolybev!
yes, it is proxy related issue and I fix it adding one line and changing other line into nginx.conf file using your nextcloud example installation.

nginx.conf →→

	location ~* ^/ds-vpath/ {
                ....
                proxy_set_header X-Forwarded-Proto https;
                proxy_read_timeout 36000s;
        }

Regards!

<!-- gh-comment-id:344024234 --> @roboto-cloud commented on GitHub (Nov 13, 2017): Hi, thanks @agolybev! yes, it is proxy related issue and I fix it adding one line and changing other line into **_nginx.conf_** file using your [nextcloud example installation](https://github.com/ONLYOFFICE/docker-onlyoffice-owncloud). **_nginx.conf_** →→ ``` location ~* ^/ds-vpath/ { .... proxy_set_header X-Forwarded-Proto https; proxy_read_timeout 36000s; } ``` Regards!
Author
Owner

@agolybev commented on GitHub (Nov 14, 2017):

Hi @roboto-cloud, good news!
Also you could fix it by adding X-Forwarded-Proto header on traefik proxy server.

<!-- gh-comment-id:344188206 --> @agolybev commented on GitHub (Nov 14, 2017): Hi @roboto-cloud, good news! Also you could fix it by adding `X-Forwarded-Proto` header on traefik proxy server.
Author
Owner

@mattronix commented on GitHub (Dec 5, 2017):

@roboto-cloud Hi, Where did you apply that in the nginx of the document server or the nginx of the nextcloud?

<!-- gh-comment-id:349308195 --> @mattronix commented on GitHub (Dec 5, 2017): @roboto-cloud Hi, Where did you apply that in the nginx of the document server or the nginx of the nextcloud?
Author
Owner

@mattronix commented on GitHub (Dec 5, 2017):

@agolybev does setting X-Forwarded-Proto work on docker backend?

<!-- gh-comment-id:349308340 --> @mattronix commented on GitHub (Dec 5, 2017): @agolybev does setting X-Forwarded-Proto work on docker backend?
Author
Owner

@agolybev commented on GitHub (Dec 5, 2017):

Hi @mattronix,
If X-Forwarded-Proto header exists in the request, Document Server uses it value as a protocol, otherwise Document Server get protocol from request to make output link. Also X-Forwarded-Host has same functionality for host name in output link generating.
This feature is working in all Document Server versions including docker.

<!-- gh-comment-id:349317361 --> @agolybev commented on GitHub (Dec 5, 2017): Hi @mattronix, If `X-Forwarded-Proto` header exists in the request, Document Server uses it value as a protocol, otherwise Document Server get protocol from request to make output link. Also `X-Forwarded-Host` has same functionality for host name in output link generating. This feature is working in all Document Server versions including docker.
Author
Owner

@mattronix commented on GitHub (Dec 6, 2017):

Ah understood thank you, makes sense.

<!-- gh-comment-id:349711010 --> @mattronix commented on GitHub (Dec 6, 2017): Ah understood thank you, makes sense.
Author
Owner

@fredleb commented on GitHub (Mar 6, 2021):

Hi @roboto-cloud, good news!
Also you could fix it by adding X-Forwarded-Proto header on traefik proxy server.

Here is an example of that solution:
https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/151#issuecomment-757392562

This has indeed solved the problem for me.

<!-- gh-comment-id:791920668 --> @fredleb commented on GitHub (Mar 6, 2021): > Hi @roboto-cloud, good news! > Also you could fix it by adding `X-Forwarded-Proto` header on traefik proxy server. Here is an example of that solution: https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/151#issuecomment-757392562 This has indeed solved the problem for me.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#42
No description provided.