origin_not_allowed

HTTP status: 403 · Code: origin_not_allowed

The browser origin matches none of the project’s web platforms.

Why it happens

A browser called Orvano from an origin that matches none of the project’s Web platforms. Browsers send the page’s origin with every call, and Orvano only answers ones you added.

How to fix

In the console, open the project’s Platforms and add a Web platform with your site’s hostname. localhost covers every port, so one platform covers next dev, Vite, and Flutter web on your machine. See Platforms.

Catch it in your code

Every SDK throws one error type for a failed call. Match on its code, which is always origin_not_allowed for this error, never on the message.

JavaScript and Next.js

import { ErrorCode, OrvanoError } from '@orvano/js'

try {
  // your Orvano call
} catch (error) {
  if (error instanceof OrvanoError && error.code === ErrorCode.originNotAllowed) {
    // handle origin_not_allowed
  } else {
    throw error
  }
}

Dart and Flutter

import 'package:orvano_flutter/orvano_flutter.dart'; // or orvano_dart on a server

try {
  // your Orvano call
} on OrvanoException catch (error) {
  if (error.code != ErrorCode.originNotAllowed) rethrow;
  // handle origin_not_allowed
}

.NET

using Orvano;

try
{
    // your Orvano call
}
catch (OrvanoException error) when (error.Code == ErrorCode.OriginNotAllowed)
{
    // handle origin_not_allowed
}

The error also carries the HTTP status (403), a message, and a request ID. Quote the request ID when you report a problem: the server logs it with the failure. See Errors for how errors work in every SDK, or every error code.