SteeltoeOSS
register instanceid host in iis inprocess model
Describe the bug
A clear and concise description of the bug.
when my asp.net core 3.1 app host in IIS, the url console is 127.0.0.1，so，when i have Multiple instances，the instances name will be the same,such as 127.0.0.1:svaname:port，eureka server think they are a single instance.
i print the console in source code：
Since this bug is not assigned yet I want to contribute its fix. Can we discuss?
Hi @ZuraizAhmedShehzad,
You're welcome to take a look at this issue, but I'm not confident it really is a "good first issue" for somebody new to Steeltoe as it could need to relate to other issues like this one or this one and there is the potential complexity with setting up an environment to replicate the issue. Happy to help work through it if you are still up for it after those considerations!
If you would prefer something a little more approachable to get started, please consider this issue with endpoint mappings and know that we would also greatly appreciate some basic validation and potential enhancements of the quick start guides or documentation, such as this issue for service discovery guides
Hi @ZuraizAhmedShehzad,
You're welcome to take a look at this issue, but I'm not confident it really is a "good first issue" for somebody new to Steeltoe as it could need to relate to other issues like this one or this one and there is the potential complexity with setting up an environment to replicate the issue. Happy to help work through it if you are still up for it after those considerations!
If you would prefer something a little more approachable to get started, please consider this issue with endpoint mappings and know that we would also greatly appreciate some basic validation and potential enhancements of the quick start guides or documentation, such as this issue for service discovery guides
Thanks for suggestion Tim. Since I was looking for a good first issue I am looking into the one you have suggested. Thanks !
@akaxb,
Are you still experiencing this issue? Are you able to provide a more complete repro (what are the multiple registrations) so we can better understand the use case? We need to understand how to setup IIS in order to reproduce this so that we can reason about it
Given the original timing on this issue, I am going to assume that this was using Eureka. As such, the solution is to set Eureka:Instance:RegistrationMethod to HostName so that the hostname will be used for the Uri rather than the IP address being a factor at all. I'm closing the issue with the assumption that fixes the problem, if you are still in need of a resolution please open a new issue