Works with Vite's normal local port
Developer Guide
Written by Casper Fenger Jensen • Updated 2026-04-14
How to Use Vite on HTTPS Locally
Test a Vite app over HTTPS without switching your development workflow to custom local certificates. Bore gives your Vite dev server a real HTTPS URL in one step.
Vite developers often need HTTPS for service workers, secure browser APIs, mobile testing, or integration callbacks. Bore makes that easier by putting a real HTTPS URL in front of the existing Vite dev server.
Install Bore
curl -sL https://bore.dk/install.sh | bashUseful for service worker and browser API testing
Can expose a separate HTTPS API origin too
How It Works
Simple local workflow, real HTTPS externally
Step 1
Run the Vite app locally
Keep Vite on its usual development port, commonly 5173.
Step 2
Expose Vite through Bore
Use Bore to create an HTTPS URL for the Vite app without teaching the app to manage certificates.
bore up 5173Step 3
Use the HTTPS URL for testing
Open the Bore URL on desktop or mobile devices and use it for secure browser feature testing.
Step 4
Route a child host to a separate backend when needed
Bore can reserve an HTTPS child host for a local API on a different port.
bore host add <namespace> api
bore host set-port <namespace> api 3001Where Bore Differs
Bore can keep HTTPS on reserved child hosts too
Most tunnel workflows stop at one public hostname. Bore can keep your main app on one HTTPS namespace and reserve a child host like `api.<namespace>.bore.dk` for a second local service.
bore host add <namespace> api
bore host set-port <namespace> api 3001That matters when frontend and API origins need to stay separate in local development, or when webhook, auth, and admin traffic should not all share one hostname.
FAQ
Common questions
How do I try a Vite app on HTTPS locally?
Run Vite normally and expose the port with Bore. You get a real HTTPS URL without setting up and trusting local certificates.
Can I use Bore for mobile and browser testing with Vite?
Yes. Bore gives your Vite server a public HTTPS URL that can be opened from other devices and external integrations.
Can the API use a different HTTPS hostname than the Vite app?
Yes. Bore supports reserved child hosts so your Vite app and local API can use separate HTTPS origins during development.
Related Guides
More HTTPS development guides
How to Put a React App on HTTPS in Development
Expose a React development app over HTTPS for secure browser APIs, embedded flows, mobile testing, and auth callbacks without setting up local certificate chains.
How to Run Next.js Dev on HTTPS
Use Next.js locally with a real HTTPS URL for auth flows, secure cookies, preview links, and webhook callbacks. Bore exposes Next.js dev over HTTPS without local certificate setup.
How to Run Node.js, Express, Fastify, or NestJS Dev on HTTPS
Run a local Node.js server behind a real HTTPS URL without wiring custom TLS code into your app. Bore works well for Express, Fastify, NestJS, and custom Node servers.
How to Expose a Local API Over HTTPS
Put a local API on a real HTTPS URL for browser clients, mobile apps, webhook callbacks, and partner integrations without adding local TLS complexity.