--- title: Troubleshooting for Unit 7 Lab --- ### Troubleshooting for Unit 7 Lab - Challenge 0: - Restart after installing Vagrant #### Challenge 1: ##### Issue 1: - hosts-updater is not properly adding the IP mapping due to the lack of admin privilege. Running powershell in administrator fails to resolve the issue. ##### Solution 1: Run notepad in admin, and open the hosts file located at C:\Windows\System32\drivers\etc. - Manually add the IP mapping as shown below, and save the file. - 192.168.33.10 wpdistillery.vm - Run vagrant up. ##### Solution 2: Downgrade the vagrant hostsupdater to version 1.2.1 and 1.2.2 so the IP mapping can function. - vagrant plugin install vagrant-hostsupdater --plugin-version=1.2.1 - vagrant plugin install vagrant-hostsupdater --plugin-version=1.2.2 :::info Note 1: Removing hosts-updater plugin and manually editing the host files works. ::: ##### Issue 2: - Firefox addons such as DuckDuckGo Essentials or Facebook Container may cause the http://wpdistillery.vm/ to be stuck in loading. ##### Solution 1: Run in private window and slowly allow addons to be run in private to identify which is the cause. ##### Solution 2: Load http://wpdistillery.vm/ into a different browser. #### Challenge 2: - No issues found - working as expected. #### Challenge 3: - No issues found - working as expected. #### Challenge 4: - Get API Token from https://wpscan.com/ ##### Issue: - Performing wpscan --update may cause scan to abort due to characters found that can't be used to start any token. ##### Solution: - Space the api_token: YOUR_API TOKEN by two spacebar instead of one tab ```console NO: api_token ``` ```console YES: api_token ``` #### Challenge 6: - No issues found - working as expected. #### Challenge 7: ##### Issue: - If receiving a Not Found page. Double check the permalink is set to Default. The settings may have resetted after performing vagrant destroy. ##### Solution: - In the Admin page, go to the setting and click permalinks. Set it to Default.