Duende.IdentityServer.Admin
Duende.IdentityServer.Admin copied to clipboard
skoruba
Unable to start admin
Hello, i cannot able to start Admin proj.
Swagger and sts works flawless but when start Admin in iis express this is result.
What am I doing wrong?
Thank you
Please check the ports and processes that are running on them. Most likely the admin project tries to find the sts on a port that is not listening (you can't just start admin alone, it needs the sts)
Please check the ports and processes that are running on them. Most likely the admin project tries to find the sts on a port that is not listening (you can't just start admin alone, it needs the sts)
indicating admin in the subdomain, i typed "admn" instead admin and it didn't wrong. Anyway Thank you for support.
I have the same issue, but with deployed in the Azure project. Locally everything works fine, but when I deployed sts and admin projects to Azure, I started to receive such kind of error. In addition, I have this issue not only with the admin project. For other Clients connected to the identity server, I'm getting access tokens, but through validating this token in my .net core project, I'm getting this issue. Might it be connected with token singing or whatever? I use the Azure web app on Linux.
I found a solution for my case. The reason was VPN restrictions, which blocked access from the admin to the STS project. So I just added IPs addresses to the whitelist and it begin working. So, if you encountered this problem, firstly check access between apps.
@Diponchik can you elaborate how you fixed the VPN restrictions? Did you deploy the apps inside K8S or simple Azure App Services? I am using Azure K8S with Docker deployed containers and I am facing the same issue with sts service not being reachable from admin service.
@apetrut I had a service plan with a few service apps on it. But for the admin APP, I added a few restrictions in the network configuration, to make it work under VPN only. Therefore IS app couldn't get access to the Admin app. So I added a couple of IPs to the white list and resolved the issue.