Hi there,
I’m working on streaming the USD Composer app using the latest kit-app-template (v.106) and the web-viewer-sample code.
The client is able to connect to the initial page, but when trying to move to the next one, it seems to get stuck in a retry loop.
Here is the error message:
Is there something I might have missed or a setting I should check to fix this? Any advice would be appreciated!
Thank you
It looks like you are having a security permissions problem connecting to one of our java scripts. Are you on a corp network with corp security? The next page, has to establish a live connection to that code. Maybe you have an internal firewall, or network or browser security preventing you from running the script required.
I’m having the same problem.
I’m testing by deploying on an Azure VM, I’ve lowered the firewall, as well as the one on my computer, and I still get the same error.
I also deployed a pod in k8s, I deployed a service to set up a load balancer and I have the same error.
Have a look at the Network exchange tab in the Chrome’s developer’s console while you navigate this menu and see if and where the http calls fail.
I share more information.
Here I have my two pods (web) and (kit-app)
This is my kubernetes service: This will bring up a load balancer.
This is the load balancer in azure:
chrome error:
dev tool:
console dev tool:
console dev tool
thanks!
Please check the Chrome’s developer’s console and the network tab there, not the k8s service.
Sorry, I already updated the message
A few questions:
http://<the URL/IP you masked>:49100/sign_in as in can you curl it?
I created it from the project, then I containerized it
I have created it from the project, followed all the steps and then containerized with the containerize option.
I created the manifests manually in both.(k8s)
The request works.(from my machine to the load balancer IP)
wscat -c ws://ip-server:49100/sign_in?peer_id=peer-272772&version=2
note:
I also did this in an Azure VM (Windows), there I did not containerize it but only ran it (web → npm run dev , kit-app ->.\repo.bat build )
If I enter via remote desktop it works within the machine.
But if I expose the public machine, open input and output ports, firewall rules, it does not work from my PC.
Ahhh… what a minute here. You are trying to stream from Azure VM, and then view that stream on your local desktop, through the public internet? No, that will not work. You cannot cross domains like that, ports open or not. The streaming sample is NOT designed to cross domain policies. No where in your previous posts did you mention that you are trying to stream through the open public internet.
The streaming “sample” is designed as a “local only” sample. Your laptop to your desktop, your desktop to your laptop. Your enterprise workstation, down to the boardroom Monitor. A central RTX super cluster to a lab workstation. Anywhere you are in a closed loop network. Even if you run it on K8s, you are only streaming to a machine WITHIN the closed network, and then for viewing remotely, across the open internet, you would need to use standard remote viewing software, that IS designed to cross public domains. Like remote desktop.
In your case, you are using an Azure VM, correct? So you would simply use “Azure Monitor” that is free with Microsoft Azure to view your “local” stream running in the VM coming into the VM web browser, as you show it. That is why it works with Remote Desktop. It is working, but it is not designed to “get out” of the VM loop.
If you want a full remote streaming solution, you will need to deploy an app to our GDN (Game Developer Network) for proper wide remote viewing from a central RTX server.
Thank you for your response.
Currently, I am behind a firewall but using wildcard permissions. In my case, the entire environment is deployed locally, without the involvement of VMs or cloud services. I have both the web-service-kit and the kit-app service running within the same local network, and I am attempting to use only HTTP connection to allow a public client to access it .
As mentioned earlier, the sample code is intended for use within a local network. Does this mean the NodeGroup -GPU on the right side of the diagram needs to be in the same local network? Please feel free to correct me if I’m mistaken.
Thanks again for your help
Could you guide me on how I could deploy the product in a Kubernetes (AKS) environment with public access?
With OVAS (Overview — Kit App Streaming API) could I achieve this? However, where could I have the web application for transmission? In the diagram (https://docs.omniverse.nvidia.com/ovas/latest/_images/ovas_arch_azure.png)
I see where it would be deployed.
@ziro I would assume that ALL network components need to be in the “local” group yes. Especially the GPU.
