-
Notifications
You must be signed in to change notification settings - Fork 998
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
Having trouble self-hosting the server #184
Comments
Hey @mridah!
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. |
Do you not have merge/write access to this repo/npm package? |
Hey @smashah I have access to merge stuff into the github repo but no permissions to push to npm |
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? |
@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 localtunnel/localtunnel#343 (comment)
The text was updated successfully, but these errors were encountered: