APIs Not Activating Despite Correct Configuration in datasources.yaml

[hxlxmjxbbxs]

Hello Amass Team,

I am experiencing an issue with the latest version of Amass where the APIs I configured are not activating, despite following the standard procedures for configuration. I'm detailing the steps I've taken below to aid in troubleshooting:

Configuration File Source: Downloaded the default datasources.yaml from the official Amass GitHub repository to ensure there are no syntax errors.

File Placement: Placed the datasources.yaml file in the default Amass config directory at ~/.config/amass/datasources.yaml.

API Configuration: Configured all my APIs correctly within the datasources.yaml file.

Command Used: The specific command I am running is amass enum -list -config ~/.config/amass/datasources.yaml.

Issue Faced: Despite the above steps, the APIs do not appear to be activating. When running amass enum -list -config ~/.config/amass/datasources.yaml, the APIs are not shown as working.

Impact: This issue is particularly concerning as I have invested in multiple API services specifically for use with Amass, and the current inability to integrate these services effectively is causing significant inconveni

ence and financial impact.

Request for Assistance:
I would appreciate guidance on how to resolve this issue. If there are any additional steps I should take, alternative configurations, or if this is a known issue with a workaround, your assistance would be greatly appreciated.

Additional Information:

Amass Version: v4.2.0
Operating System: Linux hxlxmj 6.5.0-kali3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1kali1 (2023-10-09) x86_64 GNU/Linux
Thank you for your time and assistance in resolving this matter.

Best regards,
@hxlxmjxbbxs

[Ankeet1729]

I have been facing the same issue. Do tell me if you have found out the way to correct this somehow

[hxlxmjxbbxs]

Yes you have to add both files config.yaml and datasources.yaml

[Ankeet1729]

Can you tell how I do it in config.yaml? In datasources.yaml it was straight forward but not in config.yaml

[The-Inceptions]

When you are specifying your config on the command line, make sure to provide the path for your configuration file, NOT the path for your data sources file.

Example:

amass enum -list -config config.yaml

The path for your data sources file should be written in the configuration file.

To place the data sources file in the configuration, take a look at the Configuration Users' Guide.

[Suryanshuraghav007]

Hi, using the command you give amass enum -list -config /hom/path_to_config_file/config.yaml giving the error
amass enum -list -config ~/.config/amass/config.yaml
Failed to load the configuration file: failed to get absolute path for wordlist file: file does not exist: stat /home/kali/.config/amass/wordlists/subdomains-top1mil-110000.txt: no such file or directory

[The-Inceptions]

Hi, using the command you give amass enum -list -config /hom/path_to_config_file/config.yaml giving the error amass enum -list -config ~/.config/amass/config.yaml Failed to load the configuration file: failed to get absolute path for wordlist file: file does not exist: stat /home/kali/.config/amass/wordlists/subdomains-top1mil-110000.txt: no such file or directory

Try removing objects that you will not use in your configuration. It's always good practice to either comment out or remove any unwanted objects for your situation.

[Suryanshuraghav007]

Please provide solution to this problem

[Suryanshuraghav007]

I have these file in my ~/.config/amass directory.

[The-Inceptions]

@Suryanshuraghav007 Please remove these pictures. The pictures reveal your API keys, which anyone could use. Which could harm your experience and potentially your wallet.

I am speaking about the configuration file for the error you are referring to. If you read the error, you can see that the issue is in relation to the YAML that contains the file path value, which would be the configuration file.

Please remove or comment out any unwanted objects in the configuration file.

[midjarmaksor]

do you slove it ? how?

[hxlxmjxbbxs]

do you slove it ? how?

Yes you have to add both files config.yaml and datasources.yaml

[m4ra7h0n]

Test other configure directory. It works at /Users/apple/Library/Application Support/amass in my Mac