# Reindex from remote source doesn't work with either API key or user/PW? **URL:** \ **Category:** Elastic Search\ **Created:** [October 22, 2026, 11:52pm UTC](https://discuss.elastic.co/t/reindex-from-remote-source-doesnt-work-with-either-api-key-or-user-pw/391123 "2026-10-22T23:52:16Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 24, 2026, 1:01am UTC](https://discuss.elastic.co/t/reindex-from-remote-source-doesnt-work-with-either-api-key-or-user-pw/391123/6 "2026-10-24T01:01:50Z")
Hi @rik Perhaps If you showed the entire `curl -v` command and output I might be able to help. It should show what you're sending and what available SAN in IP are available to be matched. that snippet is not really helpful. You mentioned containers if you showed a docker compose we might be able to help. We're are trying to help solve this and you're giving tiniest slivers of information. More information is the quicker way to solution than feeling around the elephant... I understand the trade-offs of security and stuff like that If you want to anonymize things you can do that just be consistent. To generate new certs perhaps look at this .. > [@Regenerate the SSL Certificate that was auto-generated on setup of ElasticSearch](https://discuss.elastic.co/t/regenerate-the-ssl-certificate-that-was-auto-generated-on-setup-of-elasticsearch/377216/7): > > Hi @Yaser_Amini Welcome to the community 1st place to start is the official documentation And here are details on using the cert util I like using the Silent Mode with instances.yml to create new certs with the correct SANs / IPs etc --- _[View the full topic](https://discuss.elastic.co/t/reindex-from-remote-source-doesnt-work-with-either-api-key-or-user-pw/391123)._