error: [acp] Failed to fetch latest version



  • After upgrading to 1.8.1, I receive this error when accessing the main admin page:

    2018-03-24T14:13:03.697Z [5805] - info: Initializing NodeBB v1.8.1 https://www.foo.bar
    2018-03-24T14:13:06.360Z [5805] - info: [socket.io] Restricting access to origin: https://www.foo.bar:*
    2018-03-24T14:13:06.964Z [5805] - info: Routes added
    2018-03-24T14:13:06.971Z [5805] - info: NodeBB Ready
    2018-03-24T14:13:06.981Z [5805] - info: Enabling 'trust proxy'
    2018-03-24T14:13:06.992Z [5805] - info: NodeBB is now listening on: 0.0.0.0:60606
    2018-03-24T14:13:23.945Z [5805] - error: [acp] Failed to fetch latest version Error: Forbidden
        at Error (native)
        at Request._callback (/home/curv/nodebb/src/admin/versions.js:36:20)
        at Request.self.callback (/home/curv/nodebb/node_modules/request/request.js:186:22)
        at emitTwo (events.js:106:13)
        at Request.emit (events.js:191:7)
        at Request.<anonymous> (/home/curv/nodebb/node_modules/request/request.js:1163:10)
        at emitOne (events.js:96:13)
        at Request.emit (events.js:188:7)
        at IncomingMessage.<anonymous> (/home/curv/nodebb/node_modules/request/request.js:1085:12)
        at IncomingMessage.g (events.js:292:16)
        at emitNone (events.js:91:20)
        at IncomingMessage.emit (events.js:185:7)
        at endReadableNT (_stream_readable.js:974:12)
        at _combinedTickCallback (internal/process/next_tick.js:80:11)
        at process._tickCallback (internal/process/next_tick.js:104:9)
    

    (the version box is red showing 1.8.1 with the message "latest-lookup-failed")

    Tom


  • Global Moderator

    @tlinden are you behind a corporate firewall or anything like that? Fetching the latest version released on GitHub, but your NodeBB server can't access GitHub for some reason.



  • @pitaj 0_1521961028214_19cc064e-04ee-453f-bccd-dc3213e206b6-image.png
    me too!



  • @PitaJ well, I have updated NodeBB via Github just moments before. So I am pretty sure, the server is able to reach it.

    However, if I try to fetch the uri from the commandline, I get:

    % curl https://api.github.com/repos/NodeBB/NodeBB/tags
    {
      "message": "API rate limit exceeded for 95.143.*.*. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
      "documentation_url": "https://developer.github.com/v3/#rate-limiting"
    }
    

  • Global Moderator

    @tlinden the API is rate limited but I can't think of any way you could normally hit the rate limit of 60 per hour, especially since NodeBB should have the response and only request again if there's an update.

    The only thing I can think of is that you might have restarted NodeBB 60 times in an hour?



  • No, I had some restarts during the update, yes, because going from 1.8.0 to 1.8.1 was not that smooth as during the last update.

    However, I don't have regular restarts. The last one was on saturday 22:00 CEST. But the error still appears.

    Maybe my IP is blacklisted and needs to be removed from the blacklist somehow?



  • Oh - I'm on a shared system, maybe some other user is accessing github API from the same IP.

    Damn 😞



  • I have same problem.

    Using VPS on GCP and i got this error.

    While on digitalocean VPS, i don't have any error with same settings.

    There is no firewall issue on GCP side as far as i know about. I am not sure what is the problem.

    On log file, there is translation issue about fetching but it shouldn't be because digitalocean and gcp has same setting on setup.


  • Global Moderator

    @TLINDEN @Kayrah can you post or PM me your Site Title as set at ACP > Settings > General ? I'm thinking it could have something to do with it.


 

| |