mediabox: error on install. several containers not loading
Hey thanks for making this project, its brilliant!
First of all received this problem: https://github.com/tom472/mediabox/issues/71 where the script just gets stuck indefinitely.
Rebooted, didn’t help.
Tested again after another reboot, this time filing in all options rather than leaving some blank and it worked. I think the problem is caused if you do not enter an option for some of the questions in the script.
But sadly the script still didn’t work for me, at the end I received this error:
sed: /usr/bin/healthcheck.sh: No such file or directory chmod: cannot access 'content/': No such file or directory Setup Complete - Open a browser and go to:
And I tried launching different apps within mediabox like plex and jellyfin and they don’t open.
My .env: LOCALUSER=tim HOSTNAME=basement IP_ADDRESS=192.168.50.149 PUID=1000 PGID=1000 DOCKERGRP=999 PWD=/home/tim/mediabox DLDIR=/mnt/data/downloads TVDIR=/mnt/data/media/tv MOVIEDIR=/mnt/data/media/movies MUSICDIR=/mnt/data/media/music PIAUNAME=tim PIAPASS=fake CIDR_ADDRESS=192.168.50.0/24 TZ=Etc/UTC PMSTAG=public PMSTOKEN= PORTAINERSTYLE=–no-auth VPN_REMOTE=ca.privateinternetaccess.com CPDAEMONUN= CPDAEMONPASS=tim NZBGETUN= NZBGETPASS=tim
Heres docker status: tim@basement:~/mediabox$ docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2f5e361302a2 binhex/arch-delugevpn “/usr/bin/tini – /b…” About an hour ago Up 11 minutes 192.168.50.149:8112->8112/tcp, 192.168.50.149:8118->8118/tcp, 192.168.50.149:58846->58846/tcp, 192.168.50.149:58946->58946/tcp, 58946/udp delugevpn 10280e20c0d3 tautulli/tautulli “/init” 4 hours ago Up 12 minutes (healthy) 192.168.50.149:8181->8181/tcp tautulli d36ec814d775 linuxserver/couchpotato “/init” 4 hours ago Up 12 minutes 192.168.50.149:5050->5050/tcp couchpotato 02b6f9ea174f jellyfin/jellyfin “/bin/sh -c 'dotnet …” 4 hours ago Restarting (134) 37 seconds ago jellyfin d27016aa50e7 linuxserver/sonarr “/init” 4 hours ago Up 11 minutes 192.168.50.149:8989->8989/tcp sonarr 8d1eb9d3bf05 linuxserver/radarr “/init” 4 hours ago Up 11 minutes 192.168.50.149:7878->7878/tcp radarr 22a639e847c7 pyouroboros/ouroboros “ouroboros” 4 hours ago Up 11 minutes ouroboros 208f62538e84 minio/minio “/usr/bin/docker-ent…” 4 hours ago Up 12 minutes (healthy) 192.168.50.149:9009->9000/tcp minio 26d0c7410ef0 linuxserver/ombi “/init” 4 hours ago Up 12 minutes 192.168.50.149:3579->3579/tcp ombi 7e4bee639cb6 linuxserver/muximux “/init” 4 hours ago Up 12 minutes 192.168.50.149:80->80/tcp, 443/tcp muximux 696bb193d45d linuxserver/lidarr “/init” 4 hours ago Up 11 minutes 192.168.50.149:8686->8686/tcp lidarr 9d31571ef2f9 linuxserver/duplicati “/init” 4 hours ago Up 11 minutes 192.168.50.149:8200->8200/tcp duplicati b907a08970e9 plexinc/pms-docker:public “/init” 4 hours ago Up 12 minutes (unhealthy) plex b523d4e80c44 linuxserver/nzbget “/init” 4 hours ago Up 12 minutes 192.168.50.149:6789->6789/tcp nzbget 478adadee6bb netdata/netdata:latest “/usr/sbin/run.sh” 4 hours ago Up 12 minutes 192.168.50.149:19999->19999/tcp netdata 630d32be0303 linuxserver/sickrage “/init” 4 hours ago Up 11 minutes 192.168.50.149:8081->8081/tcp sickchill fcf80e2a17e4 linuxserver/headphones “/init” 4 hours ago Up 11 minutes 192.168.50.149:8282->8181/tcp headphones 689949714d02 linuxserver/jackett “/init” 4 hours ago Up 12 minutes 192.168.50.149:9117->9117/tcp jackett 5377dbd688de portainer/portainer:latest “/portainer --no-aut…” 4 hours ago Up 12 minutes 192.168.50.149:9000->9000/tcp portainer
Any advice how I can get things up and running?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 22 (9 by maintainers)
Awesome - thanks for giving it some testing - and coming back with the details.
OK - so you didn’t have to create any custom OpenVPN files?
However it looks like the last 2 port mappings are different: The PIA config has: -p 8112:8112 -p 8118:8118 -p 58846:58846 -p 58946:58946
You’re config has: -p 8112:8112 -p 8118:8118 -p 78678:78678 -p 99999:99999 Both 78678 and 99999 are different from PIA. (Not necessarily a deal-breaker just clarifying the differences.)
Just confirm for me again that both:
78678and99999/ the user specified custom port are needed and with that as the configuration Deluge works as expected.If that config works - then there is a pretty good chance I can get this added right into Mediabox. And if I were to be unable to get worked directly into Mediabox proper, I’d likely be able to make you/others a separate branch for use with PureVPN.
I am busy the next two days but already have time set aside for some Mediabox work on Saturday - so hang tight.
Thanks again