Version 17 - 13.06.2019 - GoEdit Administrator|0 Comments|0 Attachments| More Details
Owner:
Categories:
Created:
11.08.2015
Tags:
Type:
Document
Visitors:
2390
Books:

Get logs for Confluence

To access the logs, go to Settings (the cog icon on the right top)General Configuration > Atlassian Support Tools.

If you cannot access logs via Support Tools, check the properties file at <confluence-installation>/confluence/WEB-INF/classes/confluence-init.properties, look for the confluence.home setting in that file, then find the logs in the Confluence home directory.

See here for further details on Confluence logging.

Optional: Enable debug-mode for GoEdit

To enable more verbose logging, please go to the GoEdit configuration page and open "Troubleshoot-Support"

  1. Click on "Debug Mode" -> Enable
    1. Hint: The Debug Mode will be automatically disabled upon a daemon restart of Confluence
  2. Export the Confluence logs like described above
  3. Do not forget to disable the Debug Mode if no longer needed

Fix GoEdit BasePath-Test warning 

Ensure your  Server-Base-URL is correctly configure (under admin/viewgeneralconfig.action )

But more importantly, you use Nginx/Apache in front of your Confluence (Tomcat)m, ensure your Connector settings in the server.xml is configured properly:

  1. Location:confluence/conf/server.xml
  2. Ensure you add this to your default Connector (port 8090 probably)
  3. Ensure you entered proxyName correctly

For HTTPS:

    proxyName="demo.goedit.io" proxyPort="443" scheme="https" secure="true"

        for HTTP

        proxyName="demo.goedit.io" proxyPort="80" scheme="http" secure="true"

        While Proxy-Name is the Domain you access Confluecen from using Nginx / Apache. Ensure in the end, your GoEdit Configuration page looks like this:

        1647

        Important, if you use different protocols or domains to access your Confluence or Jira, ensure, you create a specific connector with the correct proxyName for EACH of the domains you use

        Failed downloading the requested file

        1. Ensure you don't have a Base-Path-Test warning on your GoEdit-Configuration page: 
        2. Ensure the proxy is used by analyzing proxy request - ask your IT.
        3. Ensure you do not use any user-agent blocker on the web server.
        4. Ensure you do not use any non-cookie based authentication on the web server.
        5. After trying GoEdit and the download fails, try the download-link with the browser.
        6. Analyze your proxy requests, ensure the proxy is used (correctly).
        7. Check your web server logs for incoming requests (if they arrive) using debug mode.
        8. Check your confluence log for activity or exceptions.

        GoEdit fails uploading changed files to your server

        • Case A: If you have installed "Arsenale Lockpoint", please disable the plugin, restart your Confluence Server and reenable the plugin.
        • Case B: Microsoft Office has a protocol which tries to discover files, and like to save it through WebDAV instead of GoEdit.
          • You can deactivate the Protocol Discovery by using rewrite rules in Apache:

        # Intercept Microsoft Office Protocol Discovery
        RewriteCond %{REQUEST_METHOD} ^OPTIONS
        RewriteCond %{HTTP_USER_AGENT} ^Microsoft\ Office\ Protocol\ Discovery [OR]
        RewriteCond %{HTTP_USER_AGENT} ^Microsoft\ Office\ Existence\ Discovery [OR]
        RewriteCond %{HTTP_USER_AGENT} ^Microsoft\-WebDAV\-MiniRedir.*$
        RewriteRule .* - [R=405,L]

        Please consult your web server's documentation if you use a different server software than Apache.

        GoEdit does not react / is blocked by Content Security Policy (CSP)

        If your browser console alarms you about a Content Security Policy (CSP) issue like:

        Content Security Policy: The page’s settings blocked the loading of a resource...

        You have to allow your webserver to use the goedit header correctly. This may vary for every webserver. Here is an example for nginx:

        add_header Content-Security-Policy "default-src https: goedit: wss: 'unsafe-inline' 'unsafe-eval'; img-src https: data: 'unsafe-inline'" always;

        You may also consult the  Content Security Policy Reference.

        Upgrade issues from GoEdit 3 to GoEdit 4 

        In case you have been upgrading from GoEdit 3 to GoEdit 4 for, all your users will need to update their local installed GoEdit Native Client once - otherwise the Native Client will tell you, that it is not able to authenticate when you start the editing process.

          AttachmentDateSizeAction
          No attachments yet