Nextcloud API ERROR INFORMATION

[adbr1]

Description

Hello, I have some trouble with the Nextcloud integration, specifically with the API key. I've tried various solutions, but unfortunately none of them work for me. I attempted direct connection using the user and password, without success. I also tried using an "app password", which also did not work. I even tried a command in the Nextcloud jail on TrueNAS, but encountered issues.

homepage version

v0.9.2

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

To address the issue with the Nextcloud integration, let's go through a few troubleshooting steps based on the documentation and context provided:

1. Ensure Correct API Key Usage: According to the documentation, you can use either a username and password or an NC-Token for authentication. If you're using an NC-Token, make sure it's obtained correctly. The token can be found under Settings > System in Nextcloud. If you're using an app password, ensure it's generated correctly within Nextcloud's security settings.

2. Correct Configuration Syntax: Verify that your configuration syntax matches the examples provided in the documentation. Here's an example of how it should look:

   widget:
     type: nextcloud
     url: https://nextcloud.host.or.ip:port
     key: YOUR_NC_TOKEN

   Or, if using username and password:

   widget:
     type: nextcloud
     url: https://nextcloud.host.or.ip:port
     username: your_username
     password: your_password

3. No Trailing Slash: Ensure that the URL in your configuration does not end with a trailing slash, as mentioned in the troubleshooting guide.

4. Network Connectivity: Verify that the homepage installation can connect to the Nextcloud instance. You can do this by executing a ping from within the Docker container to the Nextcloud host.

5. Use curl to Test API: You can test the API output directly using curl from within the Docker container. This can help determine if there's an issue with the API itself or the way it's being accessed.

6. Check Container Logs: If you're still encountering issues, check the container logs for any error messages that could provide more insight into the problem.

7. Update to Latest Version: Ensure that you are running the latest version of the homepage, as there may have been fixes or improvements related to service widgets.

If you've gone through these steps and are still facing issues, please provide more specific details about the errors you're encountering, including any relevant logs or error messages. This will help in diagnosing the problem more accurately.

This comment was generated by Glime.

[adbr1]

Ok so in fact it was because i had to put https:// in front of the ip and i didn't notice that

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.