Kit AppStream cannot be configured On public websites

Omniverse Core Platform Kit SDK
1

My goal is to access the Kit project running on the server from a mobile device.
I have tried to configure the server under the local settings to my IPv4 (and made sure that all required ports are open).
If the server is filled in as a URL or the server’s IPv4,console will output :

xxx.cn/:1  Access to fetch at 'http://xxx/' from origin 'http://xxx.cn' has been blocked by CORS policy: Method OPTIONS is not allowed by Access-Control-Allow-Methods in preflight response.

If the server is set to localhost or 127.0.0.1 , then:

index.js:2  WebSocket connection to 'ws://127.0.0.1:49100/sign_in?peer_id=peer-6621654090&version=2' failed:
2

Yes, unfortunately, I believe this streaming system is not designed for WAN applications like this. Just for LAN. Just local area networks. Your mobile device my not be able to receive this stream. However, I will check with the dev team.

Just for additional options, I asked ChatGPT about this and I got the following reply. It may be worth a look.

The error you’re encountering is related to CORS (Cross-Origin Resource Sharing) policy. Here’s a breakdown of the issue and how to resolve it:

Error Explained

  1. Preflight Request:
  • When your application sends a cross-origin request (e.g., from http://xxx.cn to http://xxx), the browser first sends an OPTIONS request (preflight) to check if the server allows the actual request method (e.g., GET, POST).
  • The server must respond to this OPTIONS request with appropriate CORS headers.
  1. Cause of the Error:
  • The server’s CORS policy does not include the OPTIONS method in the Access-Control-Allow-Methods header of its preflight response.
  • This blocks the browser from proceeding with the actual request.

Solution Steps

  1. Update Server CORS Configuration:
  • Ensure the server explicitly allows the OPTIONS method in its response header:

makefile

Copy code

Access-Control-Allow-Methods: GET, POST, OPTIONS
  • Example server configuration for Node.js with Express:

javascript

Copy code

app.use((req, res, next) => {
  res.header("Access-Control-Allow-Origin", "*");
  res.header("Access-Control-Allow-Methods", "GET, POST, OPTIONS");
  res.header("Access-Control-Allow-Headers", "Content-Type");
  if (req.method === 'OPTIONS') {
    res.sendStatus(200);
  } else {
    next();
  }
});
  1. Verify CORS Middleware:
  • If using a framework or middleware to handle CORS (e.g., Flask-CORS, Django-CORS, or CORS plugins in NGINX/Apache), ensure it includes OPTIONS in the allowed methods.
  1. Debug Preflight Response:
  • Use browser developer tools or tools like curl or Postman to inspect the preflight OPTIONS response. Ensure:
    • Access-Control-Allow-Methods includes OPTIONS.
    • Access-Control-Allow-Origin matches or is set to *.
  1. Check Server Logs:
  • Look at the server logs to confirm that the OPTIONS request is being received and processed correctly.
  1. Temporary Workaround (Not Recommended for Production):
  • You can disable CORS checks in your browser for testing purposes (e.g., using browser flags or plugins). However, this should never be used in production as it compromises security.

Example Response Headers for CORS

A correct preflight response should look like this:

mathematica

Copy code

HTTP/1.1 204 No Content
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type
3

Thank you Richard, I have a few more questions, such as how to configure the ‘stream’ in stream.config. If it’s set up correctly, would the server.source work over a LAN? Since I’m only using one server for a POC, I don’t want to use the DOCKER+K8S scenario for such a small-scale test—it’s too complicated for me.