Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DomainTenantResolveContributor does not resolve domain
See original GitHub issue- Your Abp package version. 8.0
- Your base framework: .Net Core.
- Activated MultiTenancy and specified
DomainFormat. - Application deployed via DigitalOcean as ‘App’, separated for Frontend and Backend
- Everything released, everything works except for domain resolver, my tenantId is always null whatever domain I pass.
mytenant.mydomain.com - frontend api.mydomain.com - backend
however inside DomainTenantResolveContributor from Abp.AspNetCore.MultiTenancy (as below picture related), Host is being taken and then resolved (as host), instead of mytenant.mydomain.com I receive api.mydomain.com. Am I missing some header from frontendside/backendside in configuration (like X-Forwarded-Host)?
That makes me think that most probably I need to create my own TenantResolveContributor that is getting origin instead of Host.Host. Do you think we have a bug inside this TenantResolver or it is my misconfiguration?
Localhost screenshot, to prove that Host in my situation is backend host, instead of frontend host.
Issue Analytics
- State:
- Created 8 months ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello, this is how I managed to resolve this issue:
( after two days of debugging 😃 )
Cheers