One risk is that with some ISP's, the IP address can be geo located down to the neighborhood. It might be smart to use a tunneling service like https://ngrok.com/ or https://pagekite.net/, which essentially sets up a server somewhere else, which then forwards the traffic to your PC. But your viewers only get the IP of that server. Source: 12 months ago
The story so far: I am creating a very, very simple website. So far, it is only an image and some text. I want to expose this website to the world, but my router is behind CGNAT. So, I use a tunnelling tool to expose it to the internet, then will use a domain to redirect it to the tunnel. I use pagekite to do this, since they have free 'permanent' subdomains (I cannot change every time I get a new ngrok link, not... Source: about 1 year ago
I haven't used them, but there are past posts mentioning LocaltoNet, PageKite, and ZeroTier. Source: over 1 year ago
Try https://pagekite.net to make your localhost server public. Source: over 1 year ago
To share out of your network I suggest you to do it through pagekite.net and you can add an extra password access there, or you can just share and ssh port through pagekite and create a dynamic tunnel each time you want to access to that website. NOTE: pagekite will limit you up to 2.5gb monthly free. Source: over 1 year ago
Cloudflare tunnels will be able to see your traffic (I assume in this case: matrix communications are e2ee and only metadata can be collected). I would recommend using https://pagekite.net that allows you to terminate TLS connections on your machine at home instead of a server in the cloud. I would also like to share my setup which is a bit different. Source: over 1 year ago
Btw, this is what http://pagekite.net/ is for. Tl;dr reverse proxy service to tunnel out of your network and give you an external ip. Source: about 2 years ago
I thin local hardware makes more sense for LAN-only sites - e.g. a company wiki, a media center or a file storage with web interface. For anything that is supposed to be visible on the internet, I'd always serve the site from the data center - if nothing else, because I really don't want to open an ingress into my personal home network, even if my ISP permitted that. For use-cases were you have to handle... - Source: Hacker News / over 2 years ago
Basic usage, gives `http://localhost:80/` a public name: $ pagekite.py NAME.pagekite.me To expose specific folders, files or use alternate local ports: $ pagekite.py /a/path/ NAME.pagekite.me +indexes # built-in HTTPD $ pagekite.py *.html NAME.pagekite.me # built-in HTTPD $ pagekite.py 3000 NAME.pagekite.me # HTTPD on 3000 To expose multiple local servers (SSH and HTTP): $ pagekite.py... Source: over 2 years ago
Do you know an article comparing Pagekite to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Pagekite. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.