You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
I'd like to know more on how people are using the self hosted Tunnelmole Service.
The text was updated successfully, but these errors were encountered: