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

LM Studio picking wrong interface to listen on #415

Open
alyandon opened this issue Feb 6, 2025 · 1 comment
Open

LM Studio picking wrong interface to listen on #415

alyandon opened this issue Feb 6, 2025 · 1 comment

Comments

@alyandon
Copy link

alyandon commented Feb 6, 2025

LM Studio 0.3.6
Windows 10

I have a relatively tame networking setup on my desktop and the LM Studio application is picking the wrong interface to listen on when enabling the built in server functionality. In this case, it is picking a VPN interface instead of the local LAN adapter. I'm currently able to work around the issue by briefly disabling my VPN connection before running LM Studio.

Regardless, there is never going to be a one-size-fits-all scenario where an application can correctly guess which interface is the correct one to use. Please consider adding a drop-down or a text box to allow the user to configure the interface explicitly - for example, 0.0.0.0:1234 for all interfaces, 192.168.1.100:1234 for a specific interface, etc. Corresponding command line options for the lms command line tool would be nice to have as well.

@Sausage-SONG
Copy link

Exactly the same problem here (Win10, 0.3.9 Build 6), it chooses to listen on my tailscale network. I found this configuration file ~/.lmstudio/.internal/http-server-config.json which has an item called networkInterface.

{
  "autoStartOnLaunch": false,
  "port": 1234,
  "cors": false,
  "logSensitiveData": true,
  "verbose": false,
  "logLinesLimit": 500,
  "networkInterface": "0.0.0.0",
  "justInTimeModelLoading": true,
  "fileLoggingMode": "succinct",
  "jitLoadingTTLSettings": {
    "enabled": true,
    "ttlSeconds": 3600
  }
}

However, setting networkInterface to 0.0.0.0 will not help. Seems like this file corresponds to the interface below, and networkInterface is simply controlling that switch "Serve on Local Network".

Image

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