API Error Radarr / Sonarr works fine about homepage

[benphelps]

If you could provide logs from the browser console and the container console, it would help to narrow down the problem.

[DavidAllmon]

Container Log:
Listening on port 3000
(node:1) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use node --trace-warnings ... to show where the warning was created)
[Error: ENOENT: no such file or directory, open '/app/config/services.yaml'] {
�
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/app/config/services.yaml'
}
[Error: ENOENT: no such file or directory, open '/app/config/services.yaml'] {
�
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/app/config/services.yaml'
}
[Error: ENOENT: no such file or directory, open '/app/config/services.yaml'] {
�
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/app/config/services.yaml'
}
services.yaml was copied to the config folder
bookmarks.yaml was copied to the config folder
widgets.yaml was copied to the config folder
docker.yaml was copied to the config folder
[
500,
Error: read ETIMEDOUT
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'read'
}
]
[
500,
Error: read ETIMEDOUT
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'read'
}
]
[
500,
Error: read ETIMEDOUT
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'read'
}
]

Browser Console:

[mrbagpipe]

I have the same problem. I also captured the Network request that is failing:

As for the container logs, the look the same as @Nomlla's

homepage | Listening on port 3000
homepage | (node:1) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
homepage | (Use `node --trace-warnings ...` to show where the warning was created)
homepage | [Error: ENOENT: no such file or directory, open '/app/config/services.yaml'] {
homepage |   errno: -2,
homepage |   code: 'ENOENT',
homepage |   syscall: 'open',
homepage |   path: '/app/config/services.yaml'
homepage | }

I also tried using the IP address to no avail

[DavidAllmon]

I have the same problem. I also captured the Network request that is failing:

As for the container logs, the look the same as @Nomlla's

homepage | Listening on port 3000

homepage | (node:1) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time

homepage | (Use `node --trace-warnings ...` to show where the warning was created)

homepage | [Error: ENOENT: no such file or directory, open '/app/config/services.yaml'] {

homepage |   errno: -2,

homepage |   code: 'ENOENT',

homepage |   syscall: 'open',

homepage |   path: '/app/config/services.yaml'

homepage | }

I also tried using the IP address to no avail

I believe the latest update fixed this issue. I'm only saying that because this issue was fixed after last update.

[benphelps]

Yeah, the latest update fixed some cases where loading would fail due to some specific configuration cases.

The 404 is fine, it's just part the i18n support looking for a more specific language than en, but we're sharing the same one for en-US and en-GB.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.