[Support] cheesemarathons repo


640 posts in this topic Last Reply

Recommended Posts

This is a snippet of my content_log.txt.  GenericCache was running and working for blizzard/origin at the time.

[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CS,612) - valve612.steampipe.steamcontent.com (192.168.1.8:80 / 192.168.1.8:80, host: valve612.steamcontent.com): Closing connection
[2018-06-13 16:07:42] HTTP (CS,615) - valve615.steampipe.steamcontent.com (192.168.1.8:80 / 192.168.1.8:80, host: valve615.steamcontent.com): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection
Link to post
  • Replies 639
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Bitwarden Description: This is a Bitwarden server API implementation written in Rust compatible with upstream Bitwarden clients*, perfect for self-hosted deployment where runnin

Hello, Nice work on steamcachebundle, makes LAN parties a breeze. Would it be possible to add Xbox download cache to the docker as well?

Thought I'd post this here as it might be useful to some.  I worte a brief guide on how to setup bitwarden with a reverse proxy using our LetsEncrypt container.  It's on the LinuxServer.io blog.  It's

Posted Images

8 minutes ago, defiant said:

This is a snippet of my content_log.txt.  GenericCache was running and working for blizzard/origin at the time.


[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (69.241.32.246:443 / 69.241.32.246:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2018-06-13 16:07:42] HTTP (CS,612) - valve612.steampipe.steamcontent.com (192.168.1.8:80 / 192.168.1.8:80, host: valve612.steamcontent.com): Closing connection
[2018-06-13 16:07:42] HTTP (CS,615) - valve615.steampipe.steamcontent.com (192.168.1.8:80 / 192.168.1.8:80, host: valve615.steamcontent.com): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection
[2018-06-13 16:07:43] HTTP (CDN,64) - edge.steam-dns-2.top.comcast.net (69.241.116.154:443 / 69.241.116.154:443, host: edge.steam-dns-2.top.comcast.net): Closing connection

Damn Comcast!

 

What is the UP_STREAM_DNS set to?

Link to post
  • 2 weeks later...

I've been trying to setup Steamcache (and now SteamCacheBundle) on unRAID for a long, long time, but I've never gotten it to work.

 

The issue I keep seeing is that the container itself doesn't seem to have internet connectivity, no matter what upstream DNS server I use.

I've tried both a dedicated NIC and IP for the container, as well as bridged. Everything should be working, but it's not.

 

It almost seems like it's able to resolve Steam-related DNS requests, and everything else is just dropped.

 

Anyone else seeing the same? Any advice on what to try next?

Link to post

Yes, I have.


In case it makes a difference, I'm dedicating a single network interface to Steamcache (eth2), which is statically set to 192.168.1.7 in unRAID's network settings, while the Docker container itself is found to 192.168.1.8.

Link to post

@Didstopia

It looks ok, i would try using the "Custom: br0" network type. That works for me.

I also see you are using the Docker share for the caching, where i would use a separate share for it, that doesn't use cache drives :)

 

If the problem persist, please send a picture of the Logs, and a picture of this command "tail -f /data/logs/access.log" running in the containers console :) 

Link to post
1 hour ago, Shamalamadindong said:

Ah awesome! I didn't realise that was possible! I'll take a look when I have a few mins and see what I can do! 

Link to post

@Shamalamadindong

I have just pushed a new update to the oauth2 image, so check for updates for you containers and you should be able to install it. This will grab the two default templates and save them to your oauth2 app data folder in a folder call templates. These will not be used by default. To enable them, edit the oauth2_proxy.cfg file and uncomment line 24:

# custom_templates_dir = "/etc/oauth2/templates/"

Restart the container and it will then use the html templates. One for the sign in page and one for the error page. The templates are exactly the same as the default login pages but can be modified to look however you want. I'll try to create some different themed pages when I have some more time. Any suggestions?

 

Link to post

Still can't get this to work.  Steam Cache config as follows...

Network Type: Custom br0

Fixed IP: 192.168.1.15

Privileged: Off

Lancache IP: 192.168.1.8 (IP of unraid server)

data: mnt/user/LanCache/Data

logs: user/appdata/steamcachebundle/data/logs

Port 80

 

on a virtual machine with DNS set to 192.168.1.15

 

[2018-07-10 15:21:58] Failed to get "/serverlist/1/20/" from valve600.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:00] Failed to get "/serverlist/1/20/" from valve609.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:02] Failed to get "/serverlist/1/20/" from valve607.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:04] Failed to get "/serverlist/1/20/" from valve610.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:06] Failed to get "/serverlist/1/20/" from valve606.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:08] Failed to get "/serverlist/1/20/" from valve618.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:10] Failed to get "/serverlist/1/20/" from valve616.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:12] Failed to get "/serverlist/1/20/" from valve603.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:14] Failed to get "/serverlist/1/20/" from valve712.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:16] Failed to get "/serverlist/1/20/" from valve711.steamcontent.com (HTTP Error 401)
[2018-07-10 15:22:18] Failed to get "/serverlist/1/20/" from valve602.steamcontent.com (HTTP Error 401)

 

Any ideas?  

Link to post
On 7/10/2018 at 2:19 PM, cheesemarathon said:

@Shamalamadindong

I have just pushed a new update to the oauth2 image, so check for updates for you containers and you should be able to install it. This will grab the two default templates and save them to your oauth2 app data folder in a folder call templates. These will not be used by default. To enable them, edit the oauth2_proxy.cfg file and uncomment line 24:


# custom_templates_dir = "/etc/oauth2/templates/"

Restart the container and it will then use the html templates. One for the sign in page and one for the error page. The templates are exactly the same as the default login pages but can be modified to look however you want. I'll try to create some different themed pages when I have some more time. Any suggestions?

 

 

For the templates? A fake FBI login ?

 

Seriously though great work! I'll have a look at making something for myself this weekend.

 

Edit: Had a quick look, i think you forgot to generalize the template ;)

Edited by Shamalamadindong
Link to post
  • 2 weeks later...

I was nearly done deploying a different solution when I found this. The great info here helped me work out the other one. But I would like to switch to this, mostly because there is this budding community around your work.

 

Some questions on this:

  1. If run with certain parameters (i.e. cache size, etc), is it possible to change those parameters without losing the cache that has built up. Would one simply 'docker stop' followed by 'docker run' with the revised parameters?  Or would that wipe out the cache?
  2. Regarding CACHE_MAX_AGE, would it be appropriate for someone with really truly incredibly bad internet to set this to thousands of days so that a potential reinstall two years later would still be cached if the content hadn't changed? Or is there an overriding reason to keep max age short?
  3. Does anyone know if it is possible to copy the cache effectively from one server to another. Technically, from one nginx-based lancache docker to another?

Thanks much.

Link to post

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.