not discovering ollama

[ageorgios]

I get this although

what am I doing wrong ?

[kevinhermawan]

Hello @ageorgios, the error message you're encountering doesn't seem to be related to connectivity issues with the API. To troubleshoot further, could you please check if you're using a VPN or have any network firewalls that might be interfering with the connection? Sometimes these can create unexpected issues. Additionally, it might help to completely close the Ollamac and then reopen it. This can often resolve temporary glitches. Let me know how it goes!

[ageorgios]

no VPN or network firewalls. restarted.. same problem! cannot understand why

[ageorgios]

I also get 200 on the ollama server! OLLAMA_ORIGINS=* OLLAMA_HOST=0.0.0.0:11434 ollama serve

2023/11/13 21:43:04 images.go:824: total blobs: 155
2023/11/13 21:43:04 images.go:831: total unused blobs removed: 116
2023/11/13 21:43:04 routes.go:696: Listening on [::]:11434 (version 0.1.9)
[GIN] 2023/11/13 - 21:43:08 | 200 |      48.916µs |             ::1 | HEAD     "/"
[GIN] 2023/11/13 - 21:43:08 | 200 |    3.385292ms |             ::1 | GET      "/api/tags"

[ageorgios]

    let response = request.serializingDecodable(OKModelResponse.self, decoder: decoder)

for some reason this returns AFError

[kevinhermawan]

For now, we can ignore nw_socket_handle_socket_event [C1.1.1:2] Socket SO_ERROR 61 warning.

[kevinhermawan]

Does the release version have the same issue?

[ageorgios]

yes I first downloaded the release, then decided to download the project to check why

[ageorgios]

{"models":[{"name":"codellama:34b","modified_at":"2023-11-13T00:42:20+02:00","size":19052049085,"digest":"685be00e1532e01f795e04bc59c67bc292d9b1f80b5136d4fbdebe6830402132"},{"name":"llama2:13b","modified_at":"2023-11-12T14:47:30+02:00","size":7365847104,"digest":"b3f03629d9a68f2660285cd86d786079c38a56a235032557ab9ba170786f0cf3"},{"name":"llama2:70b","modified_at":"2023-11-12T14:12:18+02:00","size":38872261740,"digest":"c3a7af098300caa39b24eb403f229a3200bb23629fdfb17fef4484d8617ae29e"},{"name":"llama2-uncensored:7b-chat-fp16","modified_at":"2023-11-12T23:48:03+02:00","size":13478117144,"digest":"b29ffe78e25027708a698a3e24e92d0679e84908c4447e6b13483b5acb458366"},{"name":"llama2-uncensored:latest","modified_at":"2023-11-12T12:52:46+02:00","size":3825819449,"digest":"44040b9222331f7eacd27ec9254e42de585af28d2c5d1211cdaeb3ffa361fe3f"},{"name":"mistral:7b-text-fp16","modified_at":"2023-11-13T20:46:32.965926724+02:00","size":14484731688,"digest":"1771c1be9e23c5addbdc55f052a17503675310f35ac2a3bafffc25b1016bcba7"},{"name":"mistral:latest","modified_at":"2023-11-12T15:40:41+02:00","size":4108916866,"digest":"d364aa8d131ef7abfc1275db682d281a307d9451fc00f96abe154d0059b0be49"},{"name":"nous-hermes:13b","modified_at":"2023-11-13T08:28:13+02:00","size":7366062640,"digest":"e6251854aa4c0c838d30c86d0cfd1b86f8c41011f35299122be3f3c87eff32bb"},{"name":"nous-hermes:13b-llama2-fp16","modified_at":"2023-11-12T19:32:39+02:00","size":26033960207,"digest":"0e2f44eb07739558f2636fde3c67157b468c526f7016c5b6b28919d48427cf1e"},{"name":"vicuna:33b-q5_0","modified_at":"2023-11-13T21:32:04.048816189+02:00","size":22395361358,"digest":"4a6fa67158d812d9f4cc3cf1be76484351c3e1f1b7e42d995a402d4d7f1884ca"},{"name":"vicuna:7b","modified_at":"2023-11-13T08:13:47+02:00","size":3825807726,"digest":"370739dc897bba0188d390bb7659e48d926cacc320875136d0115228023b1590"}]}

[kevinhermawan]

I can't produce this issue. However, I noticed that compared to mine, there's a different modified_at date format in use here.

[kevinhermawan]

Thanks for providing the JSON response, I will attempt to mock the response using that JSON and will inform you of the results. 😃

[ageorgios]

Thanks really appreciate it

[kevinhermawan]

Hi @ageorgios, a fix has been implemented in this latest release. Could you please review and test it to confirm if it's working as expected?

[ageorgios]

Working as expected! thank you very much!

[kevinhermawan]

Thanks for the confirmation @ageorgios! I will close this issue.