{"message":"Could not check for updates.Request failed with status code 404","stack":"Error: Request failed with status code 404\n at createError (C:\\Users\\User\\AppData\\Local\\MoBro\\app-1.0.0-beta5\\resources\\app.asar\\node_modules\\axios\\lib\\core\\createError.js:48:15)\n at settle (C:\\Users\\User\\AppData\\Local\\MoBro\\app-1.0.0-beta5\\resources\\app.asar\\node_modules\\axios\\lib\\core\\settle.js:49:12)\n at IncomingMessage.handleStreamEnd (C:\\Users\\User\\AppData\\Local\\MoBro\\app-1.0.0-beta5\\resources\\app.asar\\node_modules\\axios\\lib\\adapters\\http.js:268:11)\n at IncomingMessage.emit (events.js:215:7)\n at endReadableNT (_stream_readable.js:1183:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","config":{"url":"https://www.mod-bros.com/api/mobro/update","method":"get","params":{"version":"1.0.0-beta5"},"headers":{"Accept":"application/json, text/plain, */*","User-Agent":"axios/0.19.2"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1}}
All 404 Not Found messages, checking in my browser confirms.
Replies
1 - 2 (2)
Hey @Bobtb,
oh, yeah I forgot that we are actually creating log files for that error ?. We're in the process of deploying a new update server for our MoBro update that we'll launch this week (hopefully tomorrow).
There might be a lot of log files, if there are too many, please just remove them ?
Thanks for the heads up!
Hey @Bobtb, thanks for the feedback, we changed the logging a little bit and won't hold on to that many files anymore.
