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
lool@collabora-online-667b8bd6bc-nqrp6:/$ cat /etc/loolwsd/loolwsd.xml | grep server_name
<server_name desc="External hostname:port of the server running loolwsd. If empty, it's derived from the request (please set it if this doesn't work). Must be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default="">https://collabora.domain.com:443</server_name>
Relevant logs and/or screenshots
Environment
Image version / tag: build from master
Host OS:
Details
When there is no value for server_name in /etc/loolwsd/loolwsd.xml hostname will be used by default. Nextcloud accessing collabora by url (https://collabora.domain.com:443), but collabora container reports, that request should be routed to `collabora-online-667b8bd6bc-nqrp6` (hostname). In local infrastructure it can be solved by editing /etc/hosts, but not in production, when there is ingress-controller in front.
lool@collabora-online-667b8bd6bc-nqrp6:/$ cat /etc/loolwsd/loolwsd.xml | grep server_name
<server_name desc="External hostname:port of the server running loolwsd. If empty, it's derived from the request (please set it if this doesn't work). Must be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default="">collabora-online-667b8bd6bc-nqrp6</server_name>
Possible fixes
add $server_name variable into config, pass it inside /etc/loolwsd/loolwsd.xml
The text was updated successfully, but these errors were encountered:
Summary
Steps to reproduce
What is the expected correct behavior?
Relevant logs and/or screenshots
Environment
Details
When there is no value for server_name in /etc/loolwsd/loolwsd.xml hostname will be used by default. Nextcloud accessing collabora by url (https://collabora.domain.com:443), but collabora container reports, that request should be routed to `collabora-online-667b8bd6bc-nqrp6` (hostname). In local infrastructure it can be solved by editing /etc/hosts, but not in production, when there is ingress-controller in front.Possible fixes
add $server_name variable into config, pass it inside /etc/loolwsd/loolwsd.xml
The text was updated successfully, but these errors were encountered: