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

How are you using Tunnelmole Service? #14

Open
robbie-cahill opened this issue Oct 17, 2024 · 1 comment
Open

How are you using Tunnelmole Service? #14

robbie-cahill opened this issue Oct 17, 2024 · 1 comment

Comments

@robbie-cahill
Copy link
Owner

I'd like to know more on how people are using the self hosted Tunnelmole Service.

  • What are you building with the service?
  • Any reason you went with self hosting, rather than using the SaaS service i.e. compliance, being able to use your own domain or wanting to maintain full control?
  • How did it go?
@Somnath-Pandey-Vested
Copy link

Hello @robbie-cahill i am trying to self host the tunnelmole service as i want to have custom sub domains to be used instead of getting it from the subscription.

The service setup is working fine like the output below
node dist/srv/index.js Tunnelmole Service listening on http port 8000 Tunnelmole Service listening on websocket port 8080

But for me the issue is coming up with client. when i tried to setup the client and run the command node dist/src/index.js 3000 it should give me the urls according to the documentation. But i am not getting any URL's and also there is no error coming up in output. I have tested whether the webscoket connection is working fine by doing wscat -c ws://<mydomian.com>:8080 .Its getting conected.

If you can help me out why the client is not able to generate the urls.

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

2 participants