| 76 | | If you are attempting to access a daemon `deluged` on the same machine but they are running as different users. e.g. your login user is `user` and the daemon is running as `deluge` they are likely using different config locations. This will prevent accessing the daemon because when both client and daemon are localhost, they attempt to automatically authorise using the config auth files, which are assumed to be at the same location. The workaround is to replace the `localclient` line in your user config `auth` file with the `localclient` line from the `deluged` config `auth` file . |
| | 76 | When attempting to access a daemon `deluged` on the same machine but running as a different user e.g. your login user is `user` and `deluged` is running as `deluge`, you may be unable access to `deluged`. This is due to the client automatically authorising using the localhost line in the auth file, which is assumed to be at the same config location as `deluged`. |
| | 77 | |
| | 78 | The workaround is to replace the `localclient` line in your user config auth file (`~/.config/deluge/auth`) with the `localclient` line from the `deluged` config `auth` file e.g. `/var/lib/deluge/auth`. |
Deluge
