Synology service (same host homepage is running on) is having issues (2FA)

[begunfx]

Description

I have three synology servers. I tried to set all three up as services on homepage. All three of them have users that only have access to the DSM and 2FA authentication is turned off. Two of them are working without issue. However, the one server (datavault) that is hosting the homepage container is not. When I first create the user and add the service it connects without issue and displays stats as expected. After about 15 minutes I get an API error. When I look at the logs I get the following error:

[2024-06-08T01:01:43.153Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System.Utilization&version=1&method=get. code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:16:31.510Z] warn: Unable to login. Code: 407
[2024-06-08T04:16:31.511Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System&version=3&method=info. code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:16:31.588Z] warn: Unable to login. Code: 407
[2024-06-08T04:16:31.589Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System&version=3&method=info&type="storage". code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:16:31.743Z] warn: Unable to login. Code: 407
[2024-06-08T04:16:31.744Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System.Utilization&version=1&method=get. code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:25:38.518Z] warn: Unable to login. Code: 407
[2024-06-08T04:25:38.519Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System&version=3&method=info&type="storage". code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:25:38.571Z] warn: Unable to login. Code: 407
[2024-06-08T04:25:38.572Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System.Utilization&version=1&method=get. code: 407, error: Authentication failed. 2FA enabled..
[2024-06-08T04:25:38.573Z] warn: Unable to login. Code: 407
[2024-06-08T04:25:38.573Z] warn: Unable to call https://datavault/webapi/entry.cgi?api=SYNO.Core.System&version=3&method=info. code: 407, error: Authentication failed. 2FA enabled..

Here's the services.yaml for my servers:
`

• Servers:

  • MediaVault:
    icon: synology.svg
    href: https://mediavault.mydomain.com
    widget:
    type: diskstation
    url: https://mediavault
    username: xxxxx
    password: xxxxx
    volume: volume_1 # optional

  • DataVault:
    icon: synology.svg
    href: https://datavault.mydomain.com
    widget:
    type: diskstation
    url: https://datavault
    username: xxxxxx
    password: xxxxxx
    volume: volume_1 # optional

  • TMVault:
    icon: synology.svg
    href: https://tmvault.mydomain.com
    widget:
    type: diskstation
    url: https://tmvault
    username: xxxxx
    password: xxxxxx
    volume: volume_1 # optional`

I can confirm without a doubt that 2FA is disabled for that user. I tried disabling 2FA for all users, shortening the password, removing special characters. I also tried changing the URL to: HTTP://localhost/ and HTTP://127.0.0.1/. I also tried both HTTP and HTTPS. I also tried restarting the container and re-deploying the stack.

Again, just to be clear, when I first add the DSM only user it works for about 15 minutes, then after that I get the errors and cannot get it to work again.

Any ideas would be greatly appreciated.

homepage version

v0.9.2

Installation method

Docker

Configuration

version: "3.9"
services:
  homepage:
    container_name: homepage
    image: ghcr.io/gethomepage/homepage:latest
    mem_limit: 4g
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped
    ports:
      - 3550:3000
    volumes:
      - /volume1/docker/homepage:/app/config:rw
      - /volume1/docker/homepage/public:/app/public/images:rw
      - /volume1/docker/homepage/public/icons:/app/public/icons:rw
      - /var/run/docker.sock:/var/run/docker.sock

Container Logs

No response

Browser Logs

No response

Troubleshooting

See above.

[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! ❤️

---

Based on the error logs you've provided, it seems that the Synology DiskStation is reporting an authentication failure due to 2FA being enabled, despite your confirmation that 2FA is disabled for the user. This is quite unusual, especially since the other two Synology servers are working fine with a similar setup.

Here are a few troubleshooting steps you can take:

1. Double-check 2FA Settings: Even though you've confirmed that 2FA is disabled, it's worth double-checking the settings for the specific user on the DataVault Synology DSM to ensure that 2FA is indeed turned off.

2. Session Timeout: It's possible that the session is timing out or getting invalidated after 15 minutes. Check if there are any session timeout settings on the Synology DSM that might be affecting the connection.

3. Permissions: Verify that the user has the correct permissions set up, similar to the other two Synology servers that are working. Ensure that the user is part of the Administrators group and has the necessary permissions to access the required APIs.

4. API and DSM Version: Ensure that the API and DSM versions are compatible with the homepage widget. If there was a recent DSM update on the DataVault, it might have affected the API compatibility.

5. Network Settings: Since the DataVault is hosting the homepage container, check if there are any network settings or firewall rules that might be blocking the connection after a certain period.

6. Logs and Debugging: Increase the log level to debug to get more detailed logs that might help identify the issue. You can do this by setting the LOG_LEVEL environment variable to debug in your Docker configuration.

7. Restart Synology DSM: Sometimes, simply restarting the Synology DSM can resolve transient issues that might be causing authentication problems.

8. Homepage Updates: Make sure that your homepage installation is up to date. Check for any updates or patches that might address this issue.

9. Support Channels: If the issue persists, consider reaching out to the homepage support channels such as the #ai-support channel on Discord or opening a GitHub discussion for more specialized assistance.

10. Recreate the User: As a last resort, try deleting the user on the DataVault DSM and recreating it from scratch, ensuring all the settings are correctly configured.

If none of these steps resolve the issue, it may be necessary to file a bug report with the homepage developers, providing all the relevant logs and configuration details.

This comment was generated by Glime.

[begunfx]

Okay. I went through all the suggested steps by Glime.

1. Confirmed: 2FA is not enabled for this user
2. Session timeout is not an issue. Settings are also identical between all 3 of my Synology servers
3. Permissions are the same between all 3 servers
4. DSM version is the same between servers
5. No firewall is configured on the Datavault server itself and the firewall on my router doesn't distinguish the servers any different from each other when it comes to rules
6. I tried increasing the LOG_LEVEL=debug in the docker container but I don't seem to see a change in the level of the logs. Not sure what's going on with that?
7. I restarted my datavault server - no change
8. Homepage is the latest version

I did find one strange thing. For the hell of it I set the permissions to allow access to all applications for this homepage user. Suddenly my datavault homepage widget started working. Then I set everything back to deny except for DSM (like before) and it continues to work. Not sure what that is all about...but so far it seems to be working. Will update this thread if something changes.

[jdevera]

I had a similar issue and was also seeing the 2FA log messages while my user did not have 2FA enabled.

The key in my case was in this paragraph of the docs for this widget:

If you encounter issues during testing:
Make sure to uncheck the option for automatic blocking due to invalid logins under Control Panel > Security > Protection.

When I disabled that setting, the widget started working.

Sadly whenever I tried to turn it back on it started failing again. But it's something.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.