LTM

Has anyone been able to get this container to work recently? I am trying to run it and any time I try to start it, all I get is "Execution error. Server error." I have tried deleting the container, image, and config files and starting from complete scratch. No dice.

For those with the startup script errors: I just redownloaded a configuration file from PIA website, deleted the old one, and restarted Deluge and it seems to have fixed it. It looks to me that they renamed it to exclude the "nextgen-" from the file name. I don't know if that matters.

@Hawkins I was not able to get it to work with MariaDB or MySQL but I was able to get it to work with PostgreSQL. For the DB driver, it is "pgsql". But with that, I am having a couple of other problems with Cachet: 1: I am not able to bind to container path "/var/html/www". When attempting to do so, I get an error saying that '.env can not be found'. To fix this, I essentially had to copy all of the contents in '/var/html/www' into a different folder within the container, bind the new folder to the host, and then copy the contents into my original cachet config fol

If you guys get it figured out, let me know. I am having the same issue except with mysql. Initializing Cachet container ... Attempting to connect to database ... ........................................................... Could not connect to database server! Aborting...

Can you post your unRAID log of Varken? My guess is that you did not go through the process of getting a maxmind license key and it's failing to download the database upon start which would cause it to fail. You can sign up for a free account here: https://www.maxmind.com/en/geolite2/signup

I guess this is why I am unable to get things running. I have been waiting for 6 hours for something to happen. the container log just stops at 2021-02-01 12:54:18,581 Selected macOS Product: 061-86291 and nothing happens after. Guess I will have to wait for the container to get updated.

I am also getting the 1006 error but I am trying to access it locally.

You can download it and import it to use. I did find that I had to change a bunch of panels for them to work correctly. Things like the data growth panels are defaulted to "/mnt/user0" and I had to change them to include "/rootfs" so they are "/rootfs/mnt/user0".

I have found that I manually have to download the plugins and manually add them to the /grafana/data/plugins folder. You can then either restart the docker container or use "sudo service grafana-server restart" to restart Grafana alone. I am not sure if they are simply getting installed to the wrong folder or if it is just failing in general. I did come here to ask if this is still being maintained. Grafana is a couple versions behind at least and I am sure that other services are behind as well. I like how this puts everything in to a single container. If this is not going to

Ah. I am still on the latest stable version of unraid. I think my problem is that whenever I try to use apk, it says that it is not installed for me. I guess I will look in to GUS as well.

Is this Telegraf RC2? I am trying to fix this without starting from scratch but I am leaning towards just deleting all of my config files and starting new again.

I also have the same problem. Rolling back did not help. I ended up disabling [[inputs.smart]] altogether in telegraf.conf for me to get mostly everything to work again.

I am also getting [telegraf] Error running agent: could not initialize input inputs.smart: smartctl not found: verify that smartctl is installed and it is in your PATH (or specified in config): provided path does not exist: [] Switching to :latest does not fix the problem. I have also tried :1.16 and :1.16.3 with the same result.

Just putting the Github issue here. More active than these forums. https://github.com/haugene/docker-transmission-openvpn/issues/1463 Some people have had success changing the PIA login details to the ones you use to log in (p#######) instead of the 'PPTP/L2TP/SOCKS' username and password (x#######). It took like an hour, but this eventually did the trick for me.

I am having the same issue as Xed. I have it set up with a custom network. I had to revert back to 2.14 for things to start working again.