Originally Posted by p3lim
Did you try a forced update by the way?
|
Yup, tried that too, but without success. The work order gets triggered, but the error remains.
Unfortunately, I'm still running into the same issue even on 0.5.1. Could this be because of my Heroku setup? I'm using the new "Free" dyno on EU servers.
Code:
heroku/web.1: Starting process with command `npm start`
app/web.1: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
app/web.1: Recommending WEB_CONCURRENCY=1
app/web.1: > [email protected] start /app
app/web.1: > node server.js
heroku/web.1: State changed from starting to up
app/web.1: [LOG] Successfully fetched addon list.
heroku/router: at=info method=GET path="/force/ckaosMilitia/6.2v2-release" host=ckaotik-wow-addons.herokuapp.com request_id=169da82e-b1b0-4a2f-8497-3763a5e9c61f fwd="85.181.242.174" dyno=web.1 connect=0ms service=18ms status=304 bytes=131
app/web.1: [LOG] Received forced check for "ckaosMilitia" version "6.2v2-release".
app/web.1: [LOG.1] Work order #1 started
app/web.1: [LOG.1] Found tag link on CurseForge.
app/web.1: [LOG.1] Successfully downloaded file from CurseForge.
app/web.1: [LOG.1] Found file link on CurseForge.
app/web.1: [LOG.1] Successfully authenticated with WowInterface.
app/web.1: [ERR.1] "http://api.wowinterface.com/addons/details/23324.json" responded with code 403: "[object Object]"