Add desktop troubleshooting page and iOS WebDAV cloud management section

Author: tobihagemann

docs/desktop/troubleshooting.md

@@ -0,0 +1,40 @@
+---
+id: troubleshooting
+title: Troubleshooting
+sidebar_position: 14
+---
+
+# Troubleshooting
+
+This page contains solutions for common issues you might encounter when using Cryptomator on desktop platforms.
+
+## Log File Locations {#log-file-locations}
+
+Cryptomator creates log files to help with troubleshooting when issues occur. The default locations for these log files vary by operating system:
+
+| Operating System | Default Log File Location                    |
+| :--------------- | :------------------------------------------- |
+| Windows          | `%appdata%\Cryptomator\cryptomator.log`      |
+| macOS            | `~/Library/Logs/Cryptomator/cryptomator.log` |
+| Linux            | `~/.Cryptomator/cryptomator.log`             |
+
+You can change the log file directory by setting the `cryptomator.logDir` property in the [advanced configuration](advanced-settings.md). This allows you to store log files in a custom location if needed.
+
+## Debug Mode {#debug-mode}
+
+Debug mode enables additional diagnostic logging to help troubleshoot issues with Cryptomator. When debug mode is active, the application records more detailed information about its operations in the log files.
+
+:::warning Privacy Consideration
+With debug mode enabled, the paths of all files you encrypt are stored in the log file. This creates a record of your file and folder names, which may compromise privacy. Only enable debug mode when actively troubleshooting an issue, and remember to disable it afterward.
+:::
+
+To enable debug mode:
+
+1. Open Cryptomator and navigate to the settings
+2. Look for the `Enable debug logging` checkbox and enable it
+
+The additional debug information will now be written to your log files. Once you have reproduced the issue you're investigating, disable debug mode by unchecking the option to return to normal logging levels.
+
+## Known Issues {#known-issues}
+
+For a list of known issues, please refer to the [Cryptomator Community](https://community.cryptomator.org/c/help/known-issues/16) or [GitHub Issues page](https://github.com/cryptomator/cryptomator/issues).

docs/ios/cloud-management.md

@@ -6,6 +6,22 @@ sidebar_position: 2
 
 # Cloud Management
 
+## WebDAV {#webdav}
+
+Please see [Cloud Services With WebDAV Support](/docs/misc/supported-cloud-services.md#cloud-services-with-webdav-support) for a non-exhaustive list of Cloud Services and information about accessing them with WebDAV.
+
+:::note
+While creating the WebDAV connection, please make sure to add the root of the accessible storage and don't navigate directly into the vault.
+:::
+
+If you encounter the `Request method not supported by the target resource.` error, it means that the WebDAV URL entered is invalid or the server doesn't support WebDAV properly.
+
+To resolve this:
+1. Verify you're using the correct WebDAV URL for your cloud service
+2. Check the [list of supported cloud services](/docs/misc/supported-cloud-services.md#cloud-services-with-webdav-support) for the correct WebDAV URLs
+3. Ensure your cloud provider has WebDAV enabled (some require enabling it in account settings)
+4. If using 2FA, you might need to generate an app-specific password for WebDAV access
+
 ## Other File Provider {#other-file-provider}
 
 This option allows you to add a vault from any supported [file provider](https://developer.apple.com/documentation/fileprovider/). Default implementations by Apple are iCloud Drive and On My iPhone/iPad. Inside the Files app, you can also add custom connections to SMB-compatible servers.