Frequently Asked Questions

Why does my eepy.page domain use HTTPS?

Unfortunately, Google started forcing HTTPS for all .page domains, including eepy.page. We know this is not ideal, but this is a registry-level requirement, so there's nothing we can do about it. However, if you would like to expose a local HTTP-only service to the internet with eepy.page, it's still possible. We recommend using Caddy, a super simple reverse proxy that automatically handles HTTPS for you.

How do I set up Caddy?

Install Caddy using the instructions for your operating system at caddyserver.com. Then create a Caddyfile (no extension) with your eepy.page hostname and the local port where your app runs:

your-subdomain.eepy.page {
    reverse_proxy localhost:3000
}

Replace your-subdomain.eepy.page with your hostname and 3000 with your app's local port. Start Caddy from the directory containing the file:

caddy run

Caddy can obtain and renew certificates automatically when the hostname points to the machine running Caddy and ports 80 and 443 are reachable. For a local-only service behind the eepy.page tunneling feature, follow the tunnel setup steps on the tunneling page as well.

eepy.page tunneling

How does eepy.page tunneling work?

eepy.page tunneling uses Serveo. We provision the DNS records needed for a Serveo tunnel, then you create and configure your SSH key and domain in your Serveo dashboard before running the generated SSH command from eepy.page.

Help, I'm having some issues with my tunnel!

Serveo typically works well, but it's also not the best option for eepy.page. The setup process is more complicated than we'd like, and it doesn't always work as smoothly as we hoped for. You may experience subpar uptime, TLS/SSL issues, or interstitial warning pages that require a paid subscription to remove.

If you were meaningfully impacted by an issue with your tunnel, please reach out to support@eepy.page for potential compensation, however, we cannot help you if your issue is on Serveo's side or if it's caused by a limitation of their service.

We don't want to fearmonger though, as tunneling can work flawlessly once you get it set up. Don't let this scare you away from giving it a try!

We are actively working on finding a better solution that makes tunneling easier, more user-friendly, and more stable. Until then, contact support@eepy.page if you encounter any issues. We are more than happy to help!

What should I remove when deleting a tunnel?

Delete the tunnel from eepy.page first. Then open your Serveo dashboard and remove the SSH key and domain associated with it. This prevents unused Serveo configuration from remaining on your account.

Where can I get help?

If you have any questions not answered by the FAQs above, contact support@eepy.page and we will get back to you shortly.