You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Just in case the developers or users haven't noticed, localtunnel has been terrible (no offense) for the past year now. There has been an ongoing issue of the "502 Bad Gateway" error, which isn't actually caused by users. It is caused by whatever is running localtunnel. It does not appear to have a cause, it just will randomly show this 502 page every few browser refreshes. On the other hand, even when my tunnel IS running, it sometimes also gets a "404" as if it's not running, even if I get past the 502 error. And even after all of that, if I'm lucky, my page will show up in a corrupted format after loading for a really long time, and it seems like the full content of the page isn't even getting transferred to my browser. This is not just an issue with me, everyone is having this issue; and it's kind of sad to see localtunnel like this.
I don't want to put any pressure on the developers (like @TheBoroer) but is there any way this will ever be fixed? Or at least better than it is now? Because as it stands, localtunnel is completely unusable and useless. I've moved onto other tunnel providers in the past few months, such as serveo.net and ngrok, but these also have their limitations. Ultimately, I would love to use localtunnel again, but like I said, it doesn't work anymore. Please, if there's anything anyone can do, at least try.
Thanks.
The text was updated successfully, but these errors were encountered:
Hey again @Parking-Master!
lol I'm so curious...what do you use localtunnel for?? I swear you notice EVERY issue or downtime with the service haha.
Honestly, I appreciate you pinging me when things are busted and I've either forgotten to look into it or the todo has been sitting on the backburner for way too long. 🙏
RE: 502 errors
I've looked into it over the last week or so and have done a bunch of tweaks to try to figure out what the root cause of the issues is. I'm 90% sure it's just another period where some IPs are spamming the server since i've noticed my rate limiting logic has been activated way more than before.
I'm still trying a few more things to get this under control so stay tuned. In the meantime, the 502s are intermittent and should go away after a refresh.
lol I'm so curious...what do you use localtunnel for?? I swear you notice EVERY issue or downtime with the service haha.
@TheBoroer LOL - 😁 I just host a simple Node.js mailing tool on my local network (for a personal project) and I've used localtunnel for the past few years to access stuff like this publicly. In the coming months though, I'd like to host a few more personal projects that I can access publicly through localtunnel, and if possible, even stream some websockets too.
Thank you for taking a look at the issue and acknowledging. It is great to know that you still actively maintain localtunnel. Also, once the 502 problem is fixed, I'm sure the service should be mostly working again.
Hi. Just in case the developers or users haven't noticed, localtunnel has been terrible (no offense) for the past year now. There has been an ongoing issue of the "502 Bad Gateway" error, which isn't actually caused by users. It is caused by whatever is running localtunnel. It does not appear to have a cause, it just will randomly show this 502 page every few browser refreshes. On the other hand, even when my tunnel IS running, it sometimes also gets a "404" as if it's not running, even if I get past the 502 error. And even after all of that, if I'm lucky, my page will show up in a corrupted format after loading for a really long time, and it seems like the full content of the page isn't even getting transferred to my browser. This is not just an issue with me, everyone is having this issue; and it's kind of sad to see localtunnel like this.
I don't want to put any pressure on the developers (like @TheBoroer) but is there any way this will ever be fixed? Or at least better than it is now? Because as it stands, localtunnel is completely unusable and useless. I've moved onto other tunnel providers in the past few months, such as serveo.net and ngrok, but these also have their limitations. Ultimately, I would love to use localtunnel again, but like I said, it doesn't work anymore. Please, if there's anything anyone can do, at least try.
Thanks.
The text was updated successfully, but these errors were encountered: