ZuploZuplo
LoginSign Up
  • Documentation
  • API Reference
Introduction
Getting Started
    Develop using the Portal
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth4 - Deploy5 - Dynamic Rate LimitingMCP - Quick start
    Develop Locally
      1 - Setup Your Gateway2 - Rate Limiting3 - API Key Auth
Concepts
Development
    CORSEnvironment VariablesBranch-Based DeploymentsTestingTroubleshootingGitOps vs TerraformCustom Code
    Local Development
      QuickstartRoutes DesignerInstalling PackagesZuplo ServicesDebuggingEnvironment variablesTypeScript ConfigTroubleshooting
    Guides
Policies
Handlers
API Keys
MCP Server
MCP Gateway
AI Gateway
Developer Portal
Monetization
Deploying & Source Control
Observability
Networking & Infrastructure
Account Management
Programming API
Build with AI
Zuplo CLI
Migration Guides
Platform LimitsSecuritySupportTrust & ComplianceChangelog
powered by Zudoku
Local Development

Troubleshooting

Changing the port numbers

By default the Zuplo local server runs on port 9000 and route designer runs on port 9100. To change the port number, you can call

TerminalCode
npx zuplo dev --port <port number> --editor-port <editor port number>

Certificates Errors

When running Zuplo locally you may want to call a service with a self-signed certificate. By default this isn't supported - we recommend using signed/trusted certificates in deployed environments. However, for local development you can ignore certificate errors by adding the --unsafely-ignore-certificate-errors flag on the zuplo dev command.

Run your development server with the following command:

TerminalCode
npx zuplo dev --unsafely-ignore-certificate-errors

If you want to update your package.json to always allow self-signed certificates, you can add the following script:

Code
{ "scripts": { "dev": "zuplo dev --unsafely-ignore-certificate-errors" } }

Updating the Zuplo CLI

To update the CLI, run the following command in your project directory.

TerminalCode
npm install zuplo@latest

You must include the @latest to ensure you are getting the latest. Otherwise, you could have an older version cached locally on your machine.

You can compare if you have the latest version by looking at the version number on NPM

Getting help

Please reach out to support@zuplo.com or join our Discord server.

Edit this page
Last modified on March 23, 2026
TypeScript ConfigAdvanced Path Matching
On this page
  • Changing the port numbers
  • Certificates Errors
  • Updating the Zuplo CLI
  • Getting help
JSON