1

I recently created a .NET Framework web API and not .NET Core due to reliance on old libraries. Also, we had the requirement to have an API gateway, with this we used ocelot but it keeps on failing during startup with the error below.

Unable to start Ocelot, errors are: When not using service discovery DownstreamHostAndPorts must be set and not empty or Ocelot cannot find your service!

The gateway works if only .NET Core web APIs are configured in the ocelot Routes, but when the .NET Framework API settings are added, it throws this error.

Is there anything specific to .NET Framework APIs that I should do to make this work?

Improve this question
Related questions
0
WebApi 2 + OData v4 complete example
5
Identityserver 4 and Ocelot
2
How set up Ocelot Api Gateway with Azure Active Directory
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.