Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button.  The answer will now appear with a checkmark.  Please be sure to always mark answers that resolve your issue as verified.  Your fellow Community members will appreciate it!  Learn more.

  • State Not Answered
  • Replies replies
    14
  • Subscribers subscribers
    14
  • Views views
    1492
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Content Editor behind Nginx

Dariusz Leonarski
 

Hello Forum,

I found similar question community.microfocus.com/.../2705014 but NAM differs a bit from Nginx.

Like in the mentioned thread I see empty screen only or (with a bit different Nginx settings) a popup message that "CE was not able to read document. Please contact admin". Inside "LAN" CE works fine.

In the context of other project I'm able to manage WebSocket traffic via Nginx as a reverse proxy.

I tried to copy & modify these setttings but without positive results.

Any ideas would be appreciated.

 

Regards, Dariusz

  • 0   in reply to 

    Filr wants to use an external ce dns name to offer ce functionality. So Filr should be able to access CE using a dns information without passing a proxy. ;-) (maybe use your internal DNS server to handle this or your local Filr hosts file).

    Users will get the whole path to access but will pass proxy every time.

    I still use the mentioned configuration file above.

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Finally we got it working...

    <IP address of ce appliance> <reverse proxy DNS name for ce>

    in /etc/hosts to persuade Filr to use the reverse proxy. But this still seems strange to me - how does this work? And - how can one figure that out? Many thanks for the tip!

    We had to change the location / section: we added

               proxy_set_header Upgrade $http_upgrade;
               proxy_set_header Connection "Upgrade";
               proxy_set_header Host $http_host;

    here too, otherwise it did not work.

    Thanks for helping!

  • 0   in reply to 

    I used tips for Collabora to get it running Innocent 

    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to   

    New CE needs new settings in nginx proxy settings. This example file will solve issues: https://help.univention.com/t/collabora-nextcloud-hinter-nginx-reverse-proxy/19871

    Use "Verified Answers" if your problem/issue has been solved!

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.