Works with `next dev` on port 3000
Developer Guide
Written by Casper Fenger Jensen • Updated 2026-04-14
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.
Next.js development often needs HTTPS for auth providers, secure cookies, embedded browser features, and remote callbacks. Bore keeps `next dev` local while still giving you a real HTTPS origin for the outside world.
Install Bore
curl -sL https://bore.dk/install.sh | bashUseful for auth providers and secure cookies
Stable namespaces reduce callback URL churn
How It Works
Simple local workflow, real HTTPS externally
Step 1
Start Next.js in development mode
Run your normal Next.js dev server on localhost:3000.
Step 2
Create the HTTPS tunnel
Expose the running Next.js server with Bore and use the returned HTTPS URL in provider or callback settings.
bore up 3000Step 3
Reuse the same namespace later
Persistent namespaces make auth and preview setups less fragile across restarts.
Step 4
Reserve an API child host when needed
Keep the Next.js app on the root hostname and route an API child host to another local service.
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 run Next.js dev on HTTPS?
The fastest route is to run Next.js normally on localhost and expose it through Bore. That gives you a real HTTPS URL without local certificate management.
Is there a free HTTPS option for Next.js development?
Yes. Bore can give your local Next.js app a free HTTPS URL for development and testing flows.
Can Bore help when my app and API need separate origins?
Yes. Bore supports reserved child hosts, so the app can stay on the main namespace and the API can move to a child host with its own HTTPS URL.
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 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 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.
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.