Thank you Sam,
It was a miscongiguration on the pre-deploy stage, I was able to fix it by following this article:
Thanks!