-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
bin/mftf throws Faild to connect
error
#1290
Comments
Hello @pradeepkanaka! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to solve this issue. I found a similar open issue where a suggested solution involves configuring extra_hosts: &appextrahosts
- "magento.test:172.17.0.1" Make sure to uncomment all Common causes for connectivity issues to To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Getting below error when running Connecting to Selenium Server ... [OK] Successful Loading Admin page ... [ERROR] Failed to load page at url: https://magento.test/admin/admin |
To resolve the error you're encountering with
These steps should help ensure that Selenium can access the Magento instance and resolve the error you're facing with To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
These configurations have already been added but still have the same issue. When I catch the exception that we are getting |
The error message
If these steps do not resolve the issue, consider checking the logs for more detailed error messages that might provide additional insights. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
What could be the reason for this issue?
I can browse the URL https://magento.test/
The text was updated successfully, but these errors were encountered: