Magento 2.4.2 does not allow login Error 404 Page Login

[adorobeleza]

Hello friends, after upgrading from magento 2.3.6 to 2.4.2 I can't log in anymore, and as you can see there are errors in the email.php file

Website: https://www.adorobeleza.com.br/customer/account/login/

PHP 7.4.20 (cli) (built: Jun 4 2021 21:24:37) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.20, Copyright (c), by Zend Technologies

nginx.conf.sample is in the /pub folder

https://pastebin.com/JVhEjz1t

Preconditions ()
Steps to reproduce ()
Expected result (*)
[Screenshots, logs or description]
2.error 404

Actual result (*)
[Screenshots, logs or description]

Error email error 404

<script type="text/x-magento-init">{"body":{"pageCache":{"url":"https:\/\/www.website.com.br\/page_cache\/block\/render\/referer\/aHR0cHM6Ly93d3cuYWRvcm9iZWxlemEuY29tLmJyL3NhbGVzL29yZGVyL2hpc3Rvcnkv\/","handles":["default","customer_account_login"],"originalRequest":{"route":"customer","controller":"account","action":"login","uri":"\/customer\/account\/login\/referer\/aHR0cHM6Ly93d3cuYWRvcm9iZWxlemEuY29tLmJyL3NhbGVzL29yZGVyL2hpc3Rvcnkv\/"},"versionCookieName":"private_content_version"}}}</script>

email.php file

https://pastebin.com/FFqHHYSg

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

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 @adorobeleza. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[mrtuvn]

Seem problem not related with magento codebase! Have you double check from your customise code ? I don't found in the magento code around with isEnabled('google') like your console log error screenshot show
Also It's worth to mentioning, you should setup your magento folder root to pub folder. Ex: magentorootfolder/pub <= is your new root instead previously config (start from 2.4.x version)

[m2-assistant]

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

  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-Golf]

@adorobeleza This is not an issue due to Magento 2.4.2. It seems something wrong with your Codebase. I would suggest you to check error log as well. Are you getting email.php related console error on Login Screen or Login Action Screen?

I opened the link you shared for Login Screen, and have not found email.php related Console error.

Please update, if the Issue still persist.

[adorobeleza]

Hello friends, I understand that this cannot be a problem with Magento, but in version 2.3.6 it was working normally, What changed in this version to make this error occur?

@engcom-Golf You need to enter some email to get the popup with a 404 error.

Note that in this version magento has adopted the docroot this may be interfering? Regarding the Google error, do you know what it can be?

[adorobeleza]

Note: After updating we need to update the nginx file and remove the TAG ttl=3600 from the default.xml file to be able to view the menu .

[mrtuvn]

Thanks you for the further info. Update may come with some risky. If you have updated and dont want revert. It's time for migrate old code to work with newer code base. Start with recheck function popup. If customised code not have good write quality may cause some issue when update later.
In case you need any help highly recommeded you can chat in open magento slack channel for support or post issue in stackexchange magento

[engcom-November]

Verified the issue after upgrading from Magento 2.3.6 to 2.4.2 and Admin login and Front-end login both are working fine. We are closing this issue as there has been no latest update on the same. @adorobeleza , kindly reopen/create new issue if you are still facing issues and provide missing configuration details if any.
Thank you.