Samuryno 1 Posted February 4 Share Posted February 4 (edited) I already have Jellyfin installed on port 8096, so I installed Emby on port 8090 in Portainer. When I go to local:8090 I get "This site can't be reached." I've opened 8090 on UFW. It's set to Host, but I've also tried Bridge and portainer_default without success What am I doing wrong? Edited February 4 by Samuryno added pics Link to comment Share on other sites More sharing options...
Q-Droid 671 Posted February 4 Share Posted February 4 Your port mapping likely needs to be 8090:8096 as the Emby server is probably still listening on the default port. If you really want the ports to match it can be changed after you connect to Emby, in the Network settings then redo the container back to 8090:8090. Link to comment Share on other sites More sharing options...
Samuryno 1 Posted February 6 Author Share Posted February 6 That fixed it. Thank you so much. Link to comment Share on other sites More sharing options...
Samuryno 1 Posted February 6 Author Share Posted February 6 Nevermind. I restarted the container after changing the port in Emby, like it said, and now it does not work again. Link to comment Share on other sites More sharing options...
Luke 37295 Posted February 6 Share Posted February 6 3 minutes ago, Samuryno said: Nevermind. I restarted the container after changing the port in Emby, like it said, and now it does not work again. What exactly happens? Link to comment Share on other sites More sharing options...
Samuryno 1 Posted February 6 Author Share Posted February 6 The same "This site can't be reached." I even tried removing Emby and reinstalling it, but the same error occurs. I stopped Jellyfin and used only port 8096 and it still does not work. Link to comment Share on other sites More sharing options...
Luke 37295 Posted February 6 Share Posted February 6 1 minute ago, Samuryno said: The same "This site can't be reached." I even tried removing Emby and reinstalling it, but the same error occurs. I stopped Jellyfin and used only port 8096 and it still does not work. is any emby server log generated? Emby Server Data Folder Link to comment Share on other sites More sharing options...
Q-Droid 671 Posted February 6 Share Posted February 6 8 hours ago, Samuryno said: Nevermind. I restarted the container after changing the port in Emby, like it said, and now it does not work again. You need to recreate the container, not restart it. If you change the port on the Emby side the container is still mapped 8090:8096 and to change that it has to be recreated with the new mapping. 1 Link to comment Share on other sites More sharing options...
Luke 37295 Posted February 6 Share Posted February 6 @Samurynoplease let us know if this helps. Thanks. Link to comment Share on other sites More sharing options...
Samuryno 1 Posted February 7 Author Share Posted February 7 I restarted it, I redeployed it with altered ports, and nothing worked. I finally took a cue from my format c colon days and nuked the whole Emby directory, then redeployed it so I could set it all up again, and that worked. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now