[Support] Josh.5 Docker Templates


237 posts in this topic Last Reply

Recommended Posts

I've had lancache-bundle running on my unraid server in the past without issue. Same server, same router. Just installed it again and it only works if I connect to it directly by configuring my PC's IPv4 settings, but not if I configure my router to point to the docker (which used to work in the past). It sounds as though a few people are having issues so I thought I'd share as much information as I could to see if we can get to the bottom of some of them.

 

Here's my working 1 PC setup (not ideal)

 

image.thumb.png.c58ab44271a47274699cf9d3bda7e19b.png

Docker config in Unraid

 

image.png.2eb53810f8d265d2e8b0f5ffa9ae7691.png

Docker config continued

 

image.png.eb0e4e144832981d6ab06edd4517a41a.png

IPv4 DNS settings on my PC

 

image.png.8192a67c991303951aba3e5f38610744.png

Router DNS Config (I know this isn't pointing to my lancache docker image at 192.168.50.245 - this is the less than ideal non-router setup)

 

image.png.fedf576fda03605a562eaebdfb39a5f3.png

Initial download speeds from steam

 

image.png.b7243b44978adabe59c65715cae4e0d5.png

Plenty of stuff in my new lancache share

 

image.png.3ec6c257d394072b087a185affde98b1.png

Re-download speeds that prove the cache is functioning correctly

 

Now if I change the router config to point to the lancache docker image as the DNS it doesn't work and nothing on my netwrk can resolve DNS addresses...

 

image.png.a077ffa12a33df56b0f37f41f1f86e02.png

Router pointing to lancache docker image

 

image.png.dea3b22f3ee8d6aecaf9a8d64e18ad0e.png

Windows told to resolve DNS automatically (leave it to the router)

 

image.png.ee03fefeee9b364665215d12f553d0d1.png

Unresolved DNS

 

So why is it that if I point my PC directly to the docker image it works, but if I leave my PC to automatically resolve, and point the router to the docker image, it does not work?

 

Any ideas folks?

Link to post
  • Replies 236
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This is a support thread for various Unraid docker container templates. If the template has a link to another support thread, then please post questions there.   Templates will be uploa

The root folder needs to be removed. As much as it pains me to say it, this docker is not very well put together. I made it with the intent of just spending an hour or 2 getting it working and then le

Ok, with that kind of response, you get this kind of response:   If you want it to cache something, do you think you should set it to false?  Normally, the word false, means you DON'T want i

Posted Images

@MajorTomG Is it possible that your router would try to connect to the DNS using the WAN connection on your router?

You could try running another DNS server (pihole or something like that) and point your router to that and see if it will resolve... If it will not resolve either, than I think your router will use the WAN port for DNS lookups. In that case you can setup LanCache to use your router as source DNS and point your systems to the LanCache IP.

Maybe it's possible to change it in the DNS settings of your router so it will hand out the LanCache IP as the DNS server to you DHCP clients.

Link to post

having issues using the lancache

 

i finding my computers accessing the internet is much slower then when i using 1.1.1.1  where its bang fast

i also like to know for Epic Games   how do you have endless caching?  default is like 152 days for caching  how do you set caching for different days 

like Epic, Battle net, Steam  =  Endless..    anythng else can be 152 days

 

as it takes me 6 months to redownload  Epic games on my account on my current internet speed 24/7 going drives me nuts so i dont want it erasing it..  and my epic games takes up 3TB of data  on my gaming drive..  do i need least 3TB  for lancache..  

 

as i frustrated how Epic Launcher works for verifying games.. and the trick work around doesnt work

 

Link to post
  • 3 weeks later...

Hey Guys,

 

for people with issues with lancache...

I did some research on the original Lancache website and they mention Lancache does not like when certain ports are shared with Lancache e.g.53,80 and 443. This is likely the issue here when running on Unraid assuming you run other containers using any of these ports.

 

A workaround is to create a VM e.g. ubuntu and install Lancache on that VM. Within that VM Lancache has exclusive access to these ports.

I am currently checking this myself and it looks promising!! My issues went away but still testing more.

A video guide here:

 

a written guide here:

https://lurkingforgames.com/lancache

 

I am happy with this and still testing! Also within the lancache folder you can do a "nano .env" and you can see most of the parameters from the Unraid Lancache docker settings. Change them exactly like you had it before.

 

Link to post
On 7/3/2021 at 9:03 AM, xPliZit_xs said:

Hey Guys,

 

for people with issues with lancache...

I did some research on the original Lancache website and they mention Lancache does not like when certain ports are shared with Lancache e.g.53,80 and 443. This is likely the issue here when running on Unraid assuming you run other containers using any of these ports.

 

A workaround is to create a VM e.g. ubuntu and install Lancache on that VM. Within that VM Lancache has exclusive access to these ports.

I am currently checking this myself and it looks promising!! My issues went away but still testing more.

A video guide here:

 

a written guide here:

https://lurkingforgames.com/lancache

 

I am happy with this and still testing! Also within the lancache folder you can do a "nano .env" and you can see most of the parameters from the Unraid Lancache docker settings. Change them exactly like you had it before.

 

In my experience the VM solution is slower, besides I have this configured to use its own IP so there shouldn't be any port conflicts. This worked before the most recent update.

Link to post
Posted (edited)
21 hours ago, arch1mede said:

In my experience the VM solution is slower, besides I have this configured to use its own IP so there shouldn't be any port conflicts. This worked before the most recent update.

I actually figured out the issue, unknown to me, md1 was spitting out xfs errors even though the main page/dashboard showed everything green. As it happens, the lancache-bundle docker has a user setting that pointed to md1 which was really not accessible so wouldn't start. Rebooted the unraid box resolved the issue but not really happy with that solution as I shouldn't have needed to reboot it. As a result, md1 had a xfs error on it so I had to run a parity check on the whole array to resolve the issue, I may still have to put the array into maintenance mode and do a repair but thought id share how this was resolved.

Edited by arch1mede
Link to post
21 minutes ago, arch1mede said:

md1 was spitting out xfs errors even though the main page/dashboard showed everything green.

The green status indicators means the drive hasn't returned any write errors. Nothing to do with the validity of any filesystem on the drive.

Link to post
19 hours ago, jonathanm said:

The green status indicators means the drive hasn't returned any write errors. Nothing to do with the validity of any filesystem on the drive.

Yes I realize that but not sure how I am supposed to know there is an issue if I have to check multiple places.

Link to post
14 minutes ago, arch1mede said:

Yes I realize that but not sure how I am supposed to know there is an issue if I have to check multiple places.

Only major issues when the drive is unmountable or disabled (two separate issues with two separate indicators) show up on the main GUI. File system corruption minor enough that the drive still mounts don't show up there currently.

 

I'm probably going to submit a feature request, it may or may not ever get any attention.

Link to post
Posted (edited)
2 hours ago, jonathanm said:

Only major issues when the drive is unmountable or disabled (two separate issues with two separate indicators) show up on the main GUI. File system corruption minor enough that the drive still mounts don't show up there currently.

 

I'm probably going to submit a feature request, it may or may not ever get any attention.

For me md1 was mounting but showing up like: d?????????????? so it would have been good to know that there was an issue with the mount point.

Edited by arch1mede
Added more verbiage for clarity
Link to post
  • 3 weeks later...

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.