gwilikers@lemmy.ml to Linux@lemmy.ml · 1 day agoYour Most Frustrating Configuration Experience?message-squaremessage-square86fedilinkarrow-up153arrow-down10file-text
arrow-up153arrow-down1message-squareYour Most Frustrating Configuration Experience?gwilikers@lemmy.ml to Linux@lemmy.ml · 1 day agomessage-square86fedilinkfile-text
minus-squareTeryVeneno@lemmy.mllinkfedilinkarrow-up1·edit-24 hours agoI think this means it can’t actually see your jellyfin instance, you need to use your computer’s local network ip instead of localhost if the two containers aren’t in the same pod via a docket compose file. I’ve had this issue before.
minus-squareaStonedSanta@lemm.eelinkfedilinkarrow-up1·3 hours agoNah. It’s on the same docker compose file through portainer. And I’ve been using the local ip. I never use local host for some reason lol
I think this means it can’t actually see your jellyfin instance, you need to use your computer’s local network ip instead of localhost if the two containers aren’t in the same pod via a docket compose file. I’ve had this issue before.
Nah. It’s on the same docker compose file through portainer. And I’ve been using the local ip. I never use local host for some reason lol