Changing admin url from admin not working

[hemendraajmera]

Preconditions (*)

Magento 2.4.4

Steps to reproduce (*)

1. Stores > Settings > Configuration - Advanced - Admin - Custom admin Url set to "yourmagentostore.com/backend/"
2. Custom Admin path set to "backend"
3. Save config
   Issue: UI is broken Unable to login even after clearing cache.
   Note: There is no issue on setting from CLI as per docs

Expected result (*)

1. [Screenshots, logs or description]
2. it should be changed to new one and throw success message.

Actual result (*)

Exception #0 (Exception): Deprecated Functionality: stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/html/magento2/vendor/magento/module-backend/App/Area/FrontNameResolver.php on line 135

---

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 @hemendraajmera. 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

[hemendraajmera]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @hemendraajmera. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @hemendraajmera, here is your Magento Instance: https://4f08166f183fe6b8e8b094cef9312e1e.instances.magento-community.engineering
Admin access: https://4f08166f183fe6b8e8b094cef9312e1e.instances.magento-community.engineering/admin_71fd
Login: 3b62f09b
Password: d4ae11025d45

[hemendraajmera]

issue reproduced on requested instance , after saving it redirected to 404 page

[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.

[engcom-November]

Hi @hemendraajmera ,
Thank you for reporting and collaboration. Unable to reproduce the issue on Magento 2.4-develop version. It seems like your URL is not changed with new value set in admin. (Browsing with same old admin URL as per your Screenshot ). Can you please refer the docs and recheck the issue again on Magento 2.4-develop branch / 2.4.4 version and let us know if you are still facing issues.
Thank you.

[hemendraajmera]

It still open because i tried to updated admin base url from admin panel which not working,after that the admin panel URL not working,
you can try using fresh magento 2.4.4 instance

[hemendraajmera]

@magento give me 2.4.4-develop instance