Simple-proxy stuck at starting HTTP proxy - Anyone else facing this issue?

Hey everyone,

So I’ve been trying to get Simple-proxy up and running, but it’s just *stuck at starting HTTP proxy*. Like, it just hangs there, no errors, no logs, nada.

Anyone else facing this issue? I’ve tried restarting, reinstalling, and even checked the configs, but no luck.

Is there some kinda trick or setting I’m missing? Or is this a known bug?

Also, if anyone’s got a workaround, pls share. I’m kinda stuck here lol.

Thanks in advance!

(btw, running it on Ubuntu 20.04 if that helps)

Hey! I had the same issue with Simple-proxy stuck at starting HTTP proxy. Turns out, it was a port conflict. Check if port 8080 (or whatever port you're using) is already taken. You can use `sudo lsof -i :8080` to see if something else is hogging it. If it is, either kill that process or change the port in your Simple-proxy config. Hope that helps!

Yo, I faced this too! Simple-proxy stuck at starting HTTP proxy is such a pain. What worked for me was updating my Node.js version. I was on an older one, and after upgrading to Node 16, it just worked. Maybe give that a shot? Also, check out this guide on debugging Node apps: https://nodejs.org/en/docs/guides/debugg...ng-started.

Hmm, Simple-proxy stuck at starting HTTP proxy sounds familiar. Have you checked your firewall settings? Sometimes Ubuntu's UFW blocks the port. Try running `sudo ufw allow 8080` (or your proxy port) and see if that fixes it. If not, maybe share your config file (redact sensitive stuff) so we can take a look.

I had this exact issue last week! Simple-proxy stuck at starting HTTP proxy drove me nuts. Turns out, it was a permissions thing. Running it with `sudo` fixed it for me. If you're not a fan of using sudo, you could try changing the ownership of the directory where Simple-proxy is installed. Just a thought!

Hey everyone, thanks for all the suggestions! I tried a bunch of them, and it turns out it was a port conflict like @user1 mentioned. Changed the port, and now Simple-proxy is running smoothly.

I also updated Node.js like @user2 suggested, which probably helped too. Still not sure why it didn’t throw any errors, but hey, it’s working now!

Thanks again, y’all are lifesavers. If anyone else runs into Simple-proxy stuck at starting HTTP proxy, definitely check the port first!

Hey, I’ve seen this before. Simple-proxy stuck at starting HTTP proxy usually happens when there’s a dependency issue. Did you run `npm install` after setting it up? Also, check if all the required packages are installed. Sometimes, missing dependencies cause it to hang without any errors.

Simple-proxy stuck at starting HTTP proxy? Ugh, I feel your pain. Have you tried running it in debug mode? Add `DEBUG=simple-proxy:*` before your start command. It might spit out some useful logs that can help pinpoint the issue. Also, check out this thread on GitHub: https://github.com/simple-proxy/issues. Someone might’ve already posted a fix.

Hey! I had the same problem with Simple-proxy stuck at starting HTTP proxy. For me, it was an issue with the config file. Double-check your JSON formatting—sometimes a missing comma or bracket can cause it to fail silently. If you’re unsure, paste your config into a JSON validator like https://jsonlint.com/.

Simple-proxy stuck at starting HTTP proxy? Yeah, that’s annoying. Have you tried running it on a different machine or VM? Sometimes, it’s just a weird local environment issue. If it works elsewhere, then you know it’s something specific to your Ubuntu setup. Also, check your system logs (`journalctl -xe`) for any hidden errors.