-
Hello, before opening an Issue, I first wanted to ask here if i did any obvious mistake. I have an ocelot.json and and ocelot.consul.json in my project directory. Both are applied to my App Configuration.
When trying to connect to one of the downstream services, the connection to Consul is refused, stating the wrong port in the message:
If I revert back to 23.2, the issue is gone. Was there any major change to the configuration files? Or does anyone have a hint? Any help would be greatly appreciated! Nico |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hello Nicolas, It seems your
Based on the 🆗 I'll provide further recommendations once I have your feedback. |
Beta Was this translation helpful? Give feedback.
-
OK... Show us complete solution please:
|
Beta Was this translation helpful? Give feedback.
As a team, we have the right to decline zipped files, so users should upload their work as a repository on GitHub. It's acceptable this time since you're new to Ocelot, but please ensure to upload as a repository in the future.
After a quick review, it appears to be a custom solution with additional libraries. As a team, we do not provide recommendations for solutions that are not based solely on Ocelot extensions.
Properties of the custom solution include:
using MMLib.SwaggerForOcelot.DependencyInjection;
which is an unofficial third-party library, not a native Ocelot one. Its impact on overall stability is unclear. The reference<PackageReference Include="MMLib.Swag…