My case is very similar to https://dev.deluge-torrent.org/ticket/3197#no1
I tried workaround described there, it is not working.
I see error message when start deluge demon:
pi@<name>:~ $ deluged
pi@<name>:~ $ [ERROR ] 09:58:46 config:390 No JSON object could be
decoded
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/deluge/config.py", line 388, in
load
self.__config.update(json.loads(data[start:end]))
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
I am using Raspberry pi 4 with SW version(s):
deluged: 1.3.15
libtorrent: 1.1.11.0
OS:
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
Notes:
- deluge-web is working (but forgets path setting, it is different story).
- I configured deluge based on page https://pimylifeup.com/raspberry-pi-
deluge/
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3490>
Deluge <https://deluge-torrent.org/>
Deluge Project
Comment (by hazikimert):
I found the source of the issue, the ticket can be closed. core.conf line
""allow_remote": True," caused the issue, "true" shall be lower case and
deluged starts perfectly and remembers configuration.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3490#comment:1>
* status: new => closed
* resolution: => Invalid
Comment:
I think I saw you had a post in the forum that I meant to reply that it's
a corrupted config that results in that error.
Glad you figured it out!
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3490#comment:2>