Can't Access Component Manager

[astorm]

The component manager page returns a 404 when Magento is installed using the more secure /path/to/magento/pub (vs. /path/to/magento) as the system web root.

1. Install Magento
2. Configure Web Root to point to Magento's pub folder
3. Navigate in admin to System -> Web Setup Wizard

Expected result

1. Web Setup Wizard page displays

Actual result

1. Standard Magento 404 (Whoops, our bad...) page displays

[astorm]

/cc @tanya-soroka

[piotrekkaminski]

and cc @alankent as this is the MEC install model

[tanya-soroka]

Hello @astorm . Thanks for reporting this issue. I have create a ticket for our team to review it: MAGETWO-51929.

[piotrekkaminski]

Based on the latest changes so far it won't be possible to access web wizard when located in pub unless you set up separate domain to access the top level. It should be fixed better in a future version.

[piotrekkaminski]

Internal issue for proper fix MAGETWO-52799

[KrystynaKabannyk]

Hello @astorm, this issue has been fixed in the 2.1.0 Release, that's why I'm closing it. If you any questions or additional information regarding the issue feel free to reopen it or create a new one.

[astorm]

Thank you @tanya-soroka, confirmed fix, and much appreciated!

[piotrekkaminski]

@astorm @KrystynaKabannyk @tanya-soroka @xcomSteveJohnson i'm reopening this issue as it was not fixed. The only change is that there is no longer link to setup wizard in menu if Magento is installed in /pub but proper solution is scheduled for next version and tracked as MAGETWO-52799. It turned out it is harder to fix than expected and it was not merged into 2.1.

[CalebWC]

Hello, we are a Magento partner with multiple clients moving to Magento 2, and this is impacting the installation of our plugin. What is the ETA for this fix/version, and is there a workaround in the meantime besides manual installation?

[ghost]

@CalebWC To get the Component Manager to work, try configuring your Virtual Host to use the Magento root directory instead of pub. Otherwise, I'm sorry for trouble.

[alexgran]

Hi, you closed 5247 as a duplicate of this one. But I do have web root set to magento root, and still I get the odd unlogin message. And a warning that my webserver allows acces to files which it shouldn't, obviously.
I can set it to /pub, than I get a page not found when trying to access web setup wizzard

[alexgran]

Update: Chrome seems to be the issue, firefox works

[johnhughes1984]

Same issue here, clean install of CE 2.1 using composer and CLI install.

Switching web root to Magento root worked, thanks!

Look forward to the 'full fix' as don't want to use this workaround in production.

[magenx]

Magento 2.1.1 doc root /pub/
Web Setup Wizard menu still missing, but when you type http://www.shop.com/admin_xxxx/admin/backendapp/redirect/app/setup/
redirects tohttp://www.shop.com/setup/#/home and then all works as expected...

i do even have php-fpm in chroot and nginx has two doc roots defined, still no menu, but manual redirect works...

[stamster]

No comment for this issue.

What in the world could happen to make such a failure in a release, to disable menu item?!
On the other hand everything works just fine if you use 'secret passage' URL redirect provided here by @magenx ! So, it's not a core issue, but only a God damn link / frontend problem.

@magenx thanks a lot for this hint, you saved not a day but a month! 👍

Contrary to this, @ Magento core team who let this just happen w/o resolving it ASAP I just don't have words to say but that it is not only unacceptable but lame.

[astorm]

Just a note for people coming along after the fact -- per this comment, the underlying issue remains in the latest versions of Magento. This specific issue was closed when the original poster decided Magento wasn't going to address it.

[kevinjavitz]

yes this should really be re-opened, it is confusing as the issue still exists in 2.1.2 and it is a big issue as without the web installer you can only install modules/components with composer

[joebordo]

I just Tried it in google chrome "incognito modus" and it worked. magento 2.1.2 clean install. Hope it helps.

[fwolfst]

Using the nginx.conf.sample from magento2 (.1.5) directory I managed to access http:////admin/backendapp/redirect/app/setup/ which redirected me to http:///setup/#/home .

There I was able to define the marketplace public and private keys to be presented a spinning wheel of death ("Please Wait...") - or is it normal that this takes > 20 minutes? Pretty dissappointing, was so happy to finally be presented with the Web Setup Tool thing ....
Setup is ubuntu 14.04 with backported php7 running nginx.

[Radiergummi]

@fwolfst I also tried to just access it by URL, though I never even saw the marketplace key selection screen but the text Welcome to Magento Admin, your online store headquarters. To use the Magento setup wizard sign into your Admin account and navigate to System => Tools => Web Setup Wizard

[fwolfst]

make sure you are logged in as admin (or similar) in a different tab in your browser session, then visit http://<shopurl>/<adminurl>/admin/backendapp/redirect/app/setup/ .

…

On 19.04.2017 18:35, Mo wrote: @fwolfst <https://github.com/fwolfst> I also tried to just access it by URL, though I never even saw the marketplace key selection screen but the text /Welcome to Magento Admin, your online store headquarters. To use the Magento setup wizard sign into your Admin account and navigate to System => Tools => Web Setup Wizard/ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANY7cpW8xNBHRzZ5y_Jv-SxWvatOuthks5rxjfSgaJpZM4IHguY>.

[rgjoyce]

Yes, this is the problem we have been reporting. It has been in Magento since version 2.0.2 and is still there. It seems to be related to the /var folder contents. But even so, the php diagnostics on the next step are broken too, so even if they finally get this fixed, there will be further problems. Version 2 of magento is totally useless so far.

[stamster]

@rgjoyce I completely understand your point! 👍
And since you've compared Joomla (which has always been on the dark site) and Magento2, oh Boy - now it looks like Joomla is for a magnitude more professional than M2.
It's been almost two years since initial release, so I guess M2 is a dead end if the core issues are still present. 👎 M(2) is completely overrated.

[justanewbie00]

Using 2.1.6 and the issue is still unresolved.

[Radiergummi]

@alyhugo with all due respect for the Magento team, I've given up any hope for a timely fix. Of you are like everyone else and have projects due, move on and try to solve it by yourself. This may be unacceptable for an enterprise software product, but I don't have time to wait another year with a project due next month.

[drpit]

Hello,
I tried to use both /pub and non pub directory as system root but still cannot find web setup wizard.
I have switched back yo apache in order to use it.
Any suggestions?

[korostii]

@drpit, well, as a workaround I could suggest doing installs and updates via composer and not use the web setup wizard, at all. That's probably the most resilient way to do it right now.
Please also keep in mind that having web setup wizard accessible in production is a bad choice from security standpoint.

Other than that, you'll probably need to wait for some updated from Magento representatives.

[pmsteil]

By the way, a workaround for this is a symlink in pub/

ln -s ../setup/ setup

Depending on your Nginx configuration.

As I am having this issue on 2.3 in 2019 I am trying to find the easiest workaround.

The above suggestion... I have tried running it from my
/var/www/webroot
/var/www/webroot/setup
/var/www/webroot/pub
/var/www/webroot/pub/setup

folders and it doesn't change anything. I still get "Access Denied" when I try and got to /setup in my browser.

What folder do I run this from and do I need to clear any caches or any other CLI commands after I do the symlink?

thanks

[dharake]

Hey guys,

I solved this mystery, sorry you are still suffering with this. Since Magento 2.0 I've had this issue and finally in 2.3 found the answer a few days ago on https://magento.stackexchange.com/questions/222345/magento-2-2-2-web-setup-wizard-not-visible-in-backend.

Before I give the solution, warning, do not be too excited. I tried using the Component manager and it gave me so many problems. I have it now, and won't use it because it will disappoint you and invariably crash.

That said, solution:

1. Edit the file:
   magento/vendor/magento/module-backend/Model/Setup/MenuBuilder.php

2. locate @ line 36 :

• Removes 'Web Setup Wizard' from the menu if doc root is pub and no setup url variable is specified.

3. Comment out the whole function like so:

/**
* Removes 'Web Setup Wizard' from the menu if doc root is pub and no setup url variable is specified.
*
* @param Builder $subject
* @param Menu $menu
* @return Menu
* @SuppressWarnings(PHPMD.UnusedFormalParameter)
* @SInCE 100.1.0
/
/* public function afterGetResult(Builder $subject, Menu $menu)
{
if ($this->docRootLocator->isPub()) {
$menu->remove('Magento_Backend::setup_wizard');
}
return $menu;
}
*/

4. php bin/magento setup:di:compile

5. php bin/magento cache:flush

I tried installing modules, enabling/disabling modules and it was all garbage. Only good to see what modules are enabled/disabled in a visual format.

Hope that helps.

[pmsteil]

Hey guys,

I solved this mystery, sorry you are still suffering with this. Since Magento 2.0 I've had this issue and finally in 2.3 found the answer a few days ago on https://magento.stackexchange.com/questions/222345/magento-2-2-2-web-setup-wizard-not-visible-in-backend.

Before I give the solution, warning, do not be too excited. I tried using the Component manager and it gave me so many problems. I have it now, and won't use it because it will disappoint you and invariably crash.

That said, solution:

1. Edit the file:
   magento/vendor/magento/module-backend/Model/Setup/MenuBuilder.php
2. locate @ line 36 :

• Removes 'Web Setup Wizard' from the menu if doc root is pub and no setup url variable is specified.

1. Comment out the whole function like so:

/**

• Removes 'Web Setup Wizard' from the menu if doc root is pub and no setup url variable is specified.
• @param Builder $subject
• @param Menu $menu
• @return Menu
• @SuppressWarnings(PHPMD.UnusedFormalParameter)
• @SInCE 100.1.0
  / /* public function afterGetResult(Builder $subject, Menu $menu)
  {
  if ($this->docRootLocator->isPub()) {
  $menu->remove('Magento_Backend::setup_wizard');
  }
  return $menu;
  }
  */

1. php bin/magento setup:di:compile
2. php bin/magento cache:flush

I tried installing modules, enabling/disabling modules and it was all garbage. Only good to see what modules are enabled/disabled in a visual format.

Hope that helps.

Thanks... I gave up and found command line ways to do what I wanted to do with /setup...

[gladroger]

I have applied this fix and it works, thanks!

However when trying to install extensions I get composer status
You have changes in the following dependencies: /home/user/public_html/vendor/magento/module-backend

How do I bypass this in able to use composer or web setup?

[mateuszrusiecki]

Hello! It's 2020 here and this issue still exists(ver. 2.3.4)! are you serious guys? o_O

[magenx]

it is working, if you have webroot in /pub/
then you need to have separate root dir for /setup/

[mateuszrusiecki]

uh silly me. I just used nginx.conf.sample from magento and it worked

[themew]

Not working in OpenLiteSpeed with webroot in /pub/ Still getting 404 with Magento 2.3.4

[dvershinin]

The big question is not this bug. The big question is Magento 2 Q/A, speed of fixing things, inadequate closing of tickets then further neglect.

@KrystynaKabannyk was the issue really fixed when you closed it? Following all the scrolling thereafter it's obvious that it at least returned very soon, or likely never been truly fixed. Based on the volume of complaints, it has to be reopened.

It takes a second to realize how people are filing issues here and in other closed tickets:
Typed a problem on Google search, landed up here, commented here. But the QA team is not looking at tickets which are closed or simply putting them to the lowest priority despite them actually being important and trivial to fix, like this one.

Something must change with the Magento team's workflow.
No premature closing of tickets, please.
At least some monitoring set to the volume of complaints on closed tickets, please.

[dharake]

Guys the component manager, see entire web setup wizard and GUI module control have been deprecated (its somewhere in release notes of 2.4.1 i think). You need to use ssh here on out, to the best of my knowledge.

[dharake]

Your Magento is shit.
It simply doesn't work after clean installation with Docker.
2.4.2
Can't visit any page of web app =)

I gave up trying to use docker for magento

[dharake]

The big question is not this bug. The big question is Magento 2 Q/A, speed of fixing things, inadequate closing of tickets then further neglect.

@KrystynaKabannyk was the issue really fixed when you closed it? Following all the scrolling thereafter it's obvious that it at least returned very soon, or likely never been truly fixed. Based on the volume of complaints, it has to be reopened.

It takes a second to realize how people are filing issues here and in other closed tickets:
Typed a problem on Google search, landed up here, commented here. But the QA team is not looking at tickets which are closed or simply putting them to the lowest priority despite them actually being important and trivial to fix, like this one.

Something must change with the Magento team's workflow.
No premature closing of tickets, please.
At least some monitoring set to the volume of complaints on closed tickets, please.

Hopefully Adobe help steer them in a better direction 🤞

[mateuszrusiecki]

Hopefully Adobe help steer them in a better direction

@dharake no they won't. It just can not be done :)

[liquidia]

Magento system is flawed ... its too complex and confused UX make it more difficult ... Magento developer should learn from Wordpress how to make easy to install and use.. i was hoping they would change the direction with magento 2 but they moved to totally different direction and making it harder and harder ..