HTTP
HTTP tunnels allow you to expose your local web servers to the internet, you will be given a shareable URL that is accessible from the internet, This tunnel will be running in HTTP(S).
Forward a public URL to localhost:8080 in one line
loclx tunnel httpLocalXpose servers will do the TLS termination and forward the traffic for you through a secure tunnel. If you prefer to use your own custom domain (like example.com) then LocalXpose will generate a Let's Encrypt certificate for you automatically and your tunnel will be end-to-end encrypted.
For every HTTP connection from the public internet to your machine, a header X-Forwarded-For and X-Real-Ip will be added to the request so that you can get the real IP address of your clients.
Usage
Tunnel with custom temporary subdomain
loclx tunnel http --subdomain helloTunnel with custom reserved domain or subdomain
loclx tunnel http --reserved-domain hello.example.com
# or hello.loclx.io or '*.example.com'Make sure to reserve the domain before using it, check here.
Tunnel with custom wildcard domain
First reserve a wildcard custom domain, for this example we will assume our wildcard domain is *.example.com, you can run HTTP/s tunnel with any subdomain of the mentioned wildcard domain (e.g. api.example.com or dev.example.com...etc)
loclx tunnel http --reserved-domain api.example.comYou can also run the tunnel with the wildcard domain itself:
loclx tunnel http --reserved-domain '*.example.com'This will start HTTP/s tunnel with the wildcard custom domain *.example.com, you will be able to access it through the internet using:
- sub.example.com
- sub1.sub2.example.com
- sub1.sub2.sub3.example.com
- ..etc
example.com itself will not be tunneled to your wildcard custom domain, it needs to be reserved too and create a separate tunnel for it.
You can reserve multiple wildcard custom domains for the same domain name for example you can reserve *.example.com, *.uat.example.com and *.test.example.com.
The precedence here will be for the nearest match for example:
| Public URL | Matched Tunnel |
|---|---|
| sub.example.com uat.example.com test.example.com sub1.sub2.example.com | *.example.com |
| sub.uat.example.com sub1.sub2.uat.example.com | *.uat.example.com |
| sub.test.example.com sub1.sub2.test.example.com | *.test.example.com |
| example.com | No match |
Learn More
For practical examples and use cases of HTTP tunnels, check out these helpful resources:
- How to Expose Localhost to the Internet (opens in a new tab) - A complete guide to getting started
- How to Access Localhost from Another Computer (opens in a new tab) - Share your work with teammates
- Best ngrok Alternatives (opens in a new tab) - Compare LocalXpose with other tunneling solutions
- Access Local Network Remotely (opens in a new tab) - A comprehensive guide for secure connections