EC28

Members
  • Posts

    85
  • Joined

  • Last visited

Posts posted by EC28

  1. On 5/18/2020 at 10:27 AM, EC28 said:

    Somehow I've locked my web gui up.  I was fixing the ipmangle error and got it resolved.  But now I can't log in remotely on my reverse proxy.  It works fine when I open the IP directly.  Here are some logs:

     

     

     

     

    Any ideas on what I messed up?

     

     

    So I created an entirely new rTorrent docker and re-did it all from the ground up.  Even after doing that fresh, the webgui is still broke and won't let me log in.  Anyone got any ideas?

  2. Somehow I've locked my web gui up.  I was fixing the ipmangle error and got it resolved.  But now I can't log in remotely on my reverse proxy.  It works fine when I open the IP directly.  Here are some logs:

     

     

     

     

    Any ideas on what I messed up?

     

  3. I've been having some wonky problems with this container recently.  Last week usenet downloads wouldn't import and move the completed files correctly.  Now that seems to be working, yet now it won't copy torrent files and move them to /media.  Anyone have any ideas?  Thanks. 

  4. 4 minutes ago, trurl said:

    Did you read the whole link I gave? It tells you how to get diagnostics even when you can't reach the server over the network.

    Missed that part.  Somehow clicked on the link to the old page.

     

    5 minutes ago, trurl said:

    Are you sure that static IP you have assigned will actually work with the rest of your network now? Nothing changed on your network, nothing else has already grabbed that IP? Everything on that same subnet?

    Yeah, nothing has changed.  Everything has a static IP.

  5. 7 minutes ago, trurl said:

    The "Need Help?" sticky pinned near the top of this same subforum:

     

    https://forums.unraid.net/topic/37579-need-help-read-me-first/

     

    Diagnostics preferred if you can get them.

     

    What does it say the IP address is (top right of webUI)?

    I think the only way I can get the log is by rebooting and using the terminal command since I can't connect to the server.  It should still reproduce the error though, right?  If it's not loading still that is.  (Of course now I have to wait for parity to build as well.)

     

    The IP address is the local static IP I've assigned to it.  (192.168.1.3)

     

     

  6. Ok, so this is weird, I finally got my 3.3v issues straightened out and have a nice new 40TB to play with, but I can't get the WebGUI to load and it appears like the server is not connecting to my network.  (Not showing as leased on my pfSense box.)

     

    What's odd is that it was fine before putting the drives in.  I can log into the WebGUI on the server itself and it shows my license and everything.  It's building the parity drive now.  But it will not show up for some reason.  What information do you guys need and what should I do?  I made a backup of my USB on my laptop already in case we're headed that route.  Thanks!

  7. 4 minutes ago, binhex said:

    have you added a port mapping for the container for the incoming port?, you will need to add in the port 7100 for the container, otherwise it cannot get out to the lan.

    That did it, thank you so much!  Why I couldn't remember to do that is beyond me.  Just out of curiosity, what is port 5000 for?

  8. 10 minutes ago, binhex said:

    you need to set it to the following for a single port:-

    Got that working now, thanks.

     

    10 minutes ago, binhex said:

    your wan rule does not look the same as the port forward nat rule, the wan rule has a alias name of 'rTorrent' for the port, is this alias the same as your port forward nat rule value of '7100-7119' ?

    Must have somehow uploaded an older picture.  It's set to the same now.  Emby pings as open.  So does HTTP/HTTPS.  So weird.  I've tried turning NAT reflection completely off (disabled), tried PureNat, tried NAT + Proxy; doesn't seem to make a difference.

    I am curious as to what each port does in the docker settings.  I know 9080 is the webUI, but what do the other ones do?  Is it something with them and pfSense maybe?

     

    Untitled.png

  9. 6 minutes ago, binhex said:

    i wouldnt use a range of ports a single port should be sufficient, also make sure pfsense is also creating the Firewall/Rules/WAN, as you need both for the port to be open.

    I changed...

    network.port_range.set = 7100-7119

    ...to simply 7100 and ruTorrent wouldn't load with that set.  Changed it back and it loads fine.  Still no luck with opening ports though.

     

    My UnRAID IP is 192.168.1.3

    This is the NAT port forward rule.  rTorrent alias is port 7100.

     

    And the other is the WAN rule.  Still nothing seems to open.  I know it's something silly on my end.

    Untitled.png

    Untitled2.png

  10. 3 minutes ago, binhex said:

    not sure exactly what you are trying to port forward here, but if its the incoming port then you shouldn't be doing this, see Q14:-

    I have VPN turned off though.  So I'm just trying to get the incoming rTorrent ports open to the WAN I think.

  11. For some reason I can't figure out how to port forward this container in pfSense.  I had it working in the past, but I can't seem to get it to open now for whatever reason.  My ports in rtorrent are 7100-7119.  This is my NAT rule.  Anyone got any ideas what I've got wrong?

     

     

    Untitled.png

  12. Anyone else having issues with the Android apps lately not wanting to play videos?  TV and movies?  Some seem to work, but a lot don't.  Get an error message saying to restart the server and the app and see if that fixes it.  It doesn't.  I even reinstalled the server docker and still does the same things.  I don't really see any errors in the logs, but I can post whatever is needed.  Thanks.

  13. The log seems to have lots of errors.  The container seems to be running ok at the moment, but I had a hard time getting back to the guacamole login screen earlier.  What seems to be up here?

     

    https://pastebin.com/kPKkXF2z

     

    This showed up as well after I logged in.

     

    Quote
    
    Traceback (most recent call last):
    File "site-packages/calibre/gui2/notify.py", line 159, in get_notifier
    File "site-packages/calibre/gui2/notify.py", line 89, in get_dbus_notifier
    File "site-packages/dbus/_dbus.py", line 211, in __new__
    File "site-packages/dbus/_dbus.py", line 100, in __new__
    File "site-packages/dbus/bus.py", line 122, in __new__
    DBusException: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
    Traceback (most recent call last):
    File "site-packages/calibre/gui2/notify.py", line 159, in get_notifier
    File "site-packages/calibre/gui2/notify.py", line 89, in get_dbus_notifier
    File "site-packages/dbus/_dbus.py", line 211, in __new__
    File "site-packages/dbus/_dbus.py", line 100, in __new__
    File "site-packages/dbus/bus.py", line 122, in __new__
    DBusException: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead