I think that is exactly what happened to me as well. I've gotten into the habit of doing a dist-upgrade monthly with other updates - I thought it was relatively safe as last time I looked it was part of the 'full install' command.
I ran into the same behavior today - this was after I had just restarted my qBittorrent container to get it going on a couple of torrents (I force it to use a socks5 tunnel)
server acts like a black hole - can't ping it - cant connect to it with the vnc/window/shell Netcup CCP provides - it's...
You have to go to the portainer page (portainer.yourdomain .com) - stop the qbittorrent docker. click qbittorrent to open the docker, and then there should be a Duplicate / Edit button - click that, then you should be able to click on the 'Env' tab under 'advanced container settings'
check under your PGShield options.
Go into pg shield / disable pgshield for a single app and make sure plex isn't listed there. if it is you'll want to remove it and then re-deploy pgshield
(For example, my only exception is ombi)
Type a Number | Press [ENTER]: 2...
Another good couple of commands to know is
ncdu -x / mnt
ndcu -x /
the '-x' tells it to not follow 'links', so it won't list everything on your G Drive - can be very helpful for seeing stuff stuck in /mnt/move, etc
also be sure to check out the pgui.yourdomain.com interface - it can...
So I don't know how to fix this in the deploy script, but this has been a bug for quite a few versions of plexguide.
When deploying NZBGet, the following things are incorrect.
/opt/appdata/scripts - has incorrect permissions
drwxrwxr-x 6 drgnfyre drgnfyre 4.0K...
I got this working by copying the transmission.yml to /opt/mycontainers and editing/re-deploying it (renamed the yml file)
# MAIN DEPLOYMENT #############################################################
my "cannot connect to tracker" issue seems to be DNS related.
If I use portainer to launch a shell in the transmission environment, I cannot resolve anything - 'ping www.google.com' for example gives 'host not found'
the transmission wiki talks about starting your docker container with
I'm trying to get this to work - pulled the 'transmission' item from community branch - edited
OPENVPN_CONFIG to PIA - added my username/password to appropriate variables - set LOCAL_NETWORK to 172.17.0.0/16 (Is that right)?
When I deploy/start the container, logs show..
awesome to see some traction on this - I've been wanting to get a torrent/vpn solution working for awhile - had same problems as others with delugevpn -would initially work but then give bad gateway and son/radarr couldn't talk to it.
High hopes for the transmission vpn you guys are working on...
once you've deployed this, how do you connect to it with another docker container like sonarr or radarr? I've tried using 'trans' as the connection string (trans.tld.com works to get me to the transmission client) but they come back with can't connect or can't resolve.
I notice there is a folder - /opt/pgvault that has similar items (pgcron, etc)
did something just get moved maybe?
[email protected]:/opt/appdata/nzbget# ll /opt/pgvault/
drwxr-xr-x 3 root root 4096 Feb 5 21:12 ./
drwxr-xr-x 10 root root 4096 Feb 5 21:12 ../...
I'd recommend posting in the thread TimeKillls started - https://plexguide.com/threads/hw-transcoding-from-docker-solution-for-hetzner-dedicatd-maybe-others.2544/page-3
Is that the guide you had followed? When you run the vainfo command, does it show the correct info? (post that in the other...
good idea, Mr Doob.
Just to clarify - I put the script in /opt/appdata/plex/scripts and then had the script back itself up as well
1. nano /opt/appdata/plex/scripts/plex-dbbackup.sh
I copied the files down from 8.2 base for menu/pgvault and was able to launch pgcron - it backed up what was in the /tmp/program_var correctly.
So, what has to happen to put this back into 8.3? I fear that anyone on 8.3 isn't getting any of their pgvault jobs running correctly.