Baserow and N8N api errors via self host and official hosting

Technical Help
, ,
1

Self-Hosted Installation and Setup Questions

How have you self-hosted Baserow.

I’m using container manager on custom Synology nas.

What are the specs of the service or server you are using to host Baserow.

i7 7700K, 32GB RAM, NVME SSD for containers and everything neccessary

Which version of Baserow are you using.

1.22.2/Latest

How have you configured your self-hosted installation?

https://imgur.com/a/mos4dHM

Describe the problem

Describe, step by step, how to reproduce the error or problem you are encountering.

  1. Connecting to my baserow server via public url gives api error messages. So does the baserow hosted version. Error messages are the same “ERROR_INVALID_CREDENTIALS”
  2. Supabase/Discord triggers/webhooks are all working. Just not baserow.

Provide screenshots or include share links showing:

up

How many rows in total do you have in your Baserow tables?

5

Please attach full logs from all of Baserow’s services

up

Self Hosters Only
up

2

@joffcom maybe you have some ideas on how this can be fixed? :pray:

3

Sorry for the delay…

@ihoststuff it looks like a normal authentication failure, Are you using the password for your user or an api token?

4

Thanks for the reply! I’m using freshly generated api token.

5

oh wow i didn’t even think to try my user password…

Anyways it works now. What’s interesting is that api token still wont work, but it did while i self hosted on unraid system.

If you have the time to figure out why that is i would love to know. If not i’m happy you replied and gave me the idea to just try my plain user password.

1 Like
6

Sorry for the delay, we don’t support the api token in n8n at the moment. At some point I should probably overhaul the node to add some of our new features and support the other authentication options.