Zarroc

Hey Binhex, having some issues routing nicotine+ through qbit. It seems to connect to soulseek just fine; however i cant connect to my vnc server. I'm not entirely sure where i went wrong, i followed the guide through the FAQ. I've attached my supervisord.log file for nicotine+. Any help would be appreciated! Thank you in advance for all you do! supervisord.log

Hello, Looks like an update to prowlarr did something to the config file. getting a chmod cannot access /config/supervisord.log no such file or directory exists. I dont see the supervisord. just the supervisord.log1 and supervisord.log3. Not sure what happened, but everythings been working like a top for a few weeks since i started setting it up.

having some serious issues getting this to work. i was following a trash guide and now i can even access the plex manage page. I'm getting a about:blank#blocked and the port mapping area is blank for some reason. Let me know what config files you might need to help me get straightend out. Thank you in advance!

it did yes! and now cross-seed can login to qbit, oh thank god. You're fantastic lol

actually i think my issue is fixed?!?!? must have been that conflicting port issue then!

Ah the ORT int PORT just needed to be capitolized. got it! okayyyy back to my original issue 🤣

https://privatebin.net/?2767f28ef48ed5e4#GxzLAfDcr4TZMPJ7Q9oHS8kKkk5a8z4eqA2tKFQPs6cV Still cant get to the webgui. no idea what im doing wrong at this point

and it brought it back as the updated docker thats hot garbage currently. wonderful

got that.....it did not bring back that setting for the template.

where do i delete the image? nevermind im retarded lmao

okay so i delete docker, go to appdata and delete the entire qbit folder? and then reinstall from CA?

this is where i had set it

i think i deleted a setting for w you're correct, i deleted that setting instead of the one i had meant to. I set it at a different spot, which is likely my issue. can you click edit on that key 9 and show me what it should be?

You might be right, i think i deleted the wrong setting tbh. which is why i was asking for default settings lol

https://privatebin.net/?87d74f1680d1d96c#HxNvTSxpUxYHbHxQyXaZz4i2wCcFSyC9pG6f9HjzsUkR ah! okay. that part makes sense. hes current. but now i cant see my webUI

of course it is....the container port and host port should be the same port according to the article you pointed me towards???

https://privatebin.net/?59a3a546570cb95b#DVLYXEunoDBAcVTtJP4VnbC7ZbkKTr55pEQauY2E87Mu

hmmm i think i changed the wrong setting and bricked it. is there a list of default settings?

hmmmm now that ive retried this. I've noticed that qbit web interface runs on port 8080 and chromium uses 8080 for its container port. is that what is getting me?

I thought so as well, but thought it might be a general networking issue. I've certainly changed from default login, so no issue there. I'm not on the new version of the qbit docker either (after hearing the issues decided to hold off for now). I can't think of anything that cause the issue im describing. If you cant think of anything ill try the whitelist (id prefer not to if i dont have to, even if it is just an internal address) Any further thoughts? i can provide a log for qbit but im not sure how much it would help

I'm trying to setup cross-seed and im failing on the qbit login part. it keeps telling me a 403 error. which is just bad login information from the error code. so i tried replicating the issue without cross seed. On my chromium docker i go to 192.168.1.170:8080 and attempt to login with my credentials. it tells me incorrect information I log out of my qbit console and log back in with the same exact information, no isue logging in at all. I dont know what kind of issue im having or where i should really be asking this question. I'm not sure if this is a qbit issue, or just a general unraid forum question; so my apologies if this doesnt belong here!

I did, but it wasnt working so i just deleted that part of the config. if i put /data/watch as monitored folder, i also need chromium to download its files to that folder. what path would i need to hand off to the chromium docker for it to download to /data/watch

Config path -/mnt/user/appdata/binhex-qbittorrentvpn data path-/mnt/user/data/torrents/ I started this before watching videos, assuming its file structure was like windows. I was obviously wrong. So its kind of a mess currently. Is there a better way i can do this to un-fuck my folder structure?