JMO Posted February 17, 2015 Share Posted February 17, 2015 Hi, I have been busy setting up my first UnRaid box over the past few days, and have encountered an issue with CouchPotato. For whatever reason, I cannot get the CP WebUI to load. Here's a screen of my settings: The funny thing is, it was working, then by means of whatever I changed, it stopped. All I get at: http://192.168.1.250:8082/ is "This webpage is not available". Suggestions are very welcome. Quote Link to comment
Squid Posted February 17, 2015 Share Posted February 17, 2015 Is 192.168.1.250 the IP address of your server? Quote Link to comment
JMO Posted February 17, 2015 Author Share Posted February 17, 2015 Is 192.168.1.250 the IP address of your server? Yes. e.g. http://192.168.1.250/Docker Quote Link to comment
Squid Posted February 17, 2015 Share Posted February 17, 2015 What does the CP logs show? (Click on the uptime to bring it up) Quote Link to comment
JMO Posted February 17, 2015 Author Share Posted February 17, 2015 EDIT: I deleted the docker, and re-installed, all seems well again. Here's the up-time report: root@localhost:# /usr/bin/docker logs --tail=350 CouchPotato *** Running /etc/my_init.d/edge.sh... Downloading source... Cloning into '/tmp/tmp.13549920915364680'... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 24 The command finished successfully! I also have port forwarding configured on my router. 8082-->192.168.1.250 EDIT: And from the CP config file: ssl_key = ssl_cert = data_dir = permission_folder = 0755 development = 0 url_base = debug = 0 launch_browser = 0 port = 8082 permission_file = 0644 show_wizard = 0 Quote Link to comment
Darqfallen Posted February 17, 2015 Share Posted February 17, 2015 You don't need port forwarding and change the container port from 5050 to 8082 and it should be fine. The port forwarding is for outside your network, so unless you want to access your Couchpotato from the internet I wouldn't set the port forwarding until I have set a strong password / https. Quote Link to comment
JMO Posted February 18, 2015 Author Share Posted February 18, 2015 You don't need port forwarding and change the container port from 5050 to 8082 and it should be fine. Forwarding is off atm. I have some weird behaviour in CP though. If I have the following settings: WebUI: http://192.168.1.250:8082/ Container port: 8082 Host Port: 8082 Then CP tries to open the WebUI at: http://192.168.1.250:5050/ Which is the wrong port and gives me a webpage not available. Manually changing the port to 8082 in the browser loads the page fine. Alternatively, if I use (note the changed container port): WebUI: http://192.168.1.250:8082/ Container port: 5050 Host Port: 8082 CP tries to load at http://192.168.1.250:8082/ Which is the correct port, but gives me a webpage unavailable. Not a big deal to edit the port number in the browser/bookmark, and I doubt I will be launching CP directly from the Docker page very often (once I am fully up and going), but still, not exactly what i would call expected behaviour. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.