Hi @MichelZ
I'm not %100 sure but your requests might be blocked by our firewall. Is it possible to share your IP with us so we can check this ? You can share it with info@abp.io.
Also, using a nuget cache for your docker builds might help to solve this problem and speed up your development, see https://stackoverflow.com/questions/60799918/using-nuget-cache-inside-a-docker-build-with-net-core-when-offline.
Thanks, I have sent an e-mail. The BuildKit thing is a good idea and I will look into this, thank you!
Hi
No, it is not. This is for pushing packages - where a 409-Conflict makes absolutely sense. Here, we are not pushing any packages, it's just a package restore.
Any chance that this could be improved? We use a one-db-per-tenant approach as well, and having TenantID columns is just distracting :)
Hi @MichelZ
Yes, the release of 4.4.1 is still in progress, could you try again when the release is completed. We hope to complete it today.
Thanks,
Hi
The problem is not updating to 4.4.1, the problem is that all of my workflow starts to fail with the current version. All nuget restores for 4.4.0 started failing yesterday with the conflict message. This is very disruptive as I'm using docker to build this like every couple of minutes, and docker doesn't cache the packages, so I can't really build anymore.
I am currently getting "Response status code does not indicate success: 409 (Conflict)" when trying to do dotnet restore. It happens from time to time, and my best guess is that it has something to do with when a new release is put up there. As far as I can see 4.4.1 is in the process of being released currently.
I do have the same issue actually, but did not get around investigating it yet, as I'm waiting for something else to be fixed first.
hi
Is the samesite thing also required in the IdentityServer project?
Yes, It should be add in the project that using the IdentityServer.
Thanks, that was it!
When can we expect the next patch release?
I am having the same issue. The samesite thing from the article did not work for me. Is the samesite thing also required in the IdentityServer project?
The reason to want http is for development in Docker, it makes it easier not having to worry about certs
Would you also please consider adding one with Angular and Identity Server separated?
I will try to add that.
Thank you!
I have found what I was doing wrong using that sample application. I was missing this in my Configure on the Identity Server which sets the issuer URL to a static URL instead of using the Tenant-specific URL:
Configure<IdentityServerOptions>(options => { options.IssuerUri = configuration["App:SelfUrl"]; });
I'm not sure if I saw this documented somewhere, or if I just missed it, maybe it can be pointed out and clarified in the documentation. Thanks again & Cheers Michel
