This is a success story, I swear! Just read until the end. I also have a few suggestions of how to better handle the topics covered.
I attempted to install the Oculus runtime so I can use Virtual Desktop game streaming with my Quest 2, however I had some issues.
When I tried to download the software, I got a 404 error on the Oculus website. I resolved this by transferring the installer (which I had no trouble downloading from Oculus.com on my local machine) to the shadow box via Google Drive. Now the issue is that when I run the installer, I get the error “Looks like we can’t reach the Oculus server. Please check your connection”.
I suspect that Oculus may be blocking the IP range which the datacenter uses, which is not a great sign for compatibility. 
Also, yes, I had added firewall rules for the installer and tried other common fixes.
I have a personal VPN I use for all of my internet traffic that runs through a datacenter in Dallas, and I know for sure Oculus isn’t blocking it because I can access the services fine through it locally. I thought I might use it to see if I can get the setup to continue, but I suspected it might interfere with the streaming ability of the Shadow client. It very much did, which is unfortunate.
HOWEVER, I had control over the VPN service (since it’s running on my private VPS), so I just killed the server for a few minutes until the client started responding again. I thought this would be an issue, but then I remembered that I had installed the Virtual Desktop streaming service on the Shadow Box, which is not IP bound (it uses a third party server to bounce the client connection to the Oculus ID you provide, which I guess makes it VPN proof). So, I started the VPN service again after running the VD server, and I was able to begin downloading Oculus software successfully!
Streaming wasn’t at all smooth, but I still very much loved using the shadow box for VR streaming!
I can say I thoroughly enjoyed the experience of troubleshooting this issue, however I understand that most people probably wouldn’t, so I have a few thoughts on how the service could be improved:
- There should be an ability to hot-reboot the VPS without needing to completely reset it. I don’t know how you have the VM clusters configured, but I can’t think of any configuration under which this wouldn’t be possible to implement. The “Shut Down Shadow” feature doesn’t seem to be consistently able to reach the VM, so having something in the client area to just force a reboot (kinda like you’d get with most VPS services) would be a good idea.
- Failing this, some sort of safe-mode boot would suffice. One which mounts the VM drive and gives access to the registry or something like that. Getting locked out of a VPS is a fairly common issue, and having a solution that isn’t “Nuke the SSD” would be a good idea.
- VPN passthrough should probably be a thing, even if it’s some janky feature to use your local IP to do stuff. I imagine there are a great many services that will have blocked some or most of the datacenter IPs you are using to host the VMs.
