Unable to setup on Synology / Docker

[timothe]

Describe the bug
I wanted to give Maintainerr a try by setting it up on my Synology under DSM 7.2.1.
I can reach the portal however I see a redirect loop from the plex settings and only the sidebar is loading.

To Reproduce
Steps to reproduce the behavior:

1. Deploy the container
2. Navigate to http://[nasip]:6246/
3. I get redirected to http://[nasip]:6246/settings/plex

Expected behavior
I should be able to see and edit the settings to run the program.

Logs
Here's what I see in the logs:

...
[maintainerr] | 10/02/2024 18:12:34  [INFO] [RouterExplorer] Mapped {/api/collections/exclusions/:id/content/:page, GET} route
[maintainerr] | 10/02/2024 18:12:34  [INFO] [RouterExplorer] Mapped {/api/collections/logs/:id/content/:page, GET} route
[maintainerr] | 10/02/2024 18:12:34  [INFO] [SettingsService] Settings not found.. Creating initial settings
[maintainerr] | 10/02/2024 18:12:36  [INFO] [PlexApiService] Plex API isn't fully initialized, required settings aren't set
[maintainerr] | 10/02/2024 18:12:36  [WARN] [TasksService] An error occurred while creating the Collection Handler task. This is normal on first boot.
[maintainerr] | 10/02/2024 18:12:36  [INFO] [CollectionWorkerService] Creation of Collection Handler task failed. Retrying in 10s..
[maintainerr] | 10/02/2024 18:12:36  [INFO] [TasksService] Task Collection Log Cleaner created successfully
[maintainerr] | 10/02/2024 18:12:36  [WARN] [TasksService] An error occurred while creating the Rule Handler task. This is normal on first boot.
[maintainerr] | 10/02/2024 18:12:36  [INFO] [RuleExecutorService] Creation of Rule Handler task failed. Retrying in 10s..
[maintainerr] | 10/02/2024 18:12:36  [INFO] [TasksService] Task Rule Maintenance created successfully
[maintainerr] | 10/02/2024 18:12:36  [INFO] [NestApplication] Nest application successfully started
[maintainerr] | 10/02/2024 18:12:41  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
[maintainerr] | 10/02/2024 18:12:46  [INFO] [TasksService] Task Collection Handler created successfully
[maintainerr] | 10/02/2024 18:12:46  [INFO] [TasksService] Task Rule Handler created successfully
[maintainerr] | 10/02/2024 18:13:02  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
[maintainerr] | 10/02/2024 18:13:52  [WARN] [AppService] Couldn't fetch latest release version from GitHub
[maintainerr] | 10/02/2024 18:13:52  [WARN] [AppService] Couldn't fetch latest release version from GitHub
[maintainerr] | 10/02/2024 18:13:52  [WARN] [AppService] Couldn't fetch latest release version from GitHub
[maintainerr] | 10/02/2024 18:13:52  [WARN] [AppService] Couldn't fetch latest release version from GitHub
[maintainerr] | 10/02/2024 18:13:52  [WARN] [AppService] Couldn't fetch latest release version from GitHub
...

Screenshot

Device (please complete the following information):

• OS: Synology / DSM 7.2.1
• Version: ghcr.io/jorenn92/maintainerr:latest

Additional context
I tried:

• Changing network to bridge / host
• Deploying via docker compose / Portainer / DSM Container Manager

There's a user issue if I don't set the UID:GID up ("PLEASE UPDATE YOUR CONFIG..." message).
The WARN message only arises when I go to the website and get the infinite redirect behaviour.

[jorenn92]

Duplicate of #887

I'm not sure why this is happening, since nothing regarding the version changed. I'll look into it as soon as possible.
For now, using tag 2.0.0 should resolve it.

[jorenn92]

Pushed a fixed and performed an emergency release. It should work with 2.0.2

[timothe]

What a quick turnaround! Thank you!

However I have another issue now. I re-created the container on the bridge network, which allowed me to connect to Plex without issue via localhost. However I can't connect to the other -arr instances. They run on Docker on the host network, and communicate perfectly between each other via localhost.

When on bridge network, I tried switching the url to:

• localhost
• [ip of the nas]
• host.docker.internal

Nothing worked. It doesn't connect.

So I switched the network from bridge to host for Maintainerr, but I can't get it to run. When I start it on host, I get this message in a loop:

 ⨯ Failed to start server
Error: getaddrinfo ENOTFOUND maintainerr
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'maintainerr'
}

I also tried to not define / define the hostname to different values, nothing fixed it.

Any idea?

[timothe]

Actually, Plex' connection seemed to work before, but not anymore. Only authentication works.

[jorenn92]

What a quick turnaround! Thank you!

However I have another issue now. I re-created the container on the bridge network, which allowed me to connect to Plex without issue via localhost. However I can't connect to the other -arr instances. They run on Docker on the host network, and communicate perfectly between each other via localhost.

When on bridge network, I tried switching the url to:

* localhost

* [ip of the nas]

* host.docker.internal

Nothing worked. It doesn't connect.

So I switched the network from bridge to host for Maintainerr, but I can't get it to run. When I start it on host, I get this message in a loop:

 ⨯ Failed to start server
Error: getaddrinfo ENOTFOUND maintainerr
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'maintainerr'
}

I also tried to not define / define the hostname to different values, nothing fixed it.

Any idea?

This seems like a general Nodejs error (nodejs/node#44003 (comment)). I don't really know what's going on..

But, try to revert to the working config and prepend your hostname configurations with http(s)://. Also, make sure you're only using base_url when absolutely sure you need it.

The backend should automatically add http(s):// when it's not there, but i've had some recent reports that indicate it doesn't do that anymore..

[jorenn92]

Actually, Plex' connection seemed to work before, but not anymore. Only authentication works.

You can't communicate with Plex anymore? Was this because you changed the mode?

[timothe]

Ok it gets weirder.

I'm running on the bridge network.

Re: Plex, authentication is done so it gets me a list of servers to connect to when I click the 🔁 button. I have only one server but I get 2 pairs of config, either hostname or IP, local or remote. So my list is:

• manual config
• hostname - local
• hostname - remote
• ip - local
• ip - remote
  However, no matter what choice I make, it doesn't reach Plex: Connection failed! Please check and save your settings

It's weird because I run 15 containers daily alongside a VM and other apps on this NAS. Some are exposed on the local network, others on the internet, or some are not. But it's the first time I have this issue.

Usually I solve this by using the host network, but with this config, I get the network error I mentioned before and the app is not running.

I tried this:

• Using bridge, I removed all files in data to try a new setup. Once authenticated with Plex, I go back to the same issue described above, with: - Local: http://maintainerr:6246 [maintainerr] | 11/02/2024 18:21:41 [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
• I recreated the container using host, again with a clean slate, and got it again with:

Error: getaddrinfo ENOTFOUND maintainerr
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'maintainerr'
}

• So I looked online to check similar issues with node & Docker, which make me came back to your point about urls
• I came back and tried putting http://[local nas ip] for every service and... it WORKED!

I know it's quite explicit as it's marked Test Saved but the test only works AFTER you click save and it feels weird.

Thank you for your app and support, super duper appreciated! 🙏
I'm running to try it out now 🏃

[MichaelGoedken]

Exact same issue is happening with me except I cannot get it to work at all on bridge mode.