Wekan Error: undefined

Questions
1

Hi

I’m running n8n and wekan locally using docker images. I’ve created Wekan credentials in n8n pointing to my local instance:

Screenshot 2021-06-16 at 17.30.39
Screenshot 2021-06-16 at 17.30.392654×1348 179 KB

But I’m getting this error when I try run a simple GET node:

Wekan Error: undefined
at Object.getAuthorization (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Wekan/GenericFunctions.js:23:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Object.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Wekan/GenericFunctions.js:33:23)
at async Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Wekan/Wekan.node.js:434:32)
at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:395:47

In Wekan, my user has admin access.

One thing I have noted, is that the n8n credentials screen never shows the “Access > Wekan” as checked when I load it. Perhaps the access permissions aren’t being saved?

Other than that, I couldn’t find much here or elsewhere on the error…

2

Remove the last / in the url and try again.

3

Same result I’m afraid…

4

It works fine for me. It has to be something with your deployment. For testing, I used the docker-compose below.

image
image2988×1198 164 KB 

wekan:
  image: quay.io/wekan/wekan
  links:
    - wekandb
  environment:
    - MONGO_URL=mongodb://wekandb/wekan
    - ROOT_URL=http://localhost
  ports:
    - 8081:8080

wekandb:
   image: mongo:3.2.21
   volumes:
     - ~/wekan/data:/data/db
5

Good to know. I’m a complete novice, so mostly likely am missing something. Thanks for taking the time to help!

6

Hey @theneilkirk!

Are you able to access Wekan via the browser? It might be possible that the port is not accessible outside of Docker and the reason you get the error.

7

Hey. Yes, I was able to log in and set up the board that I was trying to access. In fact, using the user credentials, n8n was able to fetch the name of the board. But running the workflow failed to get the board details.