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
In my case I want to expose a port via localtunnel on my server at home, but this seems to take over the port and I'm not able to access it via local network IP anymore. Let's say I have an a REST API hosted at 192.168.1.100:9000
lt -s testrestapi9000 -p 9000
This works and I can now hit my endpoint via https://testrestapi9000.localtunnel.me/api but when I hit 192.168.1.100:9000/api, it times out.
Is this by design? Or is there a config I need to set to be able to hit both?
The text was updated successfully, but these errors were encountered:
In my case I want to expose a port via localtunnel on my server at home, but this seems to take over the port and I'm not able to access it via local network IP anymore. Let's say I have an a REST API hosted at
192.168.1.100:9000
lt -s testrestapi9000 -p 9000
This works and I can now hit my endpoint via
https://testrestapi9000.localtunnel.me/api
but when I hit192.168.1.100:9000/api
, it times out.Is this by design? Or is there a config I need to set to be able to hit both?
The text was updated successfully, but these errors were encountered: