You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a custom domain for onlyoffice and you need to expose the service using a reverse proxy, the domain can't be reached because the index.go file for the onlyoffice plugin is using a relative path instead of the full url + path, causing this error on selfhosted failstash instances.
Step by step instructions to reproduce the bug
Set the custom domain url to ONLYOFFICE_URL=
Map onlyoffice ports to host.
Add a proxy host for the doman, host ip and the exposed port.
Can you replicate that error from the demo?
No, only selfhosted filestash instances with reverse proxy are affected
filestash couldn't find my api.js file in my onlyoffice server because it was using a relative path and not my full domain name url. By updating line 414 in server/plugin/plg_editor_onlyoffice/index.go to an absolute path that included my domain (hard coded), it started working.
Expected behavior
edit the code to handle external onlyoffice servers if configured/specified in the docker compose file.
The text was updated successfully, but these errors were encountered:
Description of the bug
If you have a custom domain for onlyoffice and you need to expose the service using a reverse proxy, the domain can't be reached because the
index.go
file for the onlyoffice plugin is using a relative path instead of the full url + path, causing this error on selfhosted failstash instances.Step by step instructions to reproduce the bug
Set the custom domain url to
ONLYOFFICE_URL=
Map onlyoffice ports to host.
Add a proxy host for the doman, host ip and the exposed port.
Can you replicate that error from the demo?
No, only selfhosted filestash instances with reverse proxy are affected
Observed behavior
Source
Expected behavior
The text was updated successfully, but these errors were encountered: