-
Notifications
You must be signed in to change notification settings - Fork 57
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
WoW CAS system unable to initialize #13
Comments
Could you paste .build.info from both Client 1 and Client 2 |
There is no .build.info for either clients. |
If Client 1 is functional and has all your custom changes then it sounds like Client 2 isn't connecting to the CDN or has picked up some dodgy configs. Have you tried connecting with Client 2 after the first build? If it still doesn't work after the first build, I'd suggest deleting For the record, is this with TinyClient? If so, is this on live? |
Client 2 was connecting to the CDN as requests were being made and were visible in the CASCHost console. Client 2 couldn't connect on any of the following rebuilds. It was only able to connect after the Output folder was cleaned out and CASCHost started anew (with changes from the last time this was done included). The Data folders were emptied out in an attempt to fix this initially but were not successfl. This is with two full Battle.net clients downloaded from live and connecting into the CDN as described in the above steps. |
This WoW error is caused by unexpected CDNS behaviour, where the client cannot pull the data and therefore errors, generating an error message alike the following: Error 1, Error 2
Steps to reproduce:
Expected Behaviour:
Actual Behaviour:
When Client 2 is attempting to connect, the CASCHost outputs a lot of inexplicable 404 errors. It seems that the Client 2 is unable to access files that are a part of the custom CDNS.
The text was updated successfully, but these errors were encountered: