Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubisoft Connect no longer caching #195

Open
TheRedHerring95 opened this issue Jul 25, 2024 · 2 comments
Open

Ubisoft Connect no longer caching #195

TheRedHerring95 opened this issue Jul 25, 2024 · 2 comments

Comments

@TheRedHerring95
Copy link

Describe the issue you are having

Ubisoft Connect downloads are no longer caching. Traffic is going through the VM, but the cache is ignoring it and passing straight through. It shows a small amount initially in the logs, but then drops and ceases storing the data. Only occurring on Ubisoft

Calculated guess: Did Ubisoft switch to HTTPS or similar for downloads?

How are you running the container(s)

Separate Ubuntu VMs running LANCache DNS and LANCache Monolithic.
Default docker-compose file with modified upstream DNS (Quad 9) and mapped locations to reflect my needs. Cache location maps to an NFS share, which I can see the traffic to as an addition while downloading cache misses.

DNS Configuration

Adguard Home pointed to LANCache-DNS VM, LANCache-DNS points to a separate VM with LANCache and Quad9 for upstream

Output of container(s)

Sample of what happens while downloading Ubisoft games
image
Sample of what happens when downloading Battle.net games (which properly cache).
image

Happy to provide any other details needed, including the actual docker-compose file and my .env variables

@WhiteBoi1211
Copy link

Hey, running into the same issue here. Did you find a fix?

@TheRedHerring95
Copy link
Author

I didn't find a fix, but I haven't tried it in a while. My understanding, from what I could piece together and how it seemed to be behaving, is it's likely got to be fixed on Ubisoft's end, and I don't expect that will likely happen.

If I'm right about it being HTTPS/TLS encrypted, then the encryption may be able to be stripped out to recover it, as I seem to remember that being something that was explained as a solution back before Origin added the option to disable TLS, but I'm not sure if that would still work with modern TLS/HTTPS, and either way I certainly don't consider it something worth going through the process of trying, particularly with no guarantee that 1) it is even that that's caused it, and 2) that it would work with modern TLS/HTTPS encryption.

That said, I'm not an expert in it, and the bit I ready about EA was years ago, so I may not even be remembering that correctly; someone else with a proper understanding on how it works is welcome to weigh in and correct me on this, I would welcome the correction and knowledge. I'm just a low level tech support guy who does LANs for fun when I can and enjoys having a homelab. (Leaving it open for someone to be able to do so should they have the knowledge and inclination)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants