noraa

Not too sure if anyone else is having this issue however, the broadcast command for RCON seems to not be working.. I am able to do everything else (save, showplayers, info etc) with no issues but am getting an "unknown command" return when trying to broadcast a message using "timeout 1 rcon -a 192.168.20.5:25576 -p password broadcast Saving..." Any help would be greatly appreciated i'm sure it is something silly. Thanks in advance.

Possibly NAT Reflection? I am not 100% sure tho and am just spitballing but it could be you don't have it enabled for Port Forwarding under Firewall->NAT (At least on OPNSense). However, If you have other stuff forwarded with no issues then I am very wrong. Good luck!

Here you are sorry about that, I deleted all folders except Pal and started the container up and it is running v0.1.4.0 now. Any reason you suggest to skip pi hole for unraid? i’ve never had any issues with it but if it is known to cause issues then i’ll gladly disable it. Thanks for your help!

Hey thanks for the fast reply! I ran the above command and attached what it returned. I do have PiHole running i’ll watch the logs to see if it’s blocking anything. Thanks again Edit - Deleted everything but Backups and Pal folder, everything updated and seems to be good now. I would like to update the container properly by restarting it but I’m really not sure what the issue could be.

Hello, I am having issues trying to update the server to the latest version. Currently I've tried restarting the container, deleting steamapps folder as well as restarting without my steam credentials. None of which seemed to work Here is a screenshot of my paths if that helps at all, any help would be appreciated. Thank you!

I am stuck on getting RCON enabled even with the steps above, I haven't touched the default template at all, I have enabled RCON in my config etc. and typing rcon -H machine ip -P 25575 -p password doesn't work it just hangs. Just wondering if there is a step I am missing? Will provide whatever info is needed. Thanks in advance.

So I put a file container the folders / paths I would like to exclude from the 'Mover' process My ignore-files.txt is located in '/mnt/user/backups/' inside of the file I have the directories / folders listed like so /mnt/cache_downloads/data/usenet /mnt/cache_downloads/data/usenet/incomplete and so on, unfortunately it doesn't seem to be working, any help would be greatly appreciated. Thank you! Attached picture of my 'Mover' Settings.

As the title says, I am having an issue with Logs becoming full on my unRAID server. Not too sure what is causing it outside of NFS errors. Any help would be greatly appreciated! I've attached the log files as well. Thank you. teena-diagnostics-20210607-1118.zip

As the title says, my logs are being flooded by nfs errors. I've attached the logs if it is any help. I believe the issue is NFS erros but I could be wrong. The error I am getting is - ErrorWarningSystemArrayLogin Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Jun 7 14:20:45 Teena kernel: NFS: server 192.168.1.2 error: fileid changed Jun 7 14:20:45 Teena kernel: fsid 0:87: expected fileid 0x3000000929095c, got 0x300000092944ea Continiously, Any help would be greatly appreciated. Thank you! teena-diagnostics-20210607-1118.zip

As the title says I am having issues with my Plex docker container, I checked the logs and I get the error "Connection timed out" multiple times, and the media then becomes unavailable on Plex until the container is Restarted. I post.d another issue I am having over in the General Forums, where none of my container are pulling updates. I am not too sure if the 2 are related, Plex works perfectly fine once the container restarted, until the error happens again which at least once a day at this point. Any help would be greatly appreciated. Thank you!

As of the past week one of my unRAID boxes is having issues with Updates, I've got a screenshot I will post below, but I am not exactly sure what is causing the issue as I have another Box that has 0 issues with updating. I've checked DNS settings and everything looks good to me, any help would be greatly appreciated. Thank you!

Hey, I used to run this Docker with no issues but have recently re-installed it and am getting the following error "No profiles are available; check internet connectivity and refresh the profile list." I do have a pfsense Box but can't seem to find any information on why it wouldn't work? I have tried updated the WebUI and re installing the Node packages etc. Any help would be appreciated, thank you!

I am also getting this error. I have disabled my autodl for now. I think the git repo might have changed their URL?, not too sure but I think this is an issue with autodl in general not just you or your setup but I am talking out of pure speculation.

Sorry for the bump was just wondering if anyone might know what is causing this issue. Any help is appreciated. Thank you.

Whenever I docker exec into the deluge container and enter 'deluge-console' I am getting a lot of errors. I've checked and /usr/bin/deluge-console doesn't exist. Is it installed in another location? Or am I missing something entirely. The goal is to have ruTorrent execute the deluge-console to add torrents to deluge via autodl-irssi using the following command Command: /usr/bin/deluge-console Arguments: connect localhost:port ; add -p /path/to/downloads $(TorrentPathName) ; quit Any help is appreciated. Thanks