Applies to

DocuWare on-premises. 7.3–7.9; the source describes behavior introduced in 7.3.

What to check

Older configurations can mix an external HTTPS address with internal HTTP endpoints. A scheme mismatch in Document Processing or Smart Connect therefore needs a review of the whole request path.

Practical steps

  • Back up the relevant configuration files and record the public and internal URLs.
  • Have the administrator compare LocalWebServices, DocCap settings, inherited rewrite rules and the internal web connection against the linked procedure.
  • Review the IIS binding requirements specifically for the installed release before changing redirects or SSL enforcement.

Confirm the result

Reopen the affected configuration module and verify external HTTPS access still works. These legacy settings should not be copied into a modern deployment without release-specific confirmation.