[Support] ich777 - Application Dockers


ich777

Recommended Posts

On 9/14/2022 at 6:26 PM, Keek Uras said:

Hello,

 

I'm trying to use DirSyncPro and I'm a bit confused on one piece. In the comments at the top of the docker, you state "You can sync your files to another offsite SMB (is removed in the latest version, please use Unassigned Devices Plugin in Unraid and mount the share with the 'local' option)" and I can't for the life of me figure out how to do this. I took a long look at the plugin and I just can't see how this is done. I did have an SMB share (/mnt/remotes/192.168.1.40_Media Library) but it will not show up in the Docker. Thanks in advance for any help you can provide. 

 

~K

 

I am having issues locating where the option to mount the share with the local option in the "Unassigned Devices". I do not see that option in "Unassigned Devices". Where is it?

 

Cheers

 

 

Link to comment
35 minutes ago, Vetteman said:

I am having issues locating where the option to mount the share with the local option in the "Unassigned Devices". I do not see that option in "Unassigned Devices". Where is it?

Just mount the share through UD and create a new Path with R/W Slave and mount it to the container your local path should be something like /mnt/remotes/SHARENAME and I would strongly recommend that you mount it in the container also to something like /mnt/SHARENAME.

Link to comment
On 12/14/2022 at 12:49 PM, ich777 said:

Just mount the share through UD and create a new Path with R/W Slave and mount it to the container your local path should be something like /mnt/remotes/SHARENAME and I would strongly recommend that you mount it in the container also to something like /mnt/SHARENAME.

 

I am mounting the unassigned drive via the plugin UD. When I click the MOUNT button I do not see the place to enter path or R/W slave. Also I have no idea what you mean by mounting the drive in the container?

 

Sorry but your reply did more to confuse me,, then enlighten me. 

 

Again where is the option to mount the disk as a local share?

 

Thanks kindly...

Link to comment
4 hours ago, Vetteman said:

When I click the MOUNT button I do not see the place to enter path or R/W slave.

After mounting the share go to the Docker template and click on Add path, device,… at the bottom from the template (blue text), a pop up will appear where you can specify the host path and the container path, specify the paths like i mentioned in the previous post, then also select R/W Slave.

After that click on Add and Apply.

 

Then you should be able to navigate to the path that you‘ve specified as container path from within DirSyncPro.

 

Hope that helps.

Link to comment

Hello all, 
hello ich777, 

I have recently started to deal with Nextcloud-Talk, so now I may also deal with Stun/Turn. I pulled the docker from ich777 for this and filled out the template accordingly. Since my Nextcloud instance runs in a costom-network, I chose the same network in the Stun-Turn server. If I now enter my dyndns domain in the Nextcloud Talk settings, the green tick also appears. But only if I choose "turn: only" or "turn: and turns:". With "only turns:" a red exclamation mark appears. Have I perhaps done something wrong here? In addition, in the context of stun/turn, I kept reading about "denied ip addresses" when the server has access to the local network. How is that handled in this Docker? Attached are some screenshots of my configuration. I would be very happy if one of you experts could enlighten me a bit. :)

turns_only.jpg

turn_only.jpg

Config_stun_turn_server.jpg

Link to comment
2 minutes ago, xmastree said:

If I now enter my dyndns domain in the Nextcloud Talk settings

Dyndns is not really supported or better speaking well supported for STUN/TURN...

 

4 minutes ago, xmastree said:

Since my Nextcloud instance runs in a costom-network, I chose the same network in the Stun-Turn server.

I would strongly recommend that you give it's own unique IP and forward the ports (in custom: br0 if possible), I've never tried it to use the same network and won't recommend that.

 

5 minutes ago, xmastree said:

I kept reading about "denied ip addresses" when the server has access to the local network.

It is possible that it isn't working because of that, are you sure that you've set up your Hair Pin NAT correctly?

Have you yet tried it from outside your network?

Link to comment
18 minutes ago, ich777 said:

I would strongly recommend that you give it's own unique IP and forward the ports (in custom: br0 if possible), I've never tried it to use the same network and won't recommend that.

 

I have adjusted the Docker according to your suggestion. The port then also jumps to 5349, but the talk settings show the same behavior. Turns does not work unfortunately.

 

21 minutes ago, ich777 said:

It is possible that it isn't working because of that, are you sure that you've set up your Hair Pin NAT correctly?

Have you yet tried it from outside your network?

probably not :) i have already tried Nextcloud messaging and calling over the mobile network... that works. At least with a device that is located within the network.

Link to comment
9 minutes ago, xmastree said:

probably not :) i have already tried Nextcloud messaging and calling over the mobile network... that works. At least with a device that is located within the network.

Would be interesting what happens when the device is not in your network.

 

9 minutes ago, xmastree said:

The port then also jumps to 5349

The port shouldn't jump to anything else than what you specified in the "PORT" variable from the container, other than that if you change it to "custom: br0" you can ignore the ports which are displayed because basically all ports are exposed and the container is now handled like a computer on your local network and all ports are reachable.

 

Ah, now I get it, you changed the port from 5349 to 5309 <- may I ask why?

 

If you set the PORT variable to 5309 and you are running the container in custom: br0 mode then simply forward the port to 5309 TCP and UDP.

 

Link to comment
12 minutes ago, ich777 said:

Would be interesting what happens when the device is not in your network.

 

The port shouldn't jump to anything else than what you specified in the "PORT" variable from the container, other than that if you change it to "custom: br0" you can ignore the ports which are displayed because basically all ports are exposed and the container is now handled like a computer on your local network and all ports are reachable.

 

Ah, now I get it, you changed the port from 5349 to 5309 <- may I ask why?

 

If you set the PORT variable to 5309 and you are running the container in custom: br0 mode then simply forward the port to 5309 TCP and UDP.

 

All right, good to know. :D I have set up a port forwarding for the port specified in the template. :) Why I changed the port? → Good question, for a better conscience I usually change the default port.... No idea if this is so useful.

By the way, in the meantime I grabbed two cell phones (cellular) and made a call (video and audio) and sent some messages. Works. 

I also tried the whole thing with the default port (port forwarding, calls, messages). Same behavior. :S 

I'm still surprised that turns does not work for me.... Nevertheless, many thanks to you, @ich777.

Link to comment
44 minutes ago, xmastree said:

I have set up a port forwarding for the port specified in the template. :)

Good if you are using it with bridge or a custom bridge network like your proxynet but not necessary for custom: br0 networks.

 

44 minutes ago, xmastree said:

Why I changed the port? → Good question, for a better conscience I usually change the default port.... No idea if this is so useful.

Not really, because the default STUN/TURN port is 5349 and I would not change standardized ports anyways because you can cause all sort of weird issues with this.

 

TURN is usually only needed if a relay server is needed for example if two devices trying to talk to each other which are both behind a CG-NAT.

Maybe TURN is working for you and it is just displayed wrong in Nextcloud, that's my best guess.

 

47 minutes ago, xmastree said:

By the way, in the meantime I grabbed two cell phones (cellular) and made a call (video and audio) and sent some messages. Works. 

Okay then I'm glad that I could help, at least I think so... :D

Link to comment

Not sure if this has been noted here before but wanted to note it for myself and anyone else who comes accross it
If you're trying to use MariaDB and it's just looping through the boot

Verify you've named your database to photoprism, it doens't have an option for the database name but creating that database instead of what I had before resolved it. 

Link to comment

Evening,

 

I just recently started using the LANCahe Pre-Fill container and it's been working great (as far as I can tell). I would like some guidance on how I can check the status of current, on going, downloads. I let some downloads go overnight and this morning when I went to check, I lost the console window I had been using to monitor the status. Is there a command I can run to check the status of the current downloads? 

 

Thanks,

Link to comment
7 hours ago, ss1gohan13 said:

I let some downloads go overnight and this morning when I went to check, I lost the console window I had been using to monitor the status.

I don't understand, you see the status in the Container log.

Did you open up the container console and start a prefill like that?

If yes, do you maybe have CA Backup installed? Keep in mind that CA Backup will stop the container while taking a backup by default.

 

Keep also in mind the container is not supposed to be used with the console (only for the first run and selecting games).

Usually you set a CRON schedule in the template and after that the container will run the schedule at the given interval and you can view the status in the Docker log.

 

However you can also force the container to always do a check or better speaking prefill on start by setting the Variable "Force Sync" to true.

Keep in mind that the container is set by default to clean the log file on every restart so it is maybe a good thing set Log cleanup to false, but in general I would recommend to leave it at false.

 

Hope that helps and explains how the container works.

Link to comment
16 hours ago, ich777 said:

I don't understand, you see the status in the Container log.

Ah I mean that does make sense. I was too use to playing in the CLi and saw the gui it had to offer. But, checking the logs should suffice for what I am looking for.

Side bar question. The notes you left in the tutorial of the container were wonderful. Is there any chance you could expand on them? For example, add in the update command?

Link to comment
3 hours ago, Alchemist Zim said:

I've started researching how to enable port forwarding for use with qBittorrent

 

as this is a certain PIA feature and if you want it automated, i guess its recommended to use the @binhex VPN Dockers, either his general VPN or even the qbit VPN Version. take a look at his readme's

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

@ich777 may correct me, but afaik its not implemented in his docker by default

Link to comment
30 minutes ago, slimshizn said:

I'm really enjoying the LAN-Cache-Prefill. Any chance more services besides blizzard and steam are going to be added (or can be)? Eg. XBOX, PS, Epic. Thanks for the work, using it now.

In general they could be added but I only create the containers for easy use with Unraid and the applications themselves are written actually by someone else.

 

I've also looked into Epic but at the time of writing there is no application that makes that an easy and simple process as it is as with Steam and Battle.net

Xbox and Playstation are also not that easy from what I know and I haven't looked into it yet if it's even possible.

 

The main issue is that there are not that many applications out there which are designed for such a specific use case which looks if a manifest from the game is already downloaded, if not download the game, if yes check which version was downloaded before and compare against the online version and eventually download the newer version if a new version is found of course.

  • Thanks 1
Link to comment

I've recently implemented the lancache-prefill container on my Unraid and it's acting rather strange. 

 

 I followed Spaceinvader's setup guide to set this all up: 

 

EDIT: Should probably add what my setup is:

 

192.168.1.173 = lancache-prefill

192.168.1.174 = lancache-dns

192.168.1.175 = lancache

 

Blizzard prefill will sometimes work, sometimes come up with connection refused. Steam prefill will download the games intermittently (sometimes error downloading, sometimes constant retries, sometimes nothing at all). Unfortunately I set the log files to clear inadvertently, so will paste the error once it comes up again.

 

If I tail -f to the log file, I can see (when it works) downloads to the lancache are working as the logs are filling. Not exactly sure what the go is, but it's probably something simple I've done to break it.

 

ie: when working:

 

[10:39:45 AM] Retrieved product metadata                         36.4256
[10:39:45 AM] Downloading 80 GiB
                                                                                
Downloading.. ━━━━━━━━━━━━━━━━━━━━━━━━━━   7% 00:59:16 5.9/80.0 GiB 178.9 Mbit/s

 

[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 95796 "-" "-" "HIT" "level3.blizzard.com" "bytes=134401104-134496899"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 35948 "-" "-" "HIT" "level3.blizzard.com" "bytes=139660436-139696383"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 35312 "-" "-" "HIT" "level3.blizzard.com" "bytes=142388632-142423943"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 37416 "-" "-" "HIT" "level3.blizzard.com" "bytes=147433099-147470514"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 139587 "-" "-" "HIT" "level3.blizzard.com" "bytes=142494331-142633917"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 104460 "-" "-" "HIT" "level3.blizzard.com" "bytes=146886623-146991082"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 279348 "-" "-" "HIT" "level3.blizzard.com" "bytes=142912763-143192110"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 219811 "-" "-" "HIT" "level3.blizzard.com" "bytes=130888351-131108161"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 106040 "-" "-" "HIT" "level3.blizzard.com" "bytes=136775659-136881698"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 200330 "-" "-" "HIT" "level3.blizzard.com" "bytes=144267481-144467810"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 105703 "-" "-" "HIT" "level3.blizzard.com" "bytes=149023459-149129161"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 262034 "-" "-" "HIT" "level3.blizzard.com" "bytes=145291719-145553752"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 91984 "-" "-" "HIT" "level3.blizzard.com" "bytes=146394919-146486902"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 372961 "-" "-" "HIT" "level3.blizzard.com" "bytes=145818916-146191876"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/34/48/3448e41e21d3724195efe6ef688e81d6 HTTP/1.1" 206 3615055 "-" "-" "HIT" "level3.blizzard.com" "bytes=188148148-191763202"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 170670 "-" "-" "HIT" "level3.blizzard.com" "bytes=144842503-145013172"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 142495 "-" "-" "HIT" "level3.blizzard.com" "bytes=150512294-150654788"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/34/48/3448e41e21d3724195efe6ef688e81d6 HTTP/1.1" 206 6169748 "-" "-" "HIT" "level3.blizzard.com" "bytes=148658598-154828345"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/34/48/3448e41e21d3724195efe6ef688e81d6 HTTP/1.1" 206 1585078 "-" "-" "HIT" "level3.blizzard.com" "bytes=198792252-200377329"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 32612 "-" "-" "HIT" "level3.blizzard.com" "bytes=150116412-150149023"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 38635 "-" "-" "HIT" "level3.blizzard.com" "bytes=144575843-144614477"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 475054 "-" "-" "HIT" "level3.blizzard.com" "bytes=133722331-134197384"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:25 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 36488 "-" "-" "HIT" "level3.blizzard.com" "bytes=155993088-156029575"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 64897 "-" "-" "HIT" "level3.blizzard.com" "bytes=153538616-153603512"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 69408 "-" "-" "HIT" "level3.blizzard.com" "bytes=155814401-155883808"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 92917 "-" "-" "HIT" "level3.blizzard.com" "bytes=152477644-152570560"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 36626 "-" "-" "HIT" "level3.blizzard.com" "bytes=156169945-156206570"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 35194 "-" "-" "HIT" "level3.blizzard.com" "bytes=156355825-156391018"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 125568 "-" "-" "HIT" "level3.blizzard.com" "bytes=154258141-154383708"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 75150 "-" "-" "HIT" "level3.blizzard.com" "bytes=156243988-156319137"
[blizzard] 192.168.1.173 / - - - [22/Dec/2022:10:41:26 +1030] "GET /tpr/wow/data/4f/ab/4fab5ff2d92107a8be6ef03077d10a81 HTTP/1.1" 206 69465 "-" "-" "HIT" "level3.blizzard.com" "bytes=156065003-156134467"

 

In addition, when the prefill is running as normal, accessing SMB file shares slows to an absolute crawl (some shares take over a minute to load). When the prefill container is not running, takes less than a second.

 

Lastly, the game clients (ie. battlenet for Blizzard) won't actually download from the cache, even though my DNS is setup to do just that. I have DNS rewrites in place (using NextDNS) to point the CDNs to my lancache, but that doesn't seem to help). The URLs rewritten are from this list: https://github.com/uklans/cache-domains/blob/master/blizzard.txt, all pointing to my lancache instance (192.168.1.175).

 

Any help would be appreciated (sorry for the long post).

 

EDIT2: Error log attached for failed downloads (for battlenet)

 

battlenet_prefill.log

Edited by evakq8r
Link to comment
5 hours ago, evakq8r said:

192.168.1.173 = lancache-prefill

Prefill don't need it's own IP strictly speaking.

 

Did you set the "--dns=" parameter like mentioned in the description from the container?

 

5 hours ago, evakq8r said:

192.168.1.174 = lancache-dns

Do you need the lancache-dns at all or better speaking have you something like AdGuard or PiHole somewhere in your network? You can also use AdGuard, PiHole, Unbound or whatever as a DNS for lancache.

 

5 hours ago, evakq8r said:

Blizzard prefill will sometimes work, sometimes come up with connection refused.

May I ask where you are located in the world?

 

6 hours ago, evakq8r said:

Lastly, the game clients (ie. battlenet for Blizzard) won't actually download from the cache, even though my DNS is setup to do just that. I have DNS rewrites in place (using NextDNS) to point the CDNs to my lancache, but that doesn't seem to help). The URLs rewritten are from this list: https://github.com/uklans/cache-domains/blob/master/blizzard.txt, all pointing to my lancache instance (192.168.1.175).

Not exactly sure what NextDNS is but this sounds like a DNS issue in general in your network and would be best discussed on the lancache support Forums/Discord.

 

6 hours ago, evakq8r said:

ie: when working:

This could also be caused because of an unstable connection to the Steam CDN itself which maybe not be obvious while downloading through the Steam Client itself.

AFAIK many users get the message that it retries and it works after a short while again but that could be caused of many things.

Even I get the message sometimes but in my case that happens really occasionally.

 

6 hours ago, evakq8r said:

In addition, when the prefill is running as normal, accessing SMB file shares slows to an absolute crawl (some shares take over a minute to load). When the prefill container is not running, takes less than a second.

Do you have the data for your lancache on your Array? If yes, I would not recommend doing that it that way, rather I would recommend that you use a disk outside from your Array, maybe a spinning HDD or even better a SSD or NVME mounted through Unassigned Devices.

I could imagine that the prefill stresses your server too much and you maybe also get higher I/O Wait than usual when having the lancache on the Array.

Link to comment
3 minutes ago, ich777 said:

Prefill don't need it's own IP strictly speaking.

 

Did you set the "--dns=" parameter like mentioned in the description from the container?

 

True, however without the IP it defaults to DHCP, which was a lot lower in the IP range I have available, so kept them together.

 

Yes, I did:

 

image.png.c2e285f0fa90e00df5bb510889e5cfc8.png

 

5 minutes ago, ich777 said:

Do you need the lancache-dns at all or better speaking have you something like AdGuard or PiHole somewhere in your network? You can also use AdGuard, PiHole, Unbound or whatever as a DNS for lancache.

 

Based on Spaceinvader's tutorial video I linked earlier, yes it does seem to be needed. Happy to try an alternative method if you think one fits better. 

 

As for DNS, I use NextDNS (a variation of PiHole/Adguard etc - https://nextdns.io/)

 

6 minutes ago, ich777 said:

May I ask where you are located in the world?

 

Australia

 

6 minutes ago, ich777 said:

This could also be caused because of an unstable connection to the Steam CDN itself which maybe not be obvious while downloading through the Steam Client itself.

AFAIK many users get the message that it retries and it works after a short while again but that could be caused of many things.

Even I get the message sometimes but in my case that happens really occasionally.

 

Unfortunately for me it's quite often. Downloading direct from Steam CDNs outside of Lancache are always stable, so I find it odd for it to become unstable while using Lancache and stable outside of it.

 

7 minutes ago, ich777 said:

Do you have the data for your lancache on your Array? If yes, I would not recommend doing that it that way, rather I would recommend that you use a disk outside from your Array, maybe a spinning HDD or even better a SSD or NVME mounted through Unassigned Devices.

I could imagine that the prefill stresses your server too much and you maybe also get higher I/O Wait than usual when having the lancache on the Array.

 

I do, yes, and what you say makes sense. Unfortunately the server I have has all HDD bays populated and the NVMe adapter in use is on a PCIe bracket in the server (as the Poweredge does not support NVMe or M.2s natively). 

 

Interestingly enough, I was using Josh5's Lancache-Bundle just fine, but the prefill container could never communicate with the bundle for whatever reason. The only reason I spun up the separate containers was because prefill did work, but then had these issues instead. In addition, the lancache-bundle is also using an array share and hasn't crushed I/O at all.

Link to comment
7 minutes ago, evakq8r said:

Based on Spaceinvader's tutorial video I linked earlier, yes it does seem to be needed.

No, it isn't I only use a combination of Unbound, AdGuard and Lancache-Monolithic

I simply rewrite the URLs with the lancache Monolithic IP in my local network, in PiHole you would use something like DNSMASQ.

 

But my set up is a little different from most people ones because I use everything in a LXC container on Unraid where the applications talk to each other in the container and have only one exposed IP which is used then on my local network as DNS <- this is also doable with Docker containers on Unraid itself, I really like over complicating things for me... :D

 

14 minutes ago, evakq8r said:

Unfortunately for me it's quite often. Downloading direct from Steam CDNs outside of Lancache are always stable, so I find it odd for it to become unstable while using Lancache and stable outside of it.

Also when downloading from the lancache or also when filling the cache?

If this is happening also while downloading from the cache then there must be something going on on your network...

 

19 minutes ago, evakq8r said:

Interestingly enough, I was using Josh5's Lancache-Bundle just fine

Didn't he say that he want to deprecate it or am I wrong about that?

 

20 minutes ago, evakq8r said:

but the prefill container could never communicate with the bundle for whatever reason.

Which prefill? Did it work on your computer?

 

21 minutes ago, evakq8r said:

In addition, the lancache-bundle is also using an array share and hasn't crushed I/O at all.

Please keep in mind that this was only a guess and I really don't know what is going on over there.

I only can tell you that I run my lancache from a spinning HDD from UD and it doesn't slow down the server at all, of course I have heavy I/O wait because my HDD is simply not fast enough for my 10Gbit/s connection but that is a common issue.

Did @Josh.5 maybe use a different chunk size?

 

 

But keep in mind that this is only the support thread for the prefill container which seems like to me isn't the issue here at all and it rather seems that there is something wrong with lancache itself.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.