[GH-ISSUE #3222] Routing collabora code through NPM to NextCloud (Solved) #2177

New issue

Closed

opened 2026-02-26 07:34:22 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:34:22 +03:00

Owner

Originally created by @ken8521 on GitHub (Sep 28, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3222

This might be outside the support mechanism here, but I've used this outside NPM (with linuxserver swag) and it worked fine... I've routed all my containers through NPM, and they all work fine, except for collabora. With swag, it worked no problem. Nextcloud sees my collabora server and reports that it can reach it, but when I try to open a document (I know the document works, as I created it in collabora with swag)..

I get this error over and over

00001-00034 2023-09-28 08:04:35.381070 +0000 [ websrv_poll ] ERR #24: #24 bad request: [GET /cool/https%3A%2F%2Fnextcloud.mydomain.tld%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F1396_instanceid%3Faccess_token%3DK3Y7Xpq3TmuRtipegaq3T0zVH4h3LBXg%26access_token_ttl%3D0%26permission%3Dedit/ws?WOPISrc=https%3A%2F%2Fnextcloud.mydomain.tld%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F1396_instanceid&compat=/ws HTTP/1.1
...]: Invalid or unknown request.| wsd/COOLWSD.cpp:4061

I can reach the domain via collabora.mydomain.tld and get the traditional "OK" which confirms the server is working. Nextcloud reports that the server is online and reachable. In the past, this pretty much ment NC Office was working fine.

My compose for collabora is relatively simple...

version: "2.2"
services:
collabora:
image: collabora/code
container_name: collabora
environment:
- aliasgroup1=https://nextcloud.mydomain.xyz
- dictionaries=en_US
ports:
- 9980:9980
restart: unless-stopped

Any help or suggestions on this would be greatly appreciated.

Originally created by @ken8521 on GitHub (Sep 28, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3222 This might be outside the support mechanism here, but I've used this outside NPM (with linuxserver swag) and it worked fine... I've routed all my containers through NPM, and they all work fine, except for collabora. With swag, it worked no problem. Nextcloud sees my collabora server and reports that it can reach it, but when I try to open a document (I know the document works, as I created it in collabora with swag).. I get this error over and over 00001-00034 2023-09-28 08:04:35.381070 +0000 [ websrv_poll ] ERR #24: #24 bad request: [GET /cool/https%3A%2F%2Fnextcloud.mydomain.tld%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F1396_instanceid%3Faccess_token%3DK3Y7Xpq3TmuRtipegaq3T0zVH4h3LBXg%26access_token_ttl%3D0%26permission%3Dedit/ws?WOPISrc=https%3A%2F%2Fnextcloud.mydomain.tld%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F1396_instanceid&compat=/ws HTTP/1.1 ...]: Invalid or unknown request.| wsd/COOLWSD.cpp:4061 I can reach the domain via collabora.mydomain.tld and get the traditional "OK" which confirms the server is working. Nextcloud reports that the server is online and reachable. In the past, this pretty much ment NC Office was working fine. ![86](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/55791402/3eda806e-574f-40b3-97d1-10f7ccb025af) My compose for collabora is relatively simple... version: "2.2" services: collabora: image: collabora/code container_name: collabora environment: - aliasgroup1=https://nextcloud.mydomain.xyz - dictionaries=en_US ports: - 9980:9980 restart: unless-stopped Any help or suggestions on this would be greatly appreciated.

kerem closed this issue

2026-02-26 07:34:22 +03:00

kerem commented

2026-02-26 07:34:22 +03:00

Author

Owner

@ken8521 commented on GitHub (Sep 28, 2023):

For anyone who comes across this in a search, this matter is Solved. You have to put your public IP in the WOPI section in NC. Never had to do that before.

https://old.reddit.com/r/nginxproxymanager/comments/16uar87/npm_nextcloud_and_collabora_nextcloud_cannot/

@ken8521 commented on GitHub (Sep 28, 2023): For anyone who comes across this in a search, this matter is Solved. You have to put your public IP in the WOPI section in NC. Never had to do that before. https://old.reddit.com/r/nginxproxymanager/comments/16uar87/npm_nextcloud_and_collabora_nextcloud_cannot/

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/nginx-proxy-manager-NginxProxyManager#2177

No description provided.

Rows
Columns