Can not access Web Setup Wizard with 2.1 clean install

[cizgidekiadam]

Preconditions

Magento 2.1.0

Steps to reproduce

1. Clean install 2.1.0
2. Try to access Web Setup Wizard

Expected result

Access to Web Setup Wizard

Actual result

1. ?app=setup Response 302
2. setup Response 301
3. setup/ Response 302
4. setup/index.php/session/unlogin Response 401

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

[chrone81]

Same result after upgrading from 2.0.4 to 2.1.0, Web Setup Wizard is missing.

[EugeneVdovenko]

Same result after upgrading from 2.0.7 to 2.1.0

[nobodypb]

Try entering "setup/" into the addressbar manually. In my case the admin cookie is lost between step 2 and 3

[ghost]

Same issue here with a clean install of 2.1. The setup wizard is not there in the system menu.

[ghost]

This is an expected result if you use pub as your Magento docroot; it's designed this way so you cannot run the Web Setup Wizard in a production environment. Try setting the docroot to the Magento install directory and you should see the wizard again.

[ghost]

Web Setup wizard does not work if using the install directory as docroot or pub in 2.1.

It was also in the 2.1 release notes that the Web Setup wizard is now accessible when using pub as the docroot.

• The Web Setup Wizard now works when Magento is installed in /pub. (GITHUB-4159)

[cizgidekiadam]

Docroot is not /pub folder. Same problem exist in 2.0.7 and 2.1

[ghost]

Are there any updates on this issue? Is it a confirmed known issue?

[ghost]

I don't think so. I have installed CE and EE 2.1 recently and am able to use the Setup Wizard. Hopefully someone from engineering will respond. Sorry for the trouble.

[piotrekkaminski]

The release notes are incorrect here @tanberry. The issue was not fixed due to unexpected challenges and is scheduled for next version, tracked internally as MAGETWO-52799. You can find more information #4159.

[tanberry]

@rbostan and @crtsl apologies that this issue is listed is Fixed in Rel Notes. As @piotrekkaminski explains above it was a last minute realization, and we failed to reflect final decision.

[cizgidekiadam]

@tanberry @piotrekkaminski Thanks a lot for information. That mistake is not deadly bloody important for us as developers but end users may be 😄

[tanberry]

Sure, @rbostan, we really don't want any deadly nor bloody issues. ;-) Thanks for helping us stay safe; please keep up the communications, we appreciate it!

[carfantasy]

Is there any solution available?

[alexgran]

Is there a workaround to access the wizzard? I'd like to install a couple of modules...?
Got a clean and fresh isntallation, docroot is installation folder

[wert2all]

This is a copy of #4159 what was reopened. Thanks for reporting, closed as copy

[michaelmcgregor]

installing magento 2.1.2 to puplic.html as main domain. Then configure the second domain as multistore by parked domain direction. Websetup wizard dont working (setup/index.php/session/unlogin Response 401).
who can explain how can ı fix

[shuidaan]

@michaelmcgregor i have the problem same as you, Do You solve this problem ? could you give a email . shuidaan@gmail.com
installing magento 2.1.2 to puplic.html as main domain. Then configure the second domain as multistore by parked domain direction. Websetup wizard dont working (setup/index.php/session/unlogin Response 401).
who can explain how can ı fix

[jmsalomr]

Same problem for me in a fresh install of magento CE 2.1.3. I'm using nginx.
I'm using sample nginx config that comes with the installation.

Anybody knows how to fix that?

[simonfunk]

Same here. would be happy for any advice. using CE 2.1.2

[Ylmzef]

Same here too CE 2.1.3

[jeversen]

Same problem here, just upgraded to 2.1.4 but no web-setup-wizard

[tanberry]

@jeversen , lemme look into this. @xcomSteveJohnson ?

[che2on]

Hello, I am running the latest 2.1.4, there is a label in right corner showing correct version number. However, when I enter system upgrade through web setup wizard, I see a message "error in update" with rollback button. In reality, the system is running on 2.1.4. Just want to get rid of error message as it is misleading, can u tell me how to clean that message. I might want to update 2.1.5 when it's available so need web set up wizard for future.

[ghost]

@che2on This is based on memory but look for hidden files in the var directory. If there was a real or imaginary error during upgrade, I think there might be a file named .upgrade_err or something. Try renaming it or deleting it.

[che2on]

@xcomSteveJohnson Awesome. Removing .update_error.flag in var directory solved the problem. Now I can access the web set up wizard and it says I am running the latest magento! Thank you.

[jeversen]

@tanberry @xcomSteveJohnson Searched in the /var directory but no dot-error-alike files there. I must add that I installed 2.1.3; with no web-setup-wizard. But after upgrading (through composer...) to 2.1.4 there is still no web-setup-wizard.

Also tried to move the nginx -docroot to $MAGE_ROOT instead of $MAGE_ROOT/pub but it opened another can of worms. And because this means a considerable security-risk I wont even consider that solution-path an option.

Any other idea's ?

[korostii]

Hi @magento-engcom-team,

Are you sure that the issue is resolved? (see comments above)
Could you please link the corresponding commits which supposedly fix this bug?

Thanks in advance.

[jalot]

same problem here on clean install.
no difference on install by ftp (web setup) or by composer.
issue remains

[Carcinie]

Clean install of 2.2. Same problem.

[jalot]

I solved it by manually installation of extensions thru composer commands with putty. Works fine. Although i would love to have a working web setup wizard Verstuurd vanaf mijn iPhone Op 29 okt. 2017 om 10:30 heeft Raiden9000 <notifications@github.com<mailto:notifications@github.com>> het volgende geschreven: Clean install of 2.2. Same problem. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5247 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AfkR12WaCe64zJ8_ULvNNoWVKNhSY-lnks5sxEWWgaJpZM4I-SfM>.

[Carcinie]

I got it to show up. I was following this tutorial for installing magento: https://www.howtoforge.com/tutorial/how-to-setup-magento-2-with-varnish-and-apache-on-ubuntu-1604/

What I changed was the port from 8080 (as indicated in the tut) to 80 default.
The reason it's changed to 8080 is to run Varnish on 80.

[pier28inc]

Fresh install on Debian with PHP7.1 and Magento CE 2.2.1. Same result. Cache Management, Backups, and Index Management are the only options under the Tools menu. We've delayed over a year upgrading out of Magento 1.9.X because of this issue and the product is still not usable. There's no way that we'll ever spend the money to upgrade to be a paid customer when the codebase is this bad for this long.

[tony-sar]

I had the same issue when i moved my magento from shared hosting to vps .. i had no access to wizard with 401 error. decided to use composer to upgrade and that failed because my PHP version was not compatible with 2.2.1 so decided to switch PHP to 7.0.24 , after rebooting apache , decided to take a look at wizard one more time , and to my surprise , IT WORKD ..

as per magento doc .. php 7.1 is not compatible with magento 2 so maybe switching to something compatible like 7.0.x would help. this was just my experience with this issue , hope will help others.

[DyrectaLab]

I had the same issue:
Magento : 2.1.8 CE
Nginx : 1.13.5
PHP-fpm : 7.0.22-0
OS ubuntu : 16.04
MariaDB : Ver 15.1 Distrib 10.0.31-MariaDB
Redis-server : Redis server v=3.0.6

I've temporary solved with:

• Log in backend
• Open url : https://www.shop.it/admin_xxxx/admin/backendapp/redirect/app/setup/
  And then the setup wizzard open correctly.

Any stable fix for this issue?

[lbetineli]

Fresh install of 2.2.2 CE and same problem. Nginx 1.10.3 (Ubuntu 16.04).
MYSql 14.14, PHP 7.0.22-0

[rparsi-commer]

@lbetineli How about 2.3 CE?

[korostii]

@rparsi-commer Last time I checked, 2.3 wasn't released yet :)

[rparsi-commer]

@korostii Well I see the "Fixed in 2.3.x" label...so I thought one could checkout that version and try again

[korostii]

Well, it also says Fixed in 2.1.x, Fixed in 2.2.x, but that doesn't seem to be true neither.

Besides, in case of 2.3 it's of little use because it's basically a develop version, nowhere near stable and not suitable for use in production. Feel free to check it out all you want, but IMHO it would be a total waste of time in this case.

[rparsi-commer]

@korostii I don't think this is in magento team's list of priorities, and even if eventually fixed by the time that happens do we even need a setup wizard?
I find it easier to just use the cli for such things.

[tlc033]

Solution for me was:
Base URLs (Secure)
-> Use Secure URLs on Storefront -> Yes
-> Use Secure URLs in Admin -> Yes
-> Enable HTTP Strict Transport Security (HSTS) -> Yes
-> Upgrade Insecure Requests -> Yes
php bin/magento cache:clean
https://yadi.sk/i/iPJi4k7X3S86Za
I SOLVE THIS.

[ncompass]

@tlc033
THE MAN IS NOT LYING. BEST QUICK FIX

[fwolfst]

I could not udate these values via the admin backend (error regarding placeholer/template). I guess in core_config_values table its these values: web/secure/enable_upgrade_insecure and web/secure/enable_hsts. However, setting these to "1" (where "0" before did not solve the issue for me. Btw, after I changed the values in the db I can now change them in the backend without error.

[michelve]

Still having this issue any permanent solution

[epileftro85]

i have the same issue, any update in this? version 2.2.3, mac os and nginx, fresh install.

[DonMooi]

This is getting lame, 2.2.3 same problem ---> websetup wizard goes to /unlogin and gives a 401 authorization error.

PHP71
Appache/Nginx
Root not in PUB

Tried sollution:

Solution for me was:
Base URLs (Secure)
-> Use Secure URLs on Storefront -> Yes
-> Use Secure URLs in Admin -> Yes
-> Enable HTTP Strict Transport Security (HSTS) -> Yes
-> Upgrade Insecure Requests -> Yes
php bin/magento cache:clean

Did not work for me!

[epileftro85]

I’ve notice or I think it is cache problem, because I opened on incognito with no problems, and after try it again, and it works

[DonMooi]

This is getting lame, 2.2.3 same problem ---> websetup wizard goes to /unlogin and gives a 401 authorization error.

PHP71 / Appache/Nginx / Root not in PUB

Tried sollution:

Solution for me was:
Base URLs (Secure)
-> Use Secure URLs on Storefront -> Yes
-> Use Secure URLs in Admin -> Yes
-> Enable HTTP Strict Transport Security (HSTS) -> Yes
-> Upgrade Insecure Requests -> Yes
php bin/magento cache:clean

Did not work for me!

More testing:

1. I have noticed that in the configuration file app/etc/env.php the session save is set to db:

Code:
'save' => 'db',

so I have changed to files:

Code:
'save' => 'files',

And flushed the Magento cache.

This did not fix the problem....

2. Then I made sure all the correct permissions are set for all directories and files....

This did not fix the problem either....

3. I have noticed that the ownership of the magento directory is "nobody"

Change this to the main admin user

This did not fix the problem either.....

4. I have tested the case with PHP70 and PHP71

but sadly again to no avail....

5. I have also checked if the local php.ini file is not causing the issue

But again this was not the cause....

6. My magento installation was installed in a directory, I moved the installation to the root.

NO success either.

As I have written in my previous post, this is getting LAME! How is it possible that an eCommerce application like Magento has these major bugs.

YES we can install extensions manually through SSH or Putty, but not all extension developers offer instructions on how to do that.

I would urge everybody to write down the tests that they have done towards a fix and post it here... so we don't have to invent the wheel again.

[TechnoBuddhist]

What worked for me...

ln -s [magento-install-dir]/setup [magento-install-dir]/pub/setup

After installing mods/updates, remove the link

rm [magento-install-dir]/pub/setup

If the symbolic link doesn't work for you, check permissions and ownership(mine was set to nobody - the apache.http user)

chown [magento-user]:[magento-user] [magento-install-dir]/setup/*

Hope this helps!

[PieroBonforte]

I found this solution for magento 2.2.4

http://phpcodez.com/configure-memcached-magento-2/

for me worked.

[ghost]

I will be out of the office from May 4 and returning May 14. Please send your inquiries to sales@roselandtech.ca during this period

[chriskim-kissusa]

In my case, When I downgrade php version 7.1 to 7.0, It works for me.
hope this help.

[3615helloworld]

I am on Magento 2.3. I have the same issue. @tlc033 fix does not work for me. Did a genius managed to fix that? A step by step would be much appreciated!

Solution for me was:
Base URLs (Secure)
-> Use Secure URLs on Storefront -> Yes
-> Use Secure URLs in Admin -> Yes
-> Enable HTTP Strict Transport Security (HSTS) -> Yes
-> Upgrade Insecure Requests -> Yes
php bin/magento cache:clean
https://yadi.sk/i/iPJi4k7X3S86Za
I SOLVE THIS.

Also, there is no /setup folder in my /pub directory. Does the Symlink solution would still work? @TechnoBuddhist

What worked for me...

ln -s [magento-install-dir]/setup [magento-install-dir]/pub/setup

After installing mods/updates, remove the link

rm [magento-install-dir]/setup

If the symbolic link doesn't work for you, check permissions and ownership(mine was set to nobody - the apache.http user)

chown [magento-user]:[magento-user] [magento-install-dir]/setup/*

Hope this helps!

[urfusion]

I am still facing the issue with my magento v 2.2.6 which I have upgraded by command line from V2.1. I have tried all the solution mention above such as "Symbolic link", "session is already is in the file", "Permission and ownership" but nothing working. Anyone find out the solution.

[PrakashElsner]

If u are installing magento2 in nginx+varnish webserver then varnish must on port 80 and backend port 8080 and nginx port must be 8080.
Then create virtual hosts like this in directory /etc/nginx/conf.d/
Magento installation path must match according to magento virtual host
1.magento.test.conf

server {
listen 8080;
server_name magento.test;

 access_log /var/log/nginx/magento.test.access.log;
error_log /var/log/nginx/magento.test.error.log;


root /usr/share/nginx/html/magento;

index index.html index.htm index.php;
    autoindex on;
    autoindex_exact_size off;
    autoindex_localtime on;
 #   include /etc/nginx/conf.d/magento.phpmyadmin.conf;
    location / {
    try_files /maintenance.html $uri $uri/ @handler; ## If missing pass the URI to Magento's front handler
    expires 30d; ## Assume all files are cachable
}
location @handler { ## Magento uses a common front handler
    rewrite / /index.php;
}
location ~ .php/ { ## Forward paths like /js/index.php/x.js to relevant handler
    rewrite ^(.*.php)/ $1 last;

}
location ~ .php$ {
include /etc/nginx/fastcgi_params;
include /etc/nginx/fastcgi.conf;
fastcgi_pass 127.0.0.1:9001;
fastcgi_index index.php;
fastcgi_param SERVER_PORT 8080;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param MAGE_RUN_CODE default; ## Store code is defined in administration > Configuration > Manage Stores
fastcgi_param MAGE_RUN_TYPE store;
}

}
#End

And then do hosts entry in /etc/hosts > localhost magento.test
Then open http://magento.test in browser.
Make sure your php-fpm www.conf, and php session file has correct ownership of nginx.
Then u can start installing.