If automatic crawling fails when accessing the login page or when crawling after login, login processing may be restricted or excluded by the Safe Mode setting.
This setting may also be applied unintentionally through initial configuration such as site management. Review the following and take action as needed.
Cause: Access restrictions due to Safe Mode
Safe Mode (Standard or Strong) is a feature that automatically excludes data-changing operations and certain requests from crawling, in order to protect the target site.
Login processing (POST method) is normally allowed. Depending on how the site is built (for example, special parameter handling or JavaScript-based navigation), the login process itself may be treated as restricted, and crawling may fail.
Solution: How to change the settings
1. Change the settings (disable Safe Mode)
Copy the target scan, then go to Basic information > Advanced settings > Safe Mode, change it to Disabled, and save.
2. Verify with “Crawl only”
When starting a crawl/scan, select Crawl only and check whether screens after login are retrieved correctly.
- If crawling succeeds: Safe Mode is the cause. Proceed to the next step.
- If crawling fails: Another factor is likely, such as incorrect credentials or dual-login control.
See the following article: Login fails during automatic crawling / logged out during crawling
https://www.aeyescan.help/hc/ja/articles/37802250006297
3. Exclude specific functions in “Crawl/scan target settings”
With Safe Mode set to Disabled, if there are functions you want to exclude from crawling (such as data deletion, updates, purchases, or inquiries), configure the paths to exclude individually.
Note: To use Crawl/scan target settings, you must copy the scan again.
See the following article: Can I exclude the admin console from crawling and scanning?https://www.aeyescan.help/hc/en-us/articles/37804931815193