Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

localtunnel gives error of bad gateway - 502 #688

Open
shrey2005 opened this issue Nov 27, 2024 · 15 comments
Open

localtunnel gives error of bad gateway - 502 #688

shrey2005 opened this issue Nov 27, 2024 · 15 comments

Comments

@shrey2005
Copy link

Issue: 502 Bad Gateway Error with LocalTunnel on React.js Project

Description: I'm encountering a 502 Bad Gateway error when using LocalTunnel with my React.jsproject. The error occurs intermittently and affects my ability to test my application locally. Below are the details of my setup and the steps I've taken to troubleshoot this issue.

Project Setup:

React Version: 19

Node.jsVersion: 22.3.0

LocalTunnel Version: 2.0.0

Operating System: Windows 11

Steps to Reproduce:

Start the development server using npm start.

Open a tunnel using LocalTunnel with the command lt --port 3000.

Access the provided URL in a browser.

Observe the 502 Bad Gateway error intermittently.

Troubleshooting Steps Taken:

Verified that the LocalTunnel service is up and running.

Updated all dependencies to their latest versions.

Restarted the development server and LocalTunnel service multiple times.

Checked for any known issues on LocalTunnel's GitHub repository.

Expected Behavior: The application should be accessible through the LocalTunnel URL without encountering the 502 Bad Gateway error.

Actual Behavior: The 502 Bad Gateway error occurs intermittently, preventing access to the application.
localtunnel issue

Request for Help: I would appreciate any guidance or suggestions on how to resolve this issue. If there are any additional logs or configurations needed, please let me know.

@Jianlong-Nie
Copy link

Same issue +1

@tshtark
Copy link

tshtark commented Dec 3, 2024

same

@fatihsevimtc
Copy link

same here

@theSilver32
Copy link

same

@UndeadZed
Copy link

same did anyone manage to find a solution to this?

@kggayo
Copy link

kggayo commented Dec 19, 2024

same here

@Bokobelin
Copy link

Same

@Marius-Mulama
Copy link

Same Here

@dougj-contrast
Copy link

following this works, find your public IP and use as password...

#598

@NguyenTaiAnh
Copy link

Same

@tarjep
Copy link

tarjep commented Jan 6, 2025

Same here

@Yasirmnd
Copy link

Yasirmnd commented Jan 8, 2025

Same here. It has been happening since many weeks.

@Gostron
Copy link

Gostron commented Jan 10, 2025

same here

@TheBoroer
Copy link
Collaborator

Hey all, the 502's are used by a bunch of people spamming the server with random requests. It's causing some ngnix issues, docker routing errors, and constant near-100% cpu usage 😞

I'll be adding some rate-limiting to ngnix + doing a few more optimizations that should hopefully help.

I'll post an update when I have one but in the meantime, the 502s dont last very long and usually go away by the time you refresh.

@JamesPoel
Copy link

Same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests