Flood: "Cannot connect to rTorrent" loop on latest master

[etbusch]

Summary

The "Cannot connect to rTorrent" dialog pops up on app load and successfully tests the connection, and then proceeds to appear again when save is pressed.

Expected Behavior

The app should take the xmlrpc server information, save it, and continue loading the app.

Current Behavior

The "Cannot connect to rTorrent" dialog pops up and prompts me to enter in the ip and port the rtorrent xmlrpc server is listening on

I enter in the correct info and click "Test", and a checkmark appears.

I click submit, the dialog disappears momentarily, but then reappears with the information populated in the form.

This was working before I updated, and ruTorrent is currently working fine with the same rtorrent server. I reinstalled flood from scratch as well (with a fresh config.js) with the same result.

Possible Solution

Fix the bug, and perhaps be a little less strict on issue templates ;)

Steps to Reproduce (for bugs)

1. install flood
2. use a TCP connection to the rtorrrent xmlrpc server
3. attempt to use the app
4.

Context

This prevents the use of flood entirely on my setup

Your Environment

• Version used: e21ab29c8ed10a600ca316fb7e8a88006c5ca512
• Environment name and version (e.g. Chrome 39, node.js 5.4): nodeJS 8.9.2
• Operating System and version: Alpine Linux 3.7

[Roguyt]

Quoting @jfurrow on Discord, since i was having the same issue

8:50 PM] jfurrow: so in your case it's going to try to use the socket because it's not an empty string
[8:50 PM] jfurrow: sorry I'm not able to fully help but if you have access to the users db at server/db/users.db you can modify it directly, jsut remove the socketPath property on the user
[8:51 PM] jfurrow: then restart the Flood server and it should just work
[8:51 PM] jfurrow: I'll have to fix this later

[etbusch]

There aren't any properties named "socketPath" in the entries in users.db on my install.

[Roguyt]

Oh.
Well guess you'll have to wait for a reply from the team.

[rkkoszewski]

Same issue here inside a LXC container with the same setup: OS: Alpine Linux 3.7 NodeJS: 8.9.2 and latest commit.

[ghost]

I had the same issue

However, I'd like to add that I got mine working by just doing a reinstall.
Not sure what fixed it but I read a little bit more the second time, and didn't put in wrong information at any point.

Strangely the socket disconnect it self. So I had to restart flood, and it asked for the information again. So it seems something is causing it to want to discount at certain points

[noraj]

PS : @etbusch I know I'm boring but please respect the issue template next time ;)

[etbusch]

@noraj yes, you are boring.

[bbashy]

Edit: nvm, was at the bottom "I reinstalled flood from scratch as well (with a fresh config.js) with the same result"

Have you updated your config.js file with the config.template.js changes?

[Kiina]

Deleted all my db files, removed scgi from config.js but I still have the same issue

[bbashy]

@Kiina If you're doing all that, have you tried deleting the folder and re-cloning + setting up?

[Kiina]

I recloned the repo into a new directory and did setup from beginning. Took a long time because it's a raspberry pi but the issue is still the same.

[kiina@raspberrypi flood]$ uname -r
4.14.68-1-ARCH
[kiina@raspberrypi flood]$ node -v
v10.1.0
[kiina@raspberrypi flood]$ npm -v
6.0.1

[Handyone]

Same here, with every reboot, relogin or refresh I get cannot connect to rtorrent even when files downloading with rtorrent.
It was working fine before. This happened after I did a fresh install.
Thought I messed up while installing and did reinstall like 3 times with different versions of nodejs till I saw this post.

[VirtuBox]

Hello,

I have also tried to remove flood and to make a fresh install but issue was exactly the same each time.
So, I have tried a previous commit :

git checkout 3da1fbfc5a34212fb2955f04343af069c25bb0fe

And to run again npm i & npm run build

rm -rf node_modules
npm i
npm run build

And flood is working properly. So the issue come from one of the 7 commits done since the beginning of September. If I have some free time this afternoon, I will try each commit to find which one is the problem.

[bootldrDNB]

I can confirm that the checkout command above works - and flood is now working properly.

[boistordu]

I can confirm the result.
OS: archlinux up-to-date

[etbusch]

I also confirm that reverting to 3da1fbfc5a34212fb2955f04343af069c25bb0fe fixes the issue.

[jfurrow]

Should be fixed by https://github.com/jfurrow/flood/commit/3e782b46e5f18e05273a577dd9648223838d493c