search

jorenn92 / Maintainerr

Looks and smells like Overseerr, does the opposite. Maintenance tool for the Plex ecosystem
https://maintainerr.info
MIT License
849 stars 17 forks source link

Adding Overseerr connection; hostname doesn't work #1292

Closed SawkeeReemo closed 1 month ago

SawkeeReemo commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

Yup. All good. Thanks!