Hi @amaria.gallego - I am going to step in for @jwdebelius. The error is a little confusing, but what it is saying is that one of your FASTQ files is corrupt (it might be missing sequence data around line 13 of a specific file). To figure out which file, we can work backwards:
The filename in the error message tells us two things: which sample is impacted, and which read direction is impacted. It looks like the sample ID is DFbaby2, and the read direction is forward, because of the R1. Now, working backwards, in your manifest file, looking up the filepath for the forward reads of DFbaby2:
/home_unal/Biop_Temp/LECHEMATERNA/LECHE/Delivery/result/00.RawData/Sequences/FDMP19H003467-1a_L1_DFbaby2_1.fq
So, go ahead and take a look at that file, specifically. You can run the following and share the results with us, if you wish:
head -n 20 /home_unal/Biop_Temp/LECHEMATERNA/LECHE/Delivery/result/00.RawData/Sequences/FDMP19H003467-1a_L1_DFbaby2_1.fq
One thing to keep in mind - depending on how your files were pre-processed, this error could be more widespread than just this one FASTQ file - we will have to take care of these as they might crop up.
Thanks for double-checking your manifest/metadata - luckily the error message doesn't seem to be indicating that QIIME 2 is upset with that, so we should be all good there.
Keep us posted! 