flood icon indicating copy to clipboard operation
flood copied to clipboard

URL path for rtorrent scgi being proxied via nginx

Open evilbulgarian opened this issue 6 years ago • 8 comments

Summary

URL path for rtorrent scgi being proxied via nginx Is there a way to configure a nginx proxy URL to the rtorrent scgi?

Expected Behavior

pass this to docker environment -e RTORRENT_SCGI_HOST=http://gypsyops/tor -e RTORRENT_SCGI_PORT=80

Current Behavior

Passing the http://url/to/scgi/proxy in the RTORRENT_SCGI_HOST environment variable does not work.

Possible Solution

Not sure

Steps to Reproduce (for bugs)

  1. docker run -d --name flood --network lan_1 --ip 10.6.6.253 -p 3000:3000 -e RTORRENT_SCGI_HOST=http://gypsyops/tor -e RTORRENT_SCGI_PORT=80 -v /etc/resolv.conf:/etc/resolv.conf -v /etc/timezone:/etc/timezone --restart=unless-stopped vladi/flood:20180409

Context

Unable to talk to rtorrent running behind nginx proxy

Your Environment

  • Version used:
    • Version (stable release) => v1.0.0
    • Commit ID (development release) 293aa11d512ee089f1d559b24e6f8bbe707cfb8d
  • Environment name and version (e.g. Chrome 39, node.js 5.4): docker / firefox
  • Operating System and version: Gentoo Linux rolling release

evilbulgarian avatar May 11 '18 20:05 evilbulgarian

Hello @evilbulgarian,

Thanks for posting your issue, but can you please take time to edit it in order to fill the issue template.

Edited

I'm closing the issue until you fill it.

Feel free to ask to re-open it as soon as it's done.

noraj avatar May 11 '18 20:05 noraj

PS : why are you running docker env vars and not docker run ?

noraj avatar May 11 '18 20:05 noraj

@evilbulgarian Please do not open new issues, let's re-open this one in order to keep all links and tracking.

noraj avatar May 11 '18 20:05 noraj

@noraj Sorry about that new to this :)

evilbulgarian avatar May 11 '18 20:05 evilbulgarian

@evilbulgarian When you say does not work. what is the behavior ? What's happening ? Have you some error message or logs ?

noraj avatar May 11 '18 20:05 noraj

It hangs after creating the account..

❯ docker logs -f flood
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info lifecycle [email protected]~prestart: [email protected]
npm info lifecycle [email protected]~start: [email protected]

> [email protected] start /usr/src/app
> node server/bin/start.js

Flood server starting on http://undefined:3000.

GET / 200 8.350 ms - 543
GET /static/css/main.c8db9a96.css 200 14.776 ms - -
GET /static/js/main.bb3f4a51.js 200 5.989 ms - -
GET /favicon.ico 200 3.420 ms - -
GET /favicon.ico 304 1.620 ms - -
GET /api/activity-stream?historySnapshot=fiveMin 401 1.617 ms - -
GET /auth/verify?1526072972382 200 9.143 ms - 20
POST /auth/register 200 33.541 ms - 203
GET /api/settings 200 1.104 ms - 2
GET /api/client/settings 500 66.434 ms - 158

evilbulgarian avatar May 11 '18 21:05 evilbulgarian

@evilbulgarian Did you check https://github.com/jfurrow/flood/wiki/Troubleshooting#stuck-after-log-in ?

Are you sure that rtorrent is running?

noraj avatar May 13 '18 10:05 noraj

Yup, when I do docker exec flood curl http://10.6.6.1/tor it works so it can access the rtorrent scgi proxy

evilbulgarian avatar May 16 '18 23:05 evilbulgarian