installation is incomplete. check the console log for errors before trying again.,magento stuck at 67%,magento 2 installation not working,magento 2 installation user configuration,magento 2.2 installation guide,magento installation stuck at 99,magento 2 setup install,magento 2 500 internal server error

If you have successfully installed Magento 2 on the xampp server but having an issue of loading the admin page as it is giving you a 404. Also, when loading its homepage the default theme,it doesn’t apply and instead gives you the following errors:

Failed to load resource: the server responded with a status of 404 (Not Found)
:7777/Magento/pub/static/version1491913172/adminhtml/Magento/backend/en_US/extjs/resources/css/ext-all.css Failed to load resource: the server responded with a status of 404 (Not Found)
:7777/Magento/pub/static/version1491913172/adminhtml/Magento/backend/en_US/jquery/jstree/themes/default/style.css Failed to load resource: the server responded with a status of 404 (Not Found)
mixins.js Failed to load resource: the server responded with a status of 404 (Not Found)
require.js Failed to load resource: the server responded with a status of 404 (Not Found)
magento-icon.svg Failed to load resource: net::ERR_CONNECTION_RESET
mixins.js Failed to load resource: net::ERR_CONNECTION_RESET
requirejs-config.js:66 Uncaught TypeError: require is not a function
    at requirejs-config.js:66
    at requirejs-config.js:71
    at requirejs-config.js:423
127.0.0.1/:39 Uncaught TypeError: require.config is not a function
    at 127.0.0.1/:39
127.0.0.1/:87 Uncaught TypeError: require is not a function
    at 127.0.0.1/:87
127.0.0.1/:298 Uncaught TypeError: require is not a function
    at 127.0.0.1/:298
127.0.0.1/:430 Uncaught TypeError: require is not a function
    at 127.0.0.1/:430
127.0.0.1/:475 Uncaught TypeError: require is not a function
    at 127.0.0.1/:475
127.0.0.1/:533 Uncaught TypeError: require is not a function
    at 127.0.0.1/:533
127.0.0.1/:556 Uncaught TypeError: require is not a function
    at 127.0.0.1/:556
127.0.0.1/:579 Uncaught TypeError: require is not a function
    at 127.0.0.1/:579
opensans-400.woff2 Failed to load resource: net::ERR_CONNECTION_RESET
admin-icons.woff2 Failed to load resource: net::ERR_CONNECTION_RESET
opensans-600.woff2 Failed to load resource: net::ERR_CONNECTION_RESET
opensans-700.woff2 Failed to load resource: net::ERR_CONNECTION_RESET
opensans-400.woff Failed to load resource: net::ERR_CONNECTION_RESET
admin-icons.woff Failed to load resource: net::ERR_CONNECTION_RESET
opensans-600.woff Failed to load resource: net::ERR_CONNECTION_RESET
opensans-700.woff Failed to load resource: net::ERR_CONNECTION_RESET
opensans-400.ttf Failed to load resource: net::ERR_CONNECTION_RESET
admin-icons.ttf Failed to load resource: net::ERR_CONNECTION_RESET
opensans-600.ttf Failed to load resource: net::ERR_CONNECTION_RESET
opensans-700.ttf Failed to load resource: net::ERR_CONNECTION_RESET

SOLUTION 1:

first of all http://devdocs.magento.com/

The important things:

The owner of the Magento file system: Must have full control (read/write/execute) of all files and directories.

Must not be the web server user; it should be a different user.

The web server user must have write access to the following files and directories: var app/etc pub (and probably new in 2.2.1:) generated

In addition, the web server’s group must own the Magento file system so that the Magento user (who is in the group) can share access to files with the web server user. (This includes files created by the Magento Admin or other web-based utilities.)

We recommend setting the permissions as follows:

All directories have 770 permissions.

770 permissions give full control (that is, read/write/execute) to the owner and to the group and no permissions to anyone else.

All files have 660 permissions.

660 permissions mean the owner and the group can read and write but other users have no permissions.

You should set as bellow recommended.

cd  

find . -type f -exec chmod 644 {} \;                        // 644 permission for files

find . -type d -exec chmod 755 {} \;                        // 755 permission for directory 

find ./var -type d -exec chmod 777 {} \;                // 777 permission for var folder    

find ./pub/media -type d -exec chmod 777 {} \;

find ./pub/static -type d -exec chmod 777 {} \;

chmod 777 ./app/etc

chmod 644 ./app/etc/*.xml

chown -R : .

chmod u+x bin/magento

SOLUTION 2:

In some rare cases, you can’t use 770 and 660, like @MagenX says, 755 and 644 could also be the permission you need. (Some Fast-CGI users I guess)

So in that case, you run:

find . -type d -exec chmod 755 {} \; && find . -type f -exec chmod 644 {} \; && chmod u+x bin/magento

That seems to fix it, but if Magento generates new files or directories, those will have the permission 770 and 660 again. You can edit those default chmod values in the following files:

/vendor/magento/framework/Filesystem/DriverInterface.php 
(WRITEABLE_DIRECTORY_MODE and WRITEABLE_FILE_MODE)

/lib/internal/Cm/Cache/Backend/File.php 
(directory_mode and file_mode)

After these changes, run the first command again and after that, newly generated files shouldn’t be an issue anymore.

Note: Editing files like this is never a good idea, but I suspect these chmod options are going to be configurable in the future, so I took the easy way.

after making above changes please execute below command.

php bin/magento setup:static-content:deploy

Please try this and let me know if you need any other help. or you can contact me on my skype : mayur.jadeja8

I hope this will help you.