Username: Password:

Author Topic: Error 403 (reproduced on 2 separate servers)  (Read 690 times)

Offline auggieK

  • Rookie
  • *
  • Posts: 4
    • View Profile
Error 403 (reproduced on 2 separate servers)
« on: June 25, 2020, 01:34:19 AM »
Hi,

I hope this isn't a stupid question - upon starting the bot core, I get StatusCodeError: 403 - "Forbidden".

I have just installed GB and configured the first pair. This is the same error I got on MacOS and a Linux VPS; so I suspect it is license or configuration? Both v18.8.8

Any guidance is appreciated.
Thanks-Aug


---
Loading config...
   info  - socket.io started
GUI Server Deployed: http://localhost:5000
{ StatusCodeError: 403 - "Forbidden"
    at new StatusCodeError (/snapshot/v18build/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.module.exports.plumbing.callback (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.init.self.callback (/snapshot/v18build/node_modules/request/request.js:185:22)
    at Request.emit (events.js:159:13)
    at Request.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:159:13)
    at IncomingMessage.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:254:19)
    at IncomingMessage.emit (events.js:164:20)
    at endReadableNT (_stream_readable.js:1054:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'StatusCodeError',
  statusCode: 403,
  message: '403 - "Forbidden"',
  error: 'Forbidden',
  options:
   { body: '[truncated]',
     method: 'POST',
     uri: 'http://api.gunthy.org:5000/licenseV2',
     headers: { 'content-type': 'text/plain' },
     callback: [Function: RP$callback],
     transform: undefined,
     simple: true,
     resolveWithFullResponse: false,
     transform2xxOnly: false },
  response:
   IncomingMessage {
[truncated]

Offline Aitor

  • Administrator
  • *****
  • Posts: 410
  • Telegram: @AitorRuiz Gunbot.shop
    • View Profile
    • Gunbot
Re: Error 403 (reproduced on 2 separate servers)
« Reply #1 on: June 25, 2020, 02:14:58 AM »
Hi,

I hope this isn't a stupid question - upon starting the bot core, I get StatusCodeError: 403 - "Forbidden".

I have just installed GB and configured the first pair. This is the same error I got on MacOS and a Linux VPS; so I suspect it is license or configuration? Both v18.8.8

Any guidance is appreciated.
Thanks-Aug


---
Loading config...
   info  - socket.io started
GUI Server Deployed: http://localhost:5000
{ StatusCodeError: 403 - "Forbidden"
    at new StatusCodeError (/snapshot/v18build/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.module.exports.plumbing.callback (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/snapshot/v18build/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.init.self.callback (/snapshot/v18build/node_modules/request/request.js:185:22)
    at Request.emit (events.js:159:13)
    at Request.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:159:13)
    at IncomingMessage.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:254:19)
    at IncomingMessage.emit (events.js:164:20)
    at endReadableNT (_stream_readable.js:1054:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'StatusCodeError',
  statusCode: 403,
  message: '403 - "Forbidden"',
  error: 'Forbidden',
  options:
   { body: '[truncated]',
     method: 'POST',
     uri: 'http://api.gunthy.org:5000/licenseV2',
     headers: { 'content-type': 'text/plain' },
     callback: [Function: RP$callback],
     transform: undefined,
     simple: true,
     resolveWithFullResponse: false,
     transform2xxOnly: false },
  response:
   IncomingMessage {
[truncated]

Hi AuggieK, 403 means your IP isn't allowed to access. Maybe you are connecting from a country that isn't allowed in your exchange? Maybe your api restrictions doesn't allow your IP to connect (check if you have enabled IP white list etc...).

Offline auggieK

  • Rookie
  • *
  • Posts: 4
    • View Profile
Re: Error 403 (reproduced on 2 separate servers)
« Reply #2 on: June 25, 2020, 02:26:45 AM »
Hi - Thanks for the response. I'm connecting to Kraken from the US, so that's not the problem - and I get the same response from 2 separate IPs means that it likely wasn't locked out..

any other ideas?

Offline auggieK

  • Rookie
  • *
  • Posts: 4
    • View Profile
Re: Error 403 (reproduced on 2 separate servers)
« Reply #3 on: June 25, 2020, 03:06:25 AM »
Also tried to go back to 18.3 (saw that there were some Kraken problems) but no change....

Offline Aitor

  • Administrator
  • *****
  • Posts: 410
  • Telegram: @AitorRuiz Gunbot.shop
    • View Profile
    • Gunbot
Re: Error 403 (reproduced on 2 separate servers)
« Reply #4 on: June 25, 2020, 04:13:36 PM »
Also tried to go back to 18.3 (saw that there were some Kraken problems) but no change....

I would try changing your api key for a new one. In order to do that, please contact with your resellers, or send me a PM stating your new api key and wallet if you don't have reseller.

Offline beefrog

  • Rookie
  • *
  • Posts: 1
    • View Profile
Re: Error 403 (reproduced on 2 separate servers)
« Reply #5 on: June 26, 2020, 04:04:12 AM »
I'm receiving the same.

I'm having trouble activating gunbot.  Im using latest beta now.   I believe the bot activates licenses upon successful API pull but my fresh API is getting 403 from binance.  This is a fresh api with no IP restriction and all proper settings.

Any suggestions?  Should I try a stable version?

I have binance support also looking into it but they sent my case to a "api tech" .  Ive tested a few bots from a few IPs so maybe I am flagged some how but I was surprised that OP has the same error.
« Last Edit: June 26, 2020, 04:12:18 AM by beefrog »

Offline Aitor

  • Administrator
  • *****
  • Posts: 410
  • Telegram: @AitorRuiz Gunbot.shop
    • View Profile
    • Gunbot
Re: Error 403 (reproduced on 2 separate servers)
« Reply #6 on: June 26, 2020, 05:54:43 AM »
I'm receiving the same.

I'm having trouble activating gunbot.  Im using latest beta now.   I believe the bot activates licenses upon successful API pull but my fresh API is getting 403 from binance.  This is a fresh api with no IP restriction and all proper settings.

Any suggestions?  Should I try a stable version?

I have binance support also looking into it but they sent my case to a "api tech" .  Ive tested a few bots from a few IPs so maybe I am flagged some how but I was surprised that OP has the same error.

Take a look at this please:

https://gunbot.shop/error-403-when-running-gunbot-how-to-fix/

Offline auggieK

  • Rookie
  • *
  • Posts: 4
    • View Profile
Re: Error 403 (reproduced on 2 separate servers)
« Reply #7 on: June 26, 2020, 09:30:36 PM »
Wanted to document the solution for others...

@Aitor figured it out - my Gunthy wallet was not properly registered with the license system.

(TY Aitor)

« Last Edit: June 29, 2020, 10:00:03 PM by Aitor »

Offline Aitor

  • Administrator
  • *****
  • Posts: 410
  • Telegram: @AitorRuiz Gunbot.shop
    • View Profile
    • Gunbot
Re: Error 403 (reproduced on 2 separate servers)
« Reply #8 on: June 29, 2020, 10:00:13 PM »
You are welcome  ;)