Web Setup Wizard not visible in backend (V.2.1.2) ONGOING

[dharake]

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 in Magento CE 2.1.2
Preconditions:
Magento CE 2.1.2

Steps to reproduce:
Install Magento
Configure Web Root to point to Magento's pub folder
Navigate in admin to System -> Web Setup Wizard

Expected result
Web Setup Wizard page displays

Actual result
No Menu item for Web Setup Wizard
Standard Magento 404 (Whoops, our bad...) page displays if manually directed to URL
When using SSL & Varnish: Receive "This site can’t provide a secure connection" ERR_SSL_PROTOCOL_ERROR

[dharake]

A work around that was achieved on one client's site:

Procedure:
Install Magento 2.1.0
Use the web setup wizard to upgrade Magento to 2.1.2

Result:
You should have the most up to date version with a working Web Setup Wizard

[veloraven]

@dharake thank you for your report.
We already have internal ticket MAGETWO-52799 for this issue.
I have updated it with link to this report.

[dharake]

@veloraven thanks for your help. There was a commit in June for MAGETWO-52799, 2f9ccf0

Any idea if this works? If so would it not have been included in last release in Ocotber of Magento 2.1.2?

[timstoel]

@dharake I am not sure if rolling back to 2.1.0 is an option on our production site. I believe we installed 2.1.1 for our production setup.

Is there a way to get the same results as installing 2.1.0 and upgrading to 2.1.2 by editing some files related to this issue?

[dharake]

Possibly this commit works : 2f9ccf0

Awaiting confirmation from @veloraven

If you test it let me know, but obviously don't do this on your production site :)

[timstoel]

@dharake

In my 2.1.1 installation the lines in app/code/Magento/Backend/etc/di.xml that need to be deleted are not present. In lib/internal/Magento/Framework/App/DocRootLocator.php the file already matches the commit.

I added the three lines to app/code/Magento/Backend/etc/adminhtml/di.xml and nothing has changed.

[dharake]

Ok @timstoel thanks for that. We'll have to wait and see what the Magento peeps have to say. Personally I wouldn't hold my breath seeing they have been sitting on this issue since April. Really poor job I'm afraid, this undermines the whole Magento ecosystem if no one can install mods.

[timstoel]

@dharake So I could get around this by installing 2.1.0 and upgrading to 2.1.2? It would take some time to move our 5000 items with attributes and template and everything, but I've got to move forward somehow. My other option is Magento 1.9 and moving to 2 later on. I can't just sit here and wait for Magento to fix this.

[dharake]

See how you get on with that on a blank install first, but it worked for me. Conversely you'd have to import all the items back to 1.9 anyway, just to have to upgrade again to 2. So although it's a pain, that would still be my recommendation. Especially if you've been working on the templates on 2, because they won't work for 1.9

[timstoel]

I'll spin up another VM with 2.1.0, upgrade it and report back. There is the URL workaround as well, maybe I need to get to 2.1.2 and set up all of my add-ons before I install Varnish.

[dharake]

I do think the URL workaround is possible, I just struggled doing it with Varnish and had no success. Also, if you are using the nginx sample config from Magento, I think you'll find a bunch of other stuff not working as you expect

[timstoel]

I just installed 2.1.0 and the Web Setup Wizard link is missing out of the box. I can use the URL workaround because I have not installed Varnish yet.

My Nginx config is as follows:

`upstream fastcgi_backend {
server unix:/run/php/php7.0-fpm.sock;
}

server {
listen 80;
server_name testing.domain.com;
set $MAGE_ROOT /var/www/magento2;
set $MAGE_MODE developer;
include /var/www/magento2/nginx.conf.sample;
}`

[dharake]

What seriously?? How weird. The exact one I used was:

Magento-CE-2.1.0-2016-06-23-02-28-19.tar

Web setup was definitely there when I installed it

[timstoel]

I used git to install 2.1.0 and it shows 2.1.0 in the backend... Maybe git is my problem

[fooman]

@timstoel looks like it might be too late for this, but anyone else needing to install an extension from Marketplace:

It is possible to install extensions from Marketplace without using the Web Setup Wizard. You do need command line access, then follow these commands (this uses Fooman_OrderManager as an example):

1. Create a Backup making sure we stay in Maintenance Mode
   php -f bin/magento setup:backup --code --db --media && php -f bin/magento maintenance:enable
2. Install via Composer, copy the Component Name from your Marketplace > My Purchases
   php -f vendor/composer/composer/bin/composer require fooman/ordermanager-m2

Public Key: xxxxx
Private Key: xxxxx
To get yours see http://devdocs.magento.com/guides/v2.0/install-gde/prereq/connect-auth.html

3. List all modules - find your new module name under "List of disabled modules"
   php -f bin/magento module:status
4. Enable the new Extension
   php -f bin/magento module:enable Fooman_OrderManager --clear-static-content
5. Run database installation upgrades
   php -f bin/magento setup:upgrade
6. Remove previously compiled classes
   rm -rf var/generation
7. Compile (only needed in Production Mode)
   php -f bin/magento setup:di:compile
8. Deploy Static Content (only needed in Production Mode)
   php -f bin/magento setup:static-content:deploy
9. We are all done - take the store out of maintenance
   php -f bin/magento maintenance:disable

[dharake]

@fooman Nice to hear from you, been using your modules for years! Thanks for chipping in and all the great work! As for the cli installation, that's good for devs, but still feel this issue needs urgent resolution. I have 3 Magento 2 websites that need deployment, and would be handy to have a backend to run upgrades from hehehe.

[fooman]

thanks @dharake - agreed that this needs solving urgently. Just wanted to give some reassurance to folks who might not be aware of the command line approach (and I think it's better to use the command line in this case rather than attempting a downgrade).

[dharake]

Agreed, of course! However in @timstoel case apparently the module can't be installed by CLI for some reason (although that doesn't really make sense come to think of it). @timstoel maybe try this approach?

[timstoel]

Thanks guys. I can try using the CLI to install this, the provider of the module does not support this option. They provide a link to download the files from their website so I did not acquire it through the Magento Marketplace so never really thought of taking this course of action.

[fooman]

@timstoel if it is on the Marketplace installing it without the Web Setup Wizard with the CLI commands I posted works (the vendor doesn't need to do anything special for this, apart from having their extension on Marketplace in the first place)

[dharake]

@veloraven do we have any update for MAGETWO-52799?

[timstoel]

Any news on this?

[timstoel]

@dharake -- I downloaded the 2.1.0 tar file and installed and the Web Setup Wizard is not available in the backend either. This is on a fresh VM with nginx and PHP7.

[Sharlyll]

any solution on this? Its strange because it shows up on one of my domains and disappears in the other domain. Both are hosted on the same server/account.

SOLUTION Please?

[raymatos]

update??

[fooman]

This not fixed. 2.2.6:

[jos-zz]

Upgraded from CE 2.2.5 to CE 2.2.6 using the Web Setup Wizard.
Now, in 2.2.6, when I try to access the Web Setup Wizard, I get 404 Not Found (Whoops, our bad...).
Note that Web Setup Wizard item is present in admin menu in 2.2.6.

On a different instance, which was upgraded to CE 2.2.6 using composer, the Web Setup Wizard is working fine.

[magento-engcom-team]

Hi @TomashKhamlai. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

@TomashKhamlai Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96347, MAGETWO-96348 were created

[pmsteil]

This appears to also be happening on Magento 2.3 also using the Jelastic Magento Cluster install.

I do not have SSL setup and configured, could this be why?

[magento-engcom-team]

Hi @dharake. Thank you for your report.
The issue has been fixed in #20182 by @JeroenVanLeusden in 2.3-develop branch
Related commit(s):

• 8966f5f3a784085d53ee206b1492f708de672e55
• 204675e48423e7472761373cebab698787baffdc

The fix will be available with the upcoming 2.3.2 release.

[dharake]

Hi @dharake. Thank you for your report.
The issue has been fixed in #20182 by @JeroenVanLeusden in 2.3-develop branch
Related commit(s):

• 8966f5f3a784085d53ee206b1492f708de672e55
• 204675e48423e7472761373cebab698787baffdc

The fix will be available with the upcoming 2.3.2 release.

Ah wow! So you're not doing away with the web setup wizard? I thought this was being scraped from Magento.

[jos-zz]

Hello, Thanks for the update. Does this fix the Web Setup for instances running with apache too? Is it possible to apply this fix manually on a CE 2.2.6 instance? Which files should be replaced? Is this the correct one to replace */vendor/magento/framework/App/DocRootLocator.php* ? Anything else I should be aware of?

[magento-engcom-team]

Hi @dharake. Thank you for your report.
The issue has been fixed in #22369 by @JeroenVanLeusden in 2.2-develop branch
Related commit(s):

• 10de6de532aea6ca7a7b58334387f126e151dee2
• 40b5d2e2493f5ad8943203e7af920d703c47d499

The fix will be available with the upcoming 2.2.9 release.