File previewer plugin not displaying document



  • Hi All,

    I am newby to this forum, so please excuse lack of knowledge re Kopano in advance.

    We have installed File previewer plug and Seafile plugin (with success).

    Our issue is that we are unable to view documents and when reviewing the logs notice that there is no files downloaded into /var/lib/kopano-webapp/tmp/ for viewerjs to open.

    In the Apache error log we see the follow;
    [BACKEND_WEBDAV]: [GET_FILE] local path (/var/lib/kopano-webapp/tmp/L015IExpYnJhcnkvckROUyBlcnJvci5ydGY=Uh0nQa) writeable: 1

    Also note that java console in browser displaying an error, not sure if its related (changed fqdn);
    BUILD-debug.js:857 PUT https://example.com/webapp/presence 405 (Method Not Allowed)

    Any assistance would be very much appreciated.

    Cheers
    Geoff


  • Kopano

    Hi @pdcadmin
    Could you share the permissions set on that tmp folder?

    This link might help for presence configuration:
    https://documentation.kopano.io/web_meetings_manual/configuration.html#configuring-kopano-presence



  • Hi @marty

    Many thanks for your kind response.

    Below are the folder permissions;

    drwxr-xr-x 4 www-data www-data 4.0K Jul 12 15:40 /var/lib/kopano-webapp/tmp/

    getfacl: Removing leading ‘/’ from absolute path names

    file: var/lib/kopano-webapp/tmp/

    owner: www-data

    group: www-data

    user::rwx
    group::r-x
    other::r-x

    We will review suggested documentation for configs.

    Cheers
    Geoff



  • Hi @marty

    Double checked setting as recommended and still same results, no previewing of documents.

    Cheers
    Geoff



  • Hmmm… Just an idea that I got from one of my past issues with the filepreviewer… Is it possible that you set some Options suggested by some sites regarding https security? Maybe one called X-Frame-Options to something else than SAME-ORIGIN?
    Just try a grep for the mentioned option in your apache configuration and if it differs from SAME-ORIGIN set it to this and do some apache restart/reload. Afterwards fully reload your webapp

    Andreas


  • Kopano

    @pdcadmin

    Btw: the message in the error log is not an actually error, but a log message.


Log in to reply