-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several error #1
Comments
Does it work if you use the same address as the one you're using when using the web frontend?
That requires webhooks, which are also available in unstable only at this point.
I noticed that as well, don't know why it does that. If you have any ideas, please share.
Can you explain that? I don't think I understood you correctly here. |
Nope, but I triggered the webhook in browser and I got the following error: 'The requested webhook "GET faba251d-2f0c-49de-8a01-202582a7fbfe/webhook" is not registered.' Any other webhook gets registered except this one. "This webhook is not registered for GET requests. Did you mean to make a POST request?"
I'm not really into n8n custom nodes.
So for example I make a request for Get Many Tasks. I've got two options (By ID, By List). It's works only with ID, because
|
Sounds like a n8n error to me 🤔
I mean the Vikunja URL.
Gotcha. Sounds like you can't make any requests though. Which Vikunja version are you using? Does it work with try? Which n8n version are you using? |
Maybe. But seems like the n8n webhook is a GET one while the Vikunja uses a POST one and usually all the webhook is POST.
Yep I can't get the list, but I can manually add ID and works. Latest unstable Vikunja version and n8n 1.15.2. I never tried the main version. Unfortunately I use NPM as proxy so these problems could be unique and cannot be reproduced with the main one, anyway I will give a try later.
|
I've just tried the webhook node with try and it seems to work just fine. Seems like the problem is somewhere in your installation :/ |
I've tested with multiple docker selfhosted services and none of my incoming webhook works so that's not an issue here anymore. I ran into some kinda Nginx error. Also painful that I cannot use proxied domain only my internal docker addresses. Whenever I finish my investigation I will return to fully test this awesome node. |
Which nginx error?
You should be able to use your proxied domain (that's what I do). |
My n8n cannot get webhooks from my selfhosted services such as Baserow, Vikunja, etc. The outgoing traffic seems to be great, I can get data from these services. The basic Webhook node works well and same for the Google Services like Sheets Trigger. Whenever I tried to use a proxied domain I've got "ETIMEOUT: my external ip:443", same for the HTTP Request except I can add proxy and can get result. |
Unfortunately I always get a 401 message with GET MANY Tasks, but I have no problems with GET TASK. I have already tried to use the API of https://try.vikunja.io/, but I get the same error message. Can anyone help me with this? If further information is needed, please let me know. |
Does the api token you're using have the permission to get many tasks? |
@GinoTonello Anything in Vikunja's logs? |
experienced the same thing. any update to the community nodes? |
Is this still a problem with the latest release or the last unstable build? |
0.22.0 build. API token issue most likely as login jwt token able to work. |
So the problem remaining is basically go-vikunja/vikunja#105? |
yes. basically api token not authorized to get project tasks and many more, even though it's enabled during token creation. |
Well I still cannot get the full list, but resolved my internal dns issue a while ago. I've got an idea that a function would be nice which gets all the overdue and upcoming tasks. That's probably an easy upgrade due the overdue tasks already collected and coming via email and the upcoming task also sorted in a dedicated menu item. What do you think about it? :) |
That's a filter on the "get all tasks" endpoint, which means it should be possible with the current node already. The API request from the frontend is this one: And for upcoming: |
Once the new filter syntax is released, this will be added to the n8n node. |
Hello again! I'm experiencing a similar issue as @GinoTonello . When I make "Get" and "Get Many" requests, there are usually no problems. Also, when I target directly by ID, it works fine. However, the problem arises when I try to get information through the "From List" selection. I receive the following error: My API token has full permissions. I'm using Vikunja version 0.23 and n8n versions 1.41 and 1.42. Additionally, I have just updated to the latest version of the Vikunja community node. Is there a solution for this? As mentioned, targeting directly by ID works without any issue. |
@Niskeletor do you see any errors in Vikunja's API logs? |
Sorry for my late reply. As you can see, if I select "From List," I can't get the list of available projects to select. But if I choose the ID, the API can give me a response. What I'm trying to say is that in n8n, with the Vikuja plugin, if I choose the "From List" option, it doesn't show any projects; the list appears empty. However, if I select by ID, it does return information. |
@Niskeletor you need to select a project from the list if you set the drop-down to "from list". |
Yep, thats the point , when I try to select one of them returns an empy list, with the msg error below : |
Does the Vikunja API token has permission to read all projects? Do you see any errors in Vikunja's logs? |
Closing as inactive, please ping or open a new issue with relevant information if you still have this problem. |
Hello!
I really like Vikunja and I was so happy that it finally got an n8n support, but unfortunately I ran into several problems:
NodeApiError: UNKNOWN ERROR - check the detailed error for more information
TypeError: Cannot read properties of undefined (reading 'getCredentials')
I run Vikunja behind Nginx Proxy Manager, so i use internal docker address as API, may that why it's faulty. (http://vikunja-api:3456/api/v1)
A button for selecting all of the permission would be nice at API token page.
Anyway, great work! I'm so excited about the possibilities what it gonna unlock.
Regards
The text was updated successfully, but these errors were encountered: