put localhost on the internet
Joined February 2017
- Tweets268
- Following0
- Followers809
- Likes48
sorry to anyone that failed to get a free tunnel over the past few hours, a phishing complaint that likely came in before I added this warning triggered a domain suspension. The free tunnels are working again on a different domain name while I sort out the suspension.
for non-browser requests, and on browsers after accepting the warning, tunnels should work exactly as before, but if you have any problems please let me know and I will get them fixed.
this is to deal with a high volume of phishing complaints I have been receiving against free domains. It is less that 5 users behind all the phishing domains reported, and so they will soon move on I will revert to passing traffic thru without this warning.
hello 👋️ i have put up a phishing warning on the free domains. this is a temporary measure, it will be removed in the near future, and while it is live you can simply accept the warning and enjoy your tunnel as before.
localhost.run retweeted
Want to quickly share the local site/app with your friend? Put this snippet in your .bashrc/.zshrc and you should be good to go!
share() {
ssh -R 80:localhost:$1 [email protected]
}
Thanks, @localhost_run!
#developers #development #bash
localhost.run retweeted
I just discovered localhost.run and it is amazing.
For the @PaddleHQ integration I’m building for FeatureCat, I need to forward Paddle’s subscription webhooks to localhost on my machine.
It provides super simple SSH’ing from a public url to my Mac in seconds.
This is a blog post about localhost.run that is itself served thru a localhost.run tunnel 🤯️ 😍️
@FelixQuehl has written an awesome post about how they're using localhost.run! there are even links to the open sourced code they wrote to do this in the post 💪️ check it out! quehl.xyz/0_about.html
localhost.run retweeted
Blogged: Using SSH and @localhost_run to test @github webhooks locally buff.ly/35JKjW0 #dotnet #aspnetcore
Awesome article, thanks for using localhost.run to work on your GitHub webhooks! True story, GitHub webhooks are exactly my own use case when I wrote the first version of LHR many years ago
the bug didn't quite die, my keep-at-n system shipped the old code last night while i was asleep so there was again some down time, sorry :( code is properly committed and we're back up now, I'm awake and drinking coffee, i'll keep a very close eye on it thru the day.
I want to do it tho, so keep checking in about it, but it's not the right time yet.
there's more details on the cause in the main thread: xitter.cf/localhost_run/status/1…
if I have 1 active tunnel or 1000 it still costs me x, the nature of a server makes this cost stepped, so until I have enough paying users to cover that cost and the time cost to manage these regions i can't justify it.
regions: in this case I would likely have had the same fire, just in multiple places. and outside of the context of this outage there's cost to consider. lets say a single server can handle a few thousand active tunnels and costs me x.