Error in Magento 2.4.4 After Installed on Windows 10

[marcelovillalta0]

Preconditions (*)
Magento 2.4.4
Php 8.1
Local Server XAMPP

Steps to reproduce (*)
Download & install Magento 2.4.4

Information (*)
When I want to enter the page for the first time, I get the 404 error.

After trying some solutions provided by different internet forums I found this error:

Error: Undefined constant "Magento\Framework\Encryption\Adapter\SODIUM_CRYPTO_AEAD_CHACHA20POLY1305_IETF_NPUBBYTES" in C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\Encryption\Adapter\SodiumChachaIetf.php:40 Stack trace: #0 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\Encryption\Encryptor.php(399): Magento\Framework\Encryption\Adapter\SodiumChachaIetf->encrypt('a:3:{s:7:"defau...') #1 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-config\App\Config\Type\System.php(339): Magento\Framework\Encryption\Encryptor->encryptWithFastestAvailableAlgorithm('a:3:{s:7:"defau...') #2 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\Cache\LockGuardedCacheLoader.php(137): Magento\Config\App\Config\Type\System->cacheData(Array) #3 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-config\App\Config\Type\System.php(281): Magento\Framework\Cache\LockGuardedCacheLoader->lockedLoadData('SYSTEM_CONFIG', Object(Closure), Object(Closure), Object(Closure)) #4 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-config\App\Config\Type\System.php(207): Magento\Config\App\Config\Type\System->loadDefaultScopeData('default') #5 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-config\App\Config\Type\System.php(181): Magento\Config\App\Config\Type\System->getWithParts('default/admin/u...') #6 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Config.php(132): Magento\Config\App\Config\Type\System->get('default/admin/u...') #7 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-backend\App\Config.php(51): Magento\Framework\App\Config->get('system', 'default/admin/u...') #8 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-backend\App\Area\FrontNameResolver.php(109): Magento\Backend\App\Config->getValue('admin/url/use_c...') #9 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-backend\Helper\Data.php(209): Magento\Backend\App\Area\FrontNameResolver->getFrontName(false) #10 C:\xampp_v1\htdocs\mitienda\vendor\magento\module-backend\App\Request\PathInfoProcessor.php(50): Magento\Backend\Helper\Data->getAreaFrontName() #11 C:\xampp_v1\htdocs\mitienda\generated\code\Magento\Backend\App\Request\PathInfoProcessor\Proxy.php(95): Magento\Backend\App\Request\PathInfoProcessor->process(Object(Magento\Framework\App\Request\Http), '/') #12 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Request\Http.php(148): Magento\Backend\App\Request\PathInfoProcessor\Proxy->process(Object(Magento\Framework\App\Request\Http), '/') #13 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Request\Http.php(163): Magento\Framework\App\Request\Http->getOriginalPathInfo() #14 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Request\Http.php(213): Magento\Framework\App\Request\Http->getPathInfo() #15 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Http.php(111): Magento\Framework\App\Request\Http->getFrontName() #16 C:\xampp_v1\htdocs\mitienda\generated\code\Magento\Framework\App\Http\Interceptor.php(23): Magento\Framework\App\Http->launch() #17 C:\xampp_v1\htdocs\mitienda\vendor\magento\framework\App\Bootstrap.php(264): Magento\Framework\App\Http\Interceptor->launch() #18 C:\xampp_v1\htdocs\mitienda\pub\index.php(30): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http\Interceptor)) #19 {main}

Someone managed to solve this problem, it should be noted that I have tried the old versions of magento and they work correctly for me.

• Severity: S0 - Affects critical data or functionality and leaves users with no 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 @marcelovillalta0. 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.

⚠️ 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.

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

[gwharton]

Do you have the sodium module loaded and have the relevant sodium dll in your php folder?

If you do a phpinfo(); is there a section for sodium. That will tell you whether the module is loaded and the dll found.

[gwharton]

#35419 ???? Possible dup

[nshekhada]

This works for me works on Windows

Add "extension=sodium" to php.ini (no quotes)
Copy php/libsodium.dll to apache/bin/
Restart Apache

[m2-assistant]

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

Hi @marcelovillalta0
As suggested in above-comment, have to tried with settings updated? Is it working now?
If you haven't tried yet, please give a try.

If you have tried and still getting an issue, kindly help us with all the step by step commands and settings you are following up during the installation. It will help us to reproduce and then to confirm the issue.

Thanks in advance!

Hi @gwharton & @nshekhada Thanks for your contribution & collaboration over here :)

[gwharton]

@marcelovillalta0

To test whether sodium is working under PHP create a phpinfo.php file in your pub folder with contents

<?php
phpinfo();

Browse to that file in your browser and check the php configuration contains the following section.

[Finbayern]

@marcelovillalta0

To test whether sodium is working under PHP create a phpinfo.php file in your pub folder with contents

<?php
phpinfo();

Browse to that file in your browser and check the php configuration contains the following section.

I have the same issue as the OP and I suppose this is a dup of #35419 as you wrote above.
I have the sodium installed and I see the exact same section as in your screenshot when I run the phpinfo, so sodium should be ok.
This error only happens with php 8.1 and switching back to php 7.4. fixes the issues, but obviously this is not the long term solution.

Running CentOS v7.9.2009 with MariaDB 10.5 & PHP 7.4/8.0/8.1 .

[Finbayern]

Correction!
Phpinfo showed that libsodium was installed for php 8.0 and 7.4, but for 8.1 it was not.
EA4 showed that the extension was installed for 8.1 too, thus it was clear that something was broken in the installation.
Therefore I removed it and re-installed it, now it shows up in the phpinfo as well.

This fixed the issue, so the culprit was the missing/broken installation of libsodium.

[m2-assistant]

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

[m2-assistant]

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: 👇

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

Thanks for your contribution @gwharton @Finbayern.

@marcelovillalta0 Kindly go through with this #35474 (comment) and please let us know if you are still facing an issues.

Thanks.

[engcom-Bravo]

Hi @marcelovillalta0,

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.