Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Aitor

Pages: [1] 2 3 ... 18
Technical Support & Development / Re: ERROR: SQLITE BUSY
« on: July 03, 2020, 09:12:42 PM »
Glad to hear to found a way to fix it  :)

Technical Support & Development / Re: multiple base and pair settings
« on: July 02, 2020, 10:16:34 PM »
Hi, what you can use with multiple_base:





But try to avoid using same quote for different base coins, for example:


Hope this helps.

So i just purchased gunbot and received my gunthy in my wallet.  I setup the bot to test and get this error.  I purchased gunbot ultimate? 

Please Advice

I reverted back to the old api and now i am seeing a captcha message in the terminal

Hi, if you purchased your license directly from send me an email: or contact me via Telegram: @AitorRuiz
In the case you purchased from other reseller, contact him as it looks like your license / api is not properly registered.

Beginners & Help / Re: Error 403 (reproduced on 2 separate servers)
« on: June 29, 2020, 10:00:13 PM »
You are welcome  ;)

Beginners & Help / Re: Error 403 (reproduced on 2 separate servers)
« 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:

Beginners & Help / Re: Error 403 (reproduced on 2 separate servers)
« 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.

Beginners & Help / Re: Error 403 (reproduced on 2 separate servers)
« on: June 25, 2020, 02:14:58 AM »

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.

Loading config...
   info  - 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 (/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',
   { body: '[truncated]',
     method: 'POST',
     uri: '',
     headers: { 'content-type': 'text/plain' },
     callback: [Function: RP$callback],
     transform: undefined,
     simple: true,
     resolveWithFullResponse: false,
     transform2xxOnly: false },
   IncomingMessage {

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...).

Technical Support & Development / Re: Max volume to buy
« on: June 24, 2020, 01:50:04 AM »
Those numbers were arbitrary. It can buy 1 time or 10000 times until it blows all your balance.
I would like to suggest to simply implement a Max_Buy_Limit in a future update.

There is a way to limit the amount per trade and the number of traders running TradingView Addon. Good suggestion for standalone bot.

Technical Support & Development / Re: Max volume to buy
« on: June 22, 2020, 03:07:17 AM »
That will set the limit for a single buy.
Some nice strategies allow multiple consecutive buys, when the conditions are met.
Often, there are 4-5 buys before a sell is complete.

But sometimes, usually when the price keeps falling, I can wake up to 20 buys and a huge bag.
Is there some way I can set a hard limit for how much a pair can execute buys?

As per your example,
binance": {
            "USDT-BTC": {
                "strategy": "Base_USDT",
                "enabled": true,
                "override": {
                    "TRADING_LIMIT": 150
SMACROSS will buy 150 USDT in BTC each time. But when done 20 times, that will come up with 3000 invested in 1 trade.
It would be great to be able to set a certain amount, say 1000, that would disable the future buys until the Sell is made.

If it can buy up 20 times and you don't want to use 3000, then what you can do is to lower Trading Limit value. If you put it to 50, it will buy 1000 max if it buys 20 times.

Technical Support & Development / Re: Error on getting market data
« on: June 22, 2020, 03:06:06 AM »
Where do you change the value?

You can find "Period" parameter in the tab "Indicators" in the strategy you are using.

What Gunbot version are you running? Maybe 18.8.8 ?

Technical Support & Development / Re: Max volume to buy
« on: June 19, 2020, 08:25:32 PM »
Is there a way to set the max volume to buy on a pair?

It's tedious to constantly monitor the accumulated amount from multiple buys and manually disable the Buy on that pair when a certain threshold is reached.

You can override Trading_limit parameter for each pair, like this:

"pairs": {
        "binance": {
            "USDT-BTC": {
                "strategy": "Base_USDT",
                "enabled": true,
                "override": {
                    "TRADING_LIMIT": 150
            "USDT-ETH": {
                "strategy": "Base_USDT",
                "enabled": true,
                "override": {        "TRADING_LIMIT": 70
            "USDT-VET": {
                "strategy": "Base_USDT",
                "enabled": true,
                "override": {

It was caused by a problem with license server. It's working fine now.

General Discussion / Re: Gunbot with RT and Trailme
« on: June 16, 2020, 11:06:23 PM »
I have a question about RT.
I can't seem to figure out what the buy sequence is for RT.
Is RT using the buy startegie you set for a specific stategy or is it on it's own?
What I mean is I have tssl for the buy strategy selected and I have RT on.
Also do I have Trailme on for the buy in RT. But now it's like it never is gonna buy?
It already reached the range for the RT_buy and we way past the range for the Trailme range????
Or is the tssl from the buy strategy also working now for this RT and do I now have to add also the range of the tssl strategy to the range of the trailme?

If you want to add trail_me to RT buys, you would need to change "Trail Me RT Buy" placed on RT tab. You can take a look at this explanation on how RT flow works:

  Anyway, personally I prefer DCA than RT and my feeling is that most of the people get better results (and understanding on how it works) with DCA.

Can anyone help me please? ( I usually try and do as much research as I can before posting like this)

I have been running the BTC-alt Autoconfig since the end of April from the marketplace, and has been running full time since then with v18.8.8.  For the past 3 days though, i've been holding some bags, which have already doubled up on the first count with DCA.  I would expect them to DCA again once the RSI & price have dropped sufficiently.  However Buy_Enabled = false keeps getting intermittently enabled for the pairs with 1 DCA (2 is limit)

I have had a look through the log files for both autoconfig and pairs, and it doesn't look like the PND protection conditions are met (<0.4% change in BTC price in last 60 mins), and the PND variable is registered as false.  This looks to be the only autoconfig job that will disable buying for a pair.

Can anyone shed any light on this, or if not give me some further hints to diagnose where I am going wrong please?  I am trying to work out what is stopping it buying.  Only other thing that I can think of is something affecting is with different versions of GB rolled out.  I did try it with the latest beta version tonight, but no success..

Thanks very much!

Please send me a PM with your autoconfig logs attached, so I can search for the "thing" that is triggering buy_enabled parameter to be changed.

From the wiki page (, I understand that a limit buy order can be placed using the syntax:


I assume that would be a maker order on the exchange's books that would fill only when the price drops to the specified rate.

Is it possible for TradingView to issue an alert that cancels that limit order so a new limit buy order can be placed with a different rate?

You can't post a new order that makes the old open order to be cancelled. There are ways to cancel open orders, maybe you can get something similar to what you are looking for:

Did you lose your old Gunbot license? Getting back to Gunbot after some years and don't know how to start again?

Ok, no problem. Send me a PM to me (Aitor) or to Exquitas and we will help you to get your license back  ;)

Aitor profile:;u=1494

Exquitas profile:;u=1659

Beginners & Help / How to recover your old Gunbot license
« on: June 13, 2020, 04:50:03 PM »
Did you lose your old Gunbot license? Getting back to Gunbot after some years and don't know how to start again?

Ok, no problem. Send me a PM to me (Aitor) or to Exquitas and we will help you to get your license back  ;)

Aitor profile:;u=1494

Exquitas profile:;u=1659

Beginners & Help / Re: old licence reactivation
« on: June 09, 2020, 11:27:55 PM »
Send me a PM if you need help on getting your license back.

Pages: [1] 2 3 ... 18