Jump to content

cheesemarathon

Members
  • Content Count

    154
  • Joined

  • Last visited

  • Days Won

    1

cheesemarathon last won the day on October 25 2017

cheesemarathon had the most liked content!

Community Reputation

21 Good

1 Follower

About cheesemarathon

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. cheesemarathon

    [Support] cheesemarathons repo

    It looks like this is something that has come up before. There is nothing official supporting fail to ban, however, login attempts are written to the logs. So you should be able to use the logs with fail2ban. This is discussed in detail here. I have not set this up myself and have little experience with fail2ban, but shout if you need some help. The GitHub issue discusses setting it up with docker but not UnRAID which may make it harder or easier in place. I don't know, but do let me know how you get on. I can always create some instructions for others if we get this working. Good luck!
  2. cheesemarathon

    [Support] cheesemarathons repo

    Thanks mlebjerg 🙂
  3. cheesemarathon

    [Support] cheesemarathons repo

    @mlebjerg Have you seen this message? Something you can work on?
  4. cheesemarathon

    [Support] cheesemarathons repo

    Hi, sorry I haven't had time to look at this, however, @mlebjerg is the expert and maintainer of this version of the container so I shall message him and hopefully, he can add the option
  5. cheesemarathon

    [Support] cheesemarathons repo

    Thanks for all the info. I will spin up my instance of steamcache when I get home from work, as i'm unsure what the issue is here.
  6. cheesemarathon

    [Support] cheesemarathons repo

    In your windows pc dns settings I would not set the secondary DNS. Although you might think it would only use that if the first fails, that is not always the case depending on the application. Some times it will skip the first or just randomly chose one of the two. If you only set one, there is only one it can use. I havn't used steamcache in a bit. I'll spin up my instance when I get home tonight and see if i'm having any issues.
  7. cheesemarathon

    [Support] cheesemarathons repo

    Hey! Year very nearly there. There is just one error in your config. The "LANCACHE_IP" setting wants to be the same IP as you set in the "Fixed IP" setting. So in your case both should be 192.168.1.75 Then you should be good to go. That command you run will then output the logs from the container and you will see the cache working.
  8. cheesemarathon

    [Support] cheesemarathons repo

    Ok, background knowledge time. Docker containers run in their own self-contained environment. In order to get shell access to them you need to run the command: docker exec -it <container-name> <command> This will run the command you place in <command> in the container you specify. In unRAID you can also click the console button on the container you want, and this will open a console window in the container you specify. unRaid is effectively running the following command: docker exec -it <container-name> /bin/bash Then you can run any command you like and it will execute in then container. Therefore, you have two options. One, open a terminal window connected to your unRAID server and run: docker exec -it SteamCacheBundle tail -f /data/logs/access.log Here you can see you container name is "SteamCacheBundle" and the command is "tail -f /data/logs/access.log" Or you can open the unRAID GUI, click on the console button for the SteamCacheBundle container and then in the new window run: tail -f /data/logs/access.log I hope this clears things up for you
  9. cheesemarathon

    [Support] cheesemarathons repo

    Head to the Docker page in the unRAID GUI. Click on the icon for Steam Cache Bundle. Click "Console". In the new window that opens type then hit enter. You should then be able to continue with the instructions. If it mentions running again, do as I have instructed here again.
  10. cheesemarathon

    [Support] cheesemarathons repo

    This is not fixed yet however the issue is being looked into. There does seem to be a fix for now. Add the environment variable "DISABLE_WSUS" and set it to "true". The issue is being tracked here: https://github.com/uklans/cache-domains/issues/39
  11. cheesemarathon

    [Support] cheesemarathons repo

    Have you tried to see if this works already? The DNS forwarding should already work. If not, open an issue here as i'm not the author of the software, I just create the template with the help of @mlebjerg
  12. cheesemarathon

    [Support] cheesemarathons repo

    Yes I'm well aware that oauthproxy is no longer being developed by the owners. There is an issue that I'm subscribed to that is discusing how the project will go forward, whether that is new owners for the project or moving official support to a new fork. I'm reluctant to move to a new fork until official agreement has been made as buzzfeed sso only supports Google as an auth provider at the moment.
  13. cheesemarathon

    [Support] MarkusMcNugens Docker Repository

    Shame, his loss then....
  14. cheesemarathon

    [Support] MarkusMcNugens Docker Repository

    URGENT!!! @MarkusMcNugen It looks like with your qbittorrent template you have forgotten to remove your VPN username and password from the template. Lines 71 and 76 currently contain values. I suggest you remove them!
  15. cheesemarathon

    [Support] cheesemarathons repo

    Yeh, that's probably the best way! Not a problem, I'm here to help! Thanks for the coffee, unfortunately I'm an idiot and set it up with the wrong pay pal email. So they payment will bounce back in 30 days. Thanks anyway though!