Magento 2.4.7 Connect to elasticsearch8 and Not see the products on UI.

[Skyfly]

Preconditions and environment

Magento 2.4.7
Elasticsearch 8.11.4

Steps to reproduce

1.Ensure Elasticsearch 8.11.4 is installed
2.Ensure Magento 2.4.7 composer installation works
3. Run bin/magento .... --search-engine=elasticsearch8
4. The connection is successful in the Magento backend configuration

Expected result

Run bin/magento indexer:reindex catalogsearch_fulltext
Successfully completed

Actual result

prompt“No alive nodes. All the 1 nodes seem to be down.”

Additional information

elasticsearch/elasticsearch.yml
The file configuration is shown in the attached figure


The Elasticsearch server listens on ports normally.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Skyfly2021. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[m2-assistant]

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[devchris79]

I am sure that curl command should be reporting that you need authentication, it doesn't look like the username and password is being required.

I would have expected a curl command like below, passing the username and then the curl response asking for the password:

curl -u username 132.123.123.123:9200 -k

Maybe the Elastic search instance doesn't have the credentials configured?

[Skyfly]

I am sure that curl command should be reporting that you need authentication, it doesn't look like the username and password is being required.

I would have expected a curl command like below, passing the username and then the curl response asking for the password:

curl -u username 132.123.123.123:9200 -k

Maybe the Elastic search instance doesn't have the credentials configured?
Because I disabled safe mode on the elasticserver, I can respond without username and verification code.

[Skyfly]

I am sure that curl command should be reporting that you need authentication, it doesn't look like the username and password is being required.

I would have expected a curl command like below, passing the username and then the curl response asking for the password:

curl -u username 132.123.123.123:9200 -k

Maybe the Elastic search instance doesn't have the credentials configured?
After enabling safe mode on the elastic server, it cannot respond without a password.

At the same time, a connection error also occurred in the magento background, as follows:

[devchris79]

This looks like an issue with the Elasticsearch instance.
Try resetting the password

[Skyfly]

This looks like an issue with the Elasticsearch instance. Try resetting the password

It's not a password issue, I can pass cur on the Magento server “curl -k GET 'http://x.x.x.x:9200' -u xxxx: xxxx ” returns data.

[MagenX]

check ELK log if node is not in RED status
must be GREEN

also if your ssl cert properly signed

[Skyfly]

check ELK log if node is not in RED status must be GREEN

also if your ssl cert properly signed

thanks ,I didn't use SSL connection, and then I installed magento 2.4.7 cleanly, which can solve this problem, but there is no way to save the created product, and it has been waiting, and then I can only return to magento 2.4.6-p5.

[susena sravani simhambhatla]

Hi @Skyfly2021

Thanks for reporting and collaboration.

Verified the issue on magento 2.4.7 instance but the issue is not reproducible.

Magento 2.4.7
Elasticsearch 8.11.4

We can run "bin/magento indexer: reindex catalogsearch_fulltext" successfully.

Please refer the attached screenshots.

[Skyfly]

Hi @Skyfly2021

Thanks for reporting and collaboration.

Verified the issue on magento 2.4.7 instance but the issue is not reproducible.

Magento 2.4.7 Elasticsearch 8.11.4

We can run "bin/magento indexer: reindex catalogsearch_fulltext" successfully.

Please refer the attached screenshots.

thanks, After my fresh install, this problem is gone, but when creating the product and saving, it has been in a waiting state, and this problem appeared before from the upgrade of mangento 2.4.6-P5.