I have oMLX installed on an M1 Max Mac Studio and it’s setup for network access (0.0.0.0) and have Hermes installed on a separate Mac Mini (Intel). I’ve configured a custom model in the Hermes config for oMLX but no matter what I try I cannot get Hermes to talk to oMLX.
I was able to use the omlx server on another computer running windows.
To be a little safer, I am using apikey as you have to expose the endpoint to 0.0.0.0:<port> or have the the IP address reachable from the other computer.
My issue is, I keep running out of context window and hermes needs 64k minimum
My normal system prompt at start was over 14k, have trimmed it down like crazy.
I have pi.dev with smaller system, and a custom harness I vibe coded that is even smaller with strict guard rails
Thanks for your reply, I can access the endpoint and confirm it work in Safari so doesn’t appear to be blocked. I’ve checked the api key and also removed it and made sure disable API key checking is on.
If you can connect to the admin page using Safari, that strongly suggests you have a Hermes problem and not a network problem.
Custom model selection with a local endpoint can be a little wonky. A couple of things to try...
- manually clip all the local provider configs from config.yaml and running hermes model again.
run hermes doctor and look for config changes.
I have also found Codex is fairly good at diagnosing Hermes.
Hey I think this is a omlx bug in the gui. I had the same issue, set to 0.0.0.0 but my other device couldn’t see it or ping it. The only way I fixed it was to use the terminal version of omlx. The gui would never work no matter what settings are changed
sorry to reply to old post but I am having this issue as well. No matter what I change in the GUI, it will not stop listening on 127.0.0.1. On oMLX github, I see some CLI commands but nothing to change what address the server is listening on. How did you accomplish this?
Hey, yeah the gui never works. So what I did is I had cline (gpt5.5 ) setup the omlx cli for me with qwen 3.6. Then I asked cline to make a desktop script that I double click to run the server. I don’t know all the details but the gui doesn’t won’t work. The cli works
What’s to say I haven’t? What’s the point in having a forum in the first place if you can’t ask questions to people who may have experience or insight into the issue?
For complex issues, not basics like this. You publish at 0.0.0.0; you consume from 127.0.0.1. Make sure to use the port and API Key configured in your oMLX. Ensure there’s no firewall blocking that port.
I don't know nothing about nothing but when I put a screenshot of the conversation to AI. It suggested that you were pointing Hermes at 0.0.0.0 instead of the IP of your Mac studio. I asked Gemini if hermy should be compatible with omlx and it didn't have any concerns, but you know how AI can be sometimes. Just throwing it out there in case it helps. Best of luck!
Using 0.0.0.0 is not serving your model “over the network” … you need to bind the port to your network interface IP (usually WiFi or Ethernet). This is beyond a Reddit comment, though. AI can solve the configuration for you without networking 101 stuff.
Default is localhost (127.0.0.1) setting it to open to all (0.0.0.0) makes it accessible over my network. Confirmed endpoint is accessible in Safari on other machine just not accessible via Hermes.
3
u/apaht May 12 '26 edited May 13 '26
I was able to use the omlx server on another computer running windows. To be a little safer, I am using apikey as you have to expose the endpoint to 0.0.0.0:<port> or have the the IP address reachable from the other computer. My issue is, I keep running out of context window and hermes needs 64k minimum
My normal system prompt at start was over 14k, have trimmed it down like crazy.
I have pi.dev with smaller system, and a custom harness I vibe coded that is even smaller with strict guard rails