Skip to main content

Semantic Kernel with Ollama returns 404 - The final solution

Today I had to do some small changes in an existing project where we were using Semantic Kernel together with Ollama during debugging and testing. As Ollama exposes an Open AI compatible API, this is possible without any code changes. At least it was...

Here is the code I was using:

When I opened the project I noticed that some of the packages references where outdated so I started by upgrading to the latest version of the Semantic Kernel NuGet packages. However after doing that the requests started to fail with a 404 error message.

Mmm? Didn’t I got the same error before? And indeed I talked about this issue in an earlier post. The issue is still there as I could confirm by looking at the Ollama log messages:

Here is the successful request using the old Semantic Kernel version:

[GIN] 2025/04/24 - 10:05:40 | 200 |    48.466781s |       127.0.0.1 | POST     "/v1/chat/completions"

Here is the failing request using the new(er) Semantic Kernel version:

[GIN] 2025/04/24 - 11:31:35 | 404 |            0s |       127.0.0.1 | POST     "/chat/completions"

To finally get rid of the error I should no longer using the Open AI connector to talk to Ollama but instead use the dedicated Ollama connector. Here is the updated code:

The only disadvantage is that I had to introduce a conditional compilation symbol to load and execute the correct code depending on the environment.

But problem solved!

More information

Semantic Kernel - 404 error when using the v1.20.0 version

Semantic Kernel–Giving the new Ollama connector a try

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more