Adding Overseerr connection; hostname doesn't work

[SawkeeReemo]

trafficstars

When adding a connection to Overseerr, using the hostname (i.e. localhost) doesn't work. It adds http:// to the name in the text box, which normally wouldn't be a problem, but might be a problem here. When I change to IP address, it works fine.

[benscobie]

Do you mean that the test fails? Are you able to run an nslookup from the container to see if DNS resolution is okay? docker exec -it container_name sh -c "nslookup hostname_replace_me"

[SawkeeReemo]

Ran that command for both localhost and the hostname for my overseerr. Both worked.

But in the UI config for Maintainerr, if I use either hostname, it adds http://[hostname]/ to the entry. Then localhost does not work, but the hostname for my Overseerr container does. Both are on the same docker network as well.

And as I’m typing this, I think I just answered my own question and things are working as they should. 🤦‍♂️ 😂

[ydkmlt84]

Ran that command for both localhost and the hostname for my overseerr. Both worked.

But in the UI config for Maintainerr, if I use either hostname, it adds http://[hostname]/ to the entry. Then localhost does not work, but the hostname for my Overseerr container does. Both are on the same docker network as well.

And as I’m typing this, I think I just answered my own question and things are working as they should. 🤦‍♂️ 😂

So you are good to go now and this can be closed?

[SawkeeReemo]

Yup. All good. Thanks!