Aperture - AI-Powered Recommendations for Emby

January 10

This is so great. I've been wanting, looking for, trying to code something like this for a long long time and now it's finally here. Thank you so much.

That being said I'm having trouble getting the openai api key to work. I created numerous key 's with all kinds of settings but I keep getting "Connection failed: fetch failed" when I test the connection. I know the key is valid because I tested it on some api key tester site.
The same happens with my OMDB key by the way. Althought that just says "fetch failed" instead of "Connection failed: fetch failed".
The other integrations (emby, trakt, tmdb) are working fine.

Do you have any idea what could be wrong?

January 10

1 hour ago, DaMoekster said:

This is so great. I've been wanting, looking for, trying to code something like this for a long long time and now it's finally here. Thank you so much.

That being said I'm having trouble getting the openai api key to work. I created numerous key 's with all kinds of settings but I keep getting "Connection failed: fetch failed" when I test the connection. I know the key is valid because I tested it on some api key tester site.
The same happens with my OMDB key by the way. Althought that just says "fetch failed" instead of "Connection failed: fetch failed".
The other integrations (emby, trakt, tmdb) are working fine.

Do you have any idea what could be wrong?

Can you try again and send me the browser console logs with any errors? if you are running in docker you can send the docker log from when you attempt to save/test those connections

January 10

1 hour ago, DaMoekster said:

I know the key is valid because I tested it on some api key tester site.

You should also invalidate those keys you shared on a public site, they could very easily be compromised now

January 10

Thanks! I created a couple after that so I'm safe but good to know!

January 10

I am working on an update that will hopefully solve for some initial configuration headaches. Setup is a monster, but once done it just runs.

January 10

50 minutes ago, TheGru said:

Can you try again and send me the browser console logs with any errors? if you are running in docker you can send the docker log from when you attempt to save/test those connections

Okay, so now I"m exposing myself as a noob. Could you explain the log part in docker? I can open a "view details" panel with a lot of info scrolling every second but I'm guiessing that's not what you need.

January 10

no that's probably the log, i have it set to debug so everything is going, see if you can search for errors or anything with omdb or openai in it

January 10

I think I got it. This is the last part of a log I took via "docker logs aperture"

{"level":30,"time":1768061207407,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-cy","req":{"method":"GET","url":"/api/jobs/active","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":55610},"msg":"incoming request"}
{"level":30,"time":1768061207410,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-cy","res":{"statusCode":200},"responseTime":2.028576999902725,"msg":"request completed"}
{"level":30,"time":1768061207797,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-cz","req":{"method":"POST","url":"/api/settings/openai/test","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":53686},"msg":"incoming request"}
{"level":40,"time":1768061207806,"pid":1,"hostname":"fdb72152bc46","name":"aperture","module":"system-settings","err":{"type":"TypeError","message":"fetch failed: connect ECONNREFUSED 127.237.3.40:443","stack":"TypeError: fetch failed\n at node:internal/deps/undici/undici:14900:13\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async testOpenAIConnection (file:///app/packages/core/dist/settings/systemSettings.js:443:26)\n at async Object.<anonymous> (file:///app/apps/api/dist/routes/settings.js:1238:28)\ncaused by: Error: connect ECONNREFUSED 127.237.3.40:443\n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)"},"msg":"OpenAI connection test failed"}
{"level":30,"time":1768061207807,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-cz","res":{"statusCode":200},"responseTime":9.74664800055325,"msg":"request completed"}
{"level":30,"time":1768061209149,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d0","req":{"method":"GET","url":"/api/jobs/active","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":53686},"msg":"incoming request"}
{"level":30,"time":1768061209151,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d0","res":{"statusCode":200},"responseTime":2.003174999728799,"msg":"request completed"}
{"level":30,"time":1768061209404,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d1","req":{"method":"GET","url":"/api/jobs/active","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":55610},"msg":"incoming request"}
{"level":30,"time":1768061209407,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d1","res":{"statusCode":200},"responseTime":2.199591001495719,"msg":"request completed"}
{"level":30,"time":1768061211157,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d2","req":{"method":"GET","url":"/api/jobs/active","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":53686},"msg":"incoming request"}
{"level":30,"time":1768061211159,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-d2","res":{"statusCode":200},"responseTime":2.1573849990963936,"msg":"request completed"}

January 10

3 minutes ago, DaMoekster said:

I think I got it. This is the last part of a log I took via "docker logs aperture"

{"level":30,"time":1768061207797,"pid":1,"hostname":"fdb72152bc46","name":"api","requestId":"req-cz","req":{"method":"POST","url":"/api/settings/openai/test","host":"192.168.3.109:3456","remoteAddress":"172.20.0.1","remotePort":53686},"msg":"incoming request"}
{"level":40,"time":1768061207806,"pid":1,"hostname":"fdb72152bc46","name":"aperture","module":"system-settings","err":{"type":"TypeError","message":"fetch failed: connect ECONNREFUSED 127.237.3.40:443","stack":"TypeError: fetch failed\n at node:internal/deps/undici/undici:14900:13\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async testOpenAIConnection (file:///app/packages/core/dist/settings/systemSettings.js:443:26)\n at async Object.<anonymous> (file:///app/apps/api/dist/routes/settings.js:1238:28)\ncaused by: Error: connect ECONNREFUSED 127.237.3.40:443\n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)"},"msg":"OpenAI connection test failed"}

Looking at this error, the issue is not with the OpenAI key itself - it's a DNS resolution problem.

The Problem

connect ECONNREFUSED 127.237.3.40:443

The OpenAI API endpoint (api.openai.com) is resolving to 127.237.3.40 - a loopback address. This is not a valid IP for OpenAI's servers. OpenAI's API should resolve to actual public IP addresses.

What's Causing This

The IP 127.237.3.40 being in the 127.x.x.x range is a classic sign of DNS-based blocking. Common culprits:

Pi-hole, AdGuard Home, or similar DNS filtering - These tools often redirect "blocked" domains to loopback addresses
Network-level ad/tracker blocking on their router
A corporate firewall or security appliance that's blocking OpenAI
Hosts file entry redirecting api.openai.com

What They Should Check

If they're running Pi-hole/AdGuard/etc.: Whitelist api.openai.com and *.openai.com

Test DNS resolution from inside the Docker container:

docker exec -it <container_name> nslookup api.openai.com

or

docker exec -it <container_name> getent hosts api.openai.com

Check their Docker DNS settings - If Docker is using a custom DNS that's doing the blocking
Check their hosts file (/etc/hosts on Linux/Mac, C:\Windows\System32\drivers\etc\hosts on Windows) for any OpenAI entries
Try from the host machine:
```
nslookup api.openai.com
```
This will show if it's a host-level or container-level DNS issue.

Quick Workaround (if needed)

If they identify it's a Docker DNS issue, they could try adding explicit DNS servers to their docker-compose.yml:

services:
  api:
    dns:
      - 8.8.8.8
      - 1.1.1.1

But ideally they should find and fix the root cause (likely a DNS filter blocking OpenAI).

January 10

Ah okay, thanks. I see I have my work cut out for me.
Thanks for your response!

January 10

you could just apply the DNS workaround in your docker compose yml and compose up:

services:
  api:
  dns:
  - 8.8.8.8
  - 1.1.1.1

January 10

Thanks but I think I found the problem.
I'm running proxifier and even though I configured it for all docker stuff to connect direcly it was the cause of the error. When I removed the rule concerning docker stuff the test connection is working.
Happy days!

Thanks and looking forward to more intensive testing

January 10

26 minutes ago, DaMoekster said:

Thanks but I think I found the problem.
I'm running proxifier and even though I configured it for all docker stuff to connect direcly it was the cause of the error. When I removed the rule concerning docker stuff the test connection is working.
Happy days!

Thanks and looking forward to more intensive testing

Awesome. Big update coming that will help new users get setup and running. If you can be patient it will probably save you a ton of time and headache

January 10

I absolutely can wait, just testing at the moment.

Speaking of testing, creating top picks with strm files works great but creating ai recommendations fails completely for movies and partly for tv.
In the history window it shows Emby api errors 400 bad request.