|[FTL] Could not create runner: could not parse provider config file: EOF

[0xPugal]

Describe the bug A clear and concise description of what the bug is.

./reconftw -d target.com -a

 Running : Passive Subdomain Enumeration 
|[FTL] Could not create runner: could not parse provider config file: EOF
-
 5019 new subs (passive) in 1 minutes, 49 seconds. 
/[FTL] Could not create runner: could not parse provider config file: EOF

 Running : Crtsh Subdomain Enumeration 
-[FTL] Could not create runner: could not parse provider config file: EOF
/
 17 new subs (cert transparency) in 19 seconds. 
\[FTL] Could not create runner: could not parse provider config file: EOF

 Running : Active Subdomain Enumeration 
|[FTL] Could not create runner: could not parse provider config file: EOF
|
 40 subs DNS resolved from passive in 1 minutes, 20 seconds. 
\[FTL] Could not create runner: could not parse provider config file: EOF

 sub_noerror skipped in this mode or defined in reconftw.cfg 

 Running : Bruteforce Subdomain Enumeration 
|[FTL] Could not create runner: could not parse provider config file: EOF
|
....
 Subdomain Enumeration Finished 
[FTL] Could not create runner: could not parse provider config file: EOF
 Results are saved in redacted.com/subdomains/subdomains.txt and webs/webs.txt
#######################################################################

#######################################################################
 Http probing non standard ports 
/[FTL] Could not create runner: could not parse provider config file: EOF

Screenshots

[six2dez]

There is some file empty in your end that crashes the entire workflow