Opened 3 years ago

Closed 3 years ago

#3490 closed bug (Invalid)

Deluge cannot start - No JSON object could be decoded

Reported by: hazikimert Owned by:
Priority: major Milestone: needs verified
Component: Unknown Version: 1.3.15
Keywords: Cc:



My case is very similar to 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/", line 388, in load


File "/usr/lib/python2.7/json/", line 339, in loads

return _default_decoder.decode(s)

File "/usr/lib/python2.7/json/", line 364, in decode

obj, end = self.raw_decode(s, idx=_w(s, 0).end())

File "/usr/lib/python2.7/json/", 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:

OS: PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"


Change History (2)

comment:1 by hazikimert, 3 years ago

Summary: Deluge cannot startDeluge cannot start - No JSON object could be decoded

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.

comment:2 by Calum, 3 years ago

Resolution: Invalid
Status: newclosed

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!

Note: See TracTickets for help on using tickets.