Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with SSH Authentication for DataFeedWatch Connector Installation #39662

Closed
1 of 5 tasks
irenepakhomkina opened this issue Feb 26, 2025 · 8 comments
Closed
1 of 5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@irenepakhomkina
Copy link

Summary

Hi!
We're working on integrating DataFeedWatch with Magento for data fetching, following this guide: Adding Magento 2 to DataFeedWatch
https://help.datafeedwatch.com/article/783v6ihcks-adding-magento-2

At Step 9, we need to install the DataFeedWatch Connector via SSH. However, when attempting to log into the Magento server via SSH, the connection is established, but authentication fails.

Our question:
Could you confirm whether the credentials used for logging into the Magento Admin Dashboard are the same as those required for SSH access? It seems like the SSH account required is different from the admin account, and while the server connection is being made, our user credentials (and those provided to us) are being rejected.
Would you be able to clarify the correct login method or provide guidance on resolving this authentication issue?

Thanks in advance for your help!

Examples

Image

Proposed solution

We suspect that the SSH login credentials might be different from the Magento Admin credentials. If this is the case, could you clarify where we can find or reset the correct SSH credentials? Additionally, if there are any specific SSH access requirements (e.g., public key authentication, user role restrictions), please let us know.

Release note

Issue reported regarding SSH authentication failure when attempting to install the DataFeedWatch Connector for Magento. The user is unable to log in via SSH despite a successful server connection.

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”.
@irenepakhomkina irenepakhomkina added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Feb 26, 2025
Copy link

m2-assistant bot commented Feb 26, 2025

Hi @irenepakhomkina. 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.


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.

@irenepakhomkina
Copy link
Author

Image

@YuriyYavorskiy
Copy link

@magento add to contributors team

Copy link

m2-assistant bot commented Feb 26, 2025

Hi @YuriyYavorskiy! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Feb 27, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Feb 27, 2025
@engcom-Hotel engcom-Hotel self-assigned this Mar 3, 2025
Copy link

m2-assistant bot commented Mar 3, 2025

Hi @engcom-Hotel. 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- 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.

@engcom-Hotel
Copy link
Contributor

Hello @irenepakhomkina,

Thanks for the report and collaboration!

We are using this platform to report the bug related to the core libraries of the Magento. For the above issue I think you need to connect with the cloud support team.

Please let us know if we missed anything in understanding the issue.

Thanks

@engcom-Hotel engcom-Hotel moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Mar 3, 2025
@engcom-Hotel engcom-Hotel added the Issue: needs update Additional information is require, waiting for response label Mar 3, 2025
@bhennesAdv
Copy link

@irenepakhomkina I think I can help you on this :

First point is : This is the repository of magento 2 official code, when encountering an issue with https://www.datafeedwatch.com/ , you might need to contact directly their support team which might help you better.

Second point is : To answer your question about SSH and Magento Credentials, they probably have nothing in common (except the fact that there is a user and a password involved).

  • Magento credentials are stored in Magento database to connect the Magento application installed on the server.
  • SSH credentials are probably stored on the Operating system directly to connect a new SSH terminal on the server (Like opening a session on your Windows computer)

SSH credentials are probably managed by your hosting company (Which according to the hostname you gave, could be LiquidWeb). You should contact them to get more information about your ssh access credentials.

I hope this helps you to understand the difference.
Regards,
Baptiste

@engcom-Hotel I think this issue can be closed.

@engcom-Hotel
Copy link
Contributor

Sure @bhennesAdv closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Development

No branches or pull requests

5 participants