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 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.
The text was updated successfully, but these errors were encountered:
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.
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".
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.
The text was updated successfully, but these errors were encountered: