Having trouble self-hosting the server

[TheBoroer]

@TheBoroer first of all thanks for keeping this project alive!!!

Secondly, I am currently trying to self host this on my website. I've pointed my dns records and all and when I run the lt command on the local client machine, the server shows that it got a request and the client gets the url. But apart from that nothing happens - the browsers return 404 and after sometime the client connection automatically drops.

Can you please help me out in how it set yours up?

Originally posted by @mridah in https://github.com/localtunnel/localtunnel/issues/343#issuecomment-1227699328

[TheBoroer]

Hey @mridah! Could you please give me more info on how you set it up?

• You pointed domain.com and *.domain.com to your server IP right?
• What command + arguments do you start your localtunnel server with?
• When the client connects to your server; do they output a subdomain url under your domain?

My setup is super complicated since I run a couple certbots to get me the free letencrypt ssl certs (and they sometimes break but i haven't figured out exactly why it happens). If you're ok with running the server via docker containers then I can take some time and simplify my setup a bit and share the docker-compose file on this repo.

[smashah]

@TheBoroer

https://github.com/localtunnel/server/issues/169#issuecomment-1236393308

Do you not have merge/write access to this repo/npm package?

[TheBoroer]

Hey @smashah I have access to merge stuff into the github repo but no permissions to push to npm

[smashah]

Ok so then what's the blocker on merging all the existing PRs and the changes from your fork which seems to be the most up-to-date/maintened? Shall we all just use your fork? What's going on?