Nothing comes up and screen is flickering

[valsamis-d]

Describe the bug After installing and running as per the instruction, I was able to connect to _http://:3000_, but I don't see any of my torrents. Instead, the list comes up empty (Filter = ALL) and is flickering every 1-2 seconds or so.

Expected behavior I'm expecting to see my torrents and on the very top the appropriate info for my deluge deamon.

Device (please complete the following information):

• Devices Tested: iOS 17.0.3 and Windows 11
• Browser: Safari & Firefox (iOS), Firefox (Windows 11)
• Deluge version: 2.0.5

[maulik9898]

Can you provide me docker logs along with console log

[valsamis-d]

Thanks for replying @maulik9898 !

Can you please point me to the right direction for the docker logs?

Also, when you say console logs you mean NOT running it detached and see what messages are displayed?

[maulik9898]

Docker logs : https://docs.docker.com/engine/reference/commandline/logs/

Console logs means logs printed in the browser console.

[valsamis-d]

@maulik9898 attached. docker_logs.txt console-export-2023-10-6_21-22-23.txt

This time I used Windows 11 and Firefox 118.0.1

[maulik9898]

Can you give me the command that u used to run a docker container. And how did you generate NEXTAUTH_SECRET .?

[valsamis-d]

docker run \
  -p 3000:3000 \
  -e NEXTAUTH_SECRET=9eOro53um6a1OVoTwBvH6FUmTbNRu5byqybu0Oi36wA= \
  -e DELUGE_URL=http://localhost:8112 \
  -e DELUGE_PASSWORD=username \
  -e BARRAGE_PASSWORD=password \
  maulik9898/barrage

I generated NEXTAUTH_SECRET using:

openssl rand -base64 32

[maulik9898]

Can you use this command to generate NEXTAUTH_SECRET .

jose newkey -s 512 -t oct -a HS512

[valsamis-d]

-bash: jose: command not found

Would it be OK to install in OSMC (RPi2) using the following?

sudo apt-get -y install jose

Anyway, I did the above but there's something in the command that OSMC does not like:

osmc@VLSiOSMC:~$ jose newkey -s 512 -t oct -a HS512
Usage: jose COMMAND [OPTIONS] [ARGUMENTS]

Commands:

  jose alg      Lists all supported algorithms

  jose fmt      Converts JSON between serialization formats

  jose b64 dec  Decodes URL-safe Base64 data to binary
  jose b64 enc  Encodes binary data to URL-safe Base64

  jose jwe dec  Decrypts a JWE using the supplied JWKs and outputs plaintext
  jose jwe enc  Encrypts plaintext using one or more JWKs and outputs a JWE
  jose jwe fmt  Converts a JWE between serialization formats

  jose jwk eql  Determines if two or more JWKs are equal
  jose jwk exc  Performs a key exchange using the two input keys
  jose jwk gen  Creates a random JWK for each input JWK template
  jose jwk pub  Cleans private keys from a JWK
  jose jwk thp  Calculates the JWK thumbprint
  jose jwk use  Validates the permissions of a key for the specified use(s)

  jose jws fmt  Converts a JWS between serialization formats
  jose jws sig  Signs a payload using one or more JWKs and outputs a JWS
  jose jws ver  Verifies a JWS using the supplied JWKs and outputs payload

[valsamis-d]

@maulik9898 I think I know where I messed up and am getting the 'decryption operation failed'.

When I first installed Barrage I did it exactly as the installation instructions and used NEXTAUTH_SECRET=secret . Somehow, this value persist somewhere and I have to stick with it :(

When I start again with NEXTAUTH_SECRET=secret I don't get the decryption operation failed'. Here's what I see:

osmc@VLSiOSMC:~$ docker logs 006fd7a87a2b
Listening on port 3000 url: http://localhost:3000
[next-auth][warn][NEXTAUTH_URL]
https://next-auth.js.org/warnings#nextauth_url
osmc@VLSiOSMC:~$

However, the issue with the blank screen and the flickering persists. Also, I'm attaching a fresh set of browser logs.

console-export-2023-10-6_22-1-36.txt

[maulik9898]

U need to clear browser cache

[valsamis-d]

U need to clear browser cache

Super! Now I'm using a more appropriate NEXTAUTH_SECRET ;) Behavior is the same as my previous message.

[maulik9898]

If you are still facing an issue then remove the docker container using docker rm containername . And try opening the link in incognito