magento2: Can't Access Component Manager

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…

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

unbelievable. I am a Joomla developer and to see this problem go unresolved is astonishing. It has been several versions now. I just installed 2.1.5 and it wend through all the tests and installed perfectly. Well done. It was only when I went to setup a payment plugin that I found the system doesn’t work at all. you get a logged out message when you try top open the Web Setup Wizard. Since this is the only place you can install or setup the modules for Magento, and it’s not accessible, doesn’t that make Magento completely UN-usable? Getting the setup wizard fixed and working should be the top priority of the dev team as it’s the cor configurator of the system.

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

ln -s …/setup/ setup

Depending on your Nginx configuration.

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

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.

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

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.

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.

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

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.

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 https://github.com/magento/magento2/issues/4159#issuecomment-295335572, or mute the thread https://github.com/notifications/unsubscribe-auth/AANY7cpW8xNBHRzZ5y_Jv-SxWvatOuthks5rxjfSgaJpZM4IHguY.

@dharake Thank you for confirming my findings. In your opinion, is Magento 2.1.1/2.1.2 ready for production use? I am not an expert nor a Magento professional but I am seeing a disconnect between the dev audience who can get it working locally and the production audience trying to deploy Magento. We have been on it in production for about a month now and had nothing but problems and poor third party support. After spending four months on developing our Magento 2 site in house, we just had a sad discussion about reverting to Magento 1.9 for this and a handful of other issues that are just not getting fixed. We’ve had multiple vendors promise Magento 2 support and issues like this have stopped us from connecting to shipping, inventory and marketplace connectors.

Update: Chrome seems to be the issue, firefox works