Magento HTP 500 Error - Githubissues

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

http://www.magento.com

Open Software License 3.0

11.47k stars 9.28k forks source link

Magento HTP 500 Error #36586

Closed BUNIT1 closed 1 year ago

BUNIT1 commented 1 year ago

Preconditions and environment

Magento ver. 2.3.5-p2

Magento/Backstage is having issues with allowing customers to log into their accounts. Customers are receiving password reset emails, but are unsuccessful with signing in. Clear browser data cookies and history. Also, if you try to go through the process of creating a new order in Magento, it loads up to the HTP 500 Error.
Experience has been replicated by 6 other agents and two customers

Steps to reproduce

Click on Orders
Create an order
Website store order
Add product
Fill out customer information
Submit order
Land on HTP 500 error

Expected result

Hoping to be able to place orders without getting that error messages and customers will be able to sign back in.

Actual result

Can go through the steps of creating order, but get an HTP 500 error screen when trying to submit the order.

Additional information

No response

Release note

No response

Triage and priority

[X] 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[bot] commented 1 year ago

Hi @BUNIT1. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

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.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

m2-assistant[bot] commented 1 year ago

Hi @engcom-Bravo. 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: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

engcom-Bravo commented 1 year ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 1 year ago

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 1 year ago

Hi @engcom-Bravo, here is your Magento Instance: https://5bda34c900a707ea3b39f0a3dcb185c8.instances.magento-community.engineering Admin access: https://5bda34c900a707ea3b39f0a3dcb185c8.instances.magento-community.engineering/admin_b12e Login: 86ac0d68 Password: 8ab386dfa187

engcom-Bravo commented 1 year ago

Hi @BUNIT1,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

1.Click on Orders 2.Create an order 3.Website store order 4.Add product 5.Fill out customer information 6.Submit order

We are able to place the order without any error.

Kindly recheck the behavior on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

BUNIT1 commented 1 year ago

Screen Recording 2022-12-09 at 8.27.20 AM.mov https://drive.google.com/file/d/1M81Ea0DAfgMlJgY-CmLSk1U5C3DlU5OF/view?usp=drive_web Hey, I unfortunately am still experiencing this same issue. Uploading recording for reference:

Baylie Nixon // Team Lead, OpCX, Seeds

C: +1.801.580.0016 // E: @.***

On Fri, Dec 9, 2022 at 3:26 AM Venkata Kumar Kuntumalla < @.***> wrote:

Hi @BUNIT1 https://github.com/BUNIT1,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

1.Click on Orders 2.Create an order 3.Website store order 4.Add product 5.Fill out customer information 6.Submit order

We are able to place the order without any error.

[image: Screenshot 2022-12-09 at 3 53 52 PM] https://user-images.githubusercontent.com/51680745/206681060-0f23a4bc-6756-4331-b82d-e2f814f6fadb.png

Kindly recheck the behavior on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

— Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/36586#issuecomment-1344125528, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4UN45FGXAAVXRBZVU62ARLWMMCMXANCNFSM6AAAAAASYJN56Q . You are receiving this because you were mentioned.Message ID: @.***>

engcom-Bravo commented 1 year ago

Hi @BUNIT1,

Thanks for your Update.

We are not able to see the your reference video.

Kindly recheck the issue on Magento 2.4-develop instance and check if any 3rd party extensions / modules enabled is causing this issue.

Thanks.

engcom-Bravo commented 1 year ago

Hi @BUNIT1,

We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.