-
Notifications
You must be signed in to change notification settings - Fork 0
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
Vikunja test connection failed #16
Comments
hey, Please confirm: Your vikunja instance is running at root-level? So something like https://vikunja.your-domain.tld (e.g. like the demo instance https://try.vikunja.io) opens up your instance? No trailing slash or sth. If this is not the case, we need to investigate further. Also confirm this: If you add |
My apologies Appending /api/v1 returns steps taken |
Mh. Weird. The api is returning the correct output. From your post, i cannot see any errors. Okay, we need to go deeper... Please create a new vault in obsidian and install vikunja plugin from community hub, again. Then we can be sure, it is the plugin and nothing else is blocking. Setup your instance in vikunja plugin settings page (do not enable something else). Please enable the debugging, too. Then press f12 to open up the developer tools in obsidian... Obsidian is a javascript app, so it is something like a browser. ;) In the new opening frame, you will find a tab named "Console". Open this up, you will see some stuff is going on there. |
Though the output is less than ideal, I appreciate your time and attention, plus it's extra incentive to start my deeper understanding of web technologies All of these messages are listed without my instance
The next set of errors replaces the "Failed to load resource: from try/api/v1/labels:1" entry with my instance |
Nope, it does not help. It seems, that you do not have entered a valid instance, because the error messages coming from deleting one character with backspace in the input field. Please enter your domain in the input field, regardless if there are error messages in log and click on test and post the error log here. If there is your domain in output, which you do not want to publish, delete it manually. |
I believe this is what you're looking for |
My instance is sitting behind NGINX Proxy manager if that helps at all |
Ah now we are getting closer. In a next version, i will try to catch this error and show a notification to mention this. |
Bingo! |
No problem. |
First, thank you for this integration, I appreciate your time, expertise and generous contribution to Obsidian. Unfortunately, my developer skills are underwhelming and I'm having a difficult time with configuring your plugin.
Steps taken:
Downloaded and installed the obsidian-vikunja-plugin along with its prerequisite plugins
Generated an API token (full access) from my Vikunja account v0.24.1
In the test connection fields of the plugin I added my url (hhtps) and the generated API key
I'm receiving a "Connection Failed" message upon submission
Searched your issues page and Obsidian forums to see if someone else has run into the same issue, to no avail
This is where my developer skills are lacking, I don't know where to find the logs to see examine the error or next steps to resolve it. I would really appreciate any help, hints or pointers in the right direction
Thank you in advance!
The text was updated successfully, but these errors were encountered: