Looks like there is something wrong or interfering with your download file or with Download Monitor. When the browser tries to go to http://iotgurus.net/download/105238/ your server is returning a 500 Internal Server Error. That URL comes from Download Monitor. It thinks your file is at that location. So, something is wrong with that particular URL and/or your file and/or Download Monitor.
Typically, when the server generates a 500 Internal Server Error, it will usually put some stuff into the webserver error log that may clue you in to the problem. It could be that the file is no longer at the location in the filesystem where Download Monitor thinks it should be or the file could be inaccessible due to permissions or something like that.
You could check the webserver error log and look for the 500 error and see if it helps you figure out the issue. Or, you could just look at your download in Download Monitor and then make absolutely certain the file is really where it should be in the filesystem. Or you could just delete the file & upload it again (getting a new download_id) and see if maybe that fixes it. You could go over to the Download Monitor support forum and ask them for help. Or, shot in the dark, you could change the EBD setting “Hide/Mask” to be checked, which causes EBD to access the file in a different way (this probably wouldn’t fix it, but just mentioning it)
Good luck
Thread Starter
wfh010
(@wfh010)
Thanks,
the filepath is solved, but still it doesn’t send an email with the link in it.
Can you ep me one more time?
hendrik
http://www.iotgurus.net/dictionary
It probably is sending the email but it’s probably getting blocked by the email provider (Yahoo, Gmail, etc). That happens a lot on shared hosting systems. The reason is that the From: of the email doesn’t match the account that actually sends the email. You probably need to install Postman SMTP or Custom Sender For Email Before Download and set the From: to be a valid email account for your domain name on that host.
Thread Starter
wfh010
(@wfh010)
YES!
thanks, it’s all working now.