jakuzure

Same thing happened to me, any news on this issue yet?

Thanks for the quick reply, I'll try it out!

same thing for changes regarding a custom registry, so /etc/rancher/rke2/registries.yaml those only become active after rke2-{agent,server} was restarted

> same here, did anyone solve this issue? not yet, but I think it might have something to with the Battle.net launcher wanting to update but failing to do so....

> I've had this problem and Diablo 4 started working for me after I turned on ESync. (I'm running through Crossover, not Whisky, but I think this fix is relevant...