Real HTTPS URL for localhost
Developer Guide
Written by Casper Fenger Jensen • Updated 2026-04-14
How to Put a Local Website on HTTPS
Expose a local website over HTTPS without managing local certificates. Bore gives localhost a real HTTPS URL for browser testing, callbacks, and webhook flows.
If you need HTTPS for a local website, the simplest path is usually to keep the app on localhost and put a real TLS endpoint in front of it. Bore does that without forcing you to wire certificate files into every local setup.
Install Bore
curl -sL https://bore.dk/install.sh | bashNo local certificate authority setup
Useful for browser APIs, callbacks, and webhooks
How It Works
Simple local workflow, real HTTPS externally
Step 1
Install Bore once
Install the CLI and keep your usual development workflow unchanged.
curl -sL https://bore.dk/install.sh | bashStep 2
Run your local site normally
Keep your website on its existing local port such as 3000, 4173, or 8080.
Step 3
Expose the port over HTTPS
Bore creates a public HTTPS URL that forwards to your local website.
bore up 3000Step 4
Reuse the same namespace later
Persistent namespaces reduce callback URL churn when you stop and restart development.
Where 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 add SSL to local dev?
If you mainly need a secure public URL, use a tunnel with real HTTPS in front of your local app. Bore does that without requiring every machine to trust a local certificate authority.
Can I make a local website HTTPS for free?
Yes. Bore can give your local website a free HTTPS URL for development and testing flows.
When should I use local certificates instead?
Use local certificates when the process itself must terminate TLS on localhost. Use Bore when the main goal is secure external access to the local app.
Related Guides
More HTTPS development guides
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.
How to Open Localhost on HTTPS From Your Phone or Another Device
Test a local app or API on a phone, tablet, or another laptop over HTTPS without opening your whole machine to the internet or sharing raw LAN URLs.
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.