# Turn on debug output in SVN

DevFeed: [Turn on debug output in SVN](<https://devfeed.tech/articles/turn-on-debug-output-in-svn-35477.md>)

Original publisher: [Read original article](<https://darkcoding.net/software/turn-on-debug-output-in-svn/>)

Author: Graham King

Published: 2009-05-07T23:02:38Z

Content type: tutorial

Language: en

Sources: [Graham King](<https://devfeed.tech/sources/graham-king.md>)

Topics: [debug](<https://devfeed.tech/topics/debug.md>), [client](<https://devfeed.tech/topics/client.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [repo](<https://devfeed.tech/topics/repo.md>), [scheme](<https://devfeed.tech/topics/scheme.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [client](<https://devfeed.tech/tags/client.md>), [debug](<https://devfeed.tech/tags/debug.md>), [repo](<https://devfeed.tech/tags/repo.md>), [scheme](<https://devfeed.tech/tags/scheme.md>), [software](<https://devfeed.tech/tags/software.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

## AI overview

A troubleshooting guide explains how to enable Subversion debug output when an SVN client repeatedly requests credentials after a desktop and server upgrade. The reported cause involves an Apache AuthDigestDomain configuration that requires a scheme, although the relevant commands and full configuration values are missing from the supplied text.

## Source excerpt

After a desktop and server upgrade, my subversion client stopped working. I am using Digest authentication, and it kept asking me for the username and password. Wireshark showed me that the SVN client wasn't sending the Authentication header. To find out more, I turned on Subversion's debug output. Here's how you do it: Edit Add this line at the end: That showed me this error: This means that the path I was requesting (the root of the repo) was not considered inside the I had set in Apache.