Can we enable the use of Tailscale (via unraid 7) with the Technitium container?

On 12/17/2024 at 2:26 PM, DanielPT said:

Hi
I can see that there is a update for Duplicacy. Where can i see the version and what changes in this?

 

Thanks!

 

Was there a change log available? I'm a new duplicacy user as of the BF sale for the web client. I setup email notification without issue. That quit working mid-December and perhaps is related to this container update. There have been no duplicacy web/CLI releases in December that I can see. More details here:

 

https://forum.duplicacy.com/t/web-ui-docker-email-on-port-465-failing-i-o-timeout/8956/3

Has anyone run into this after install for Backblaze_Personal_Backup? Nothing happens if I click in the taskbar. I went into install apps and to c and tried to run the installer there as well. Nothing happens. The error log is empty. 

 

 

Edited January 4, 20251 yr by tenletters

5 hours ago, tenletters said:

Has anyone run into this after install for Backblaze_Personal_Backup? Nothing happens if I click in the taskbar. I went into install apps and to c and tried to run the installer there as well. Nothing happens. The error log is empty. 

 

 

Yup, having the exact same issue...

How would I increase the retention time?

--storage.tsdb.retention.time

 

Edited January 9, 20251 yr by nebb00

Maihai's Invoice Ninja container still uses v5.11.11 which is broken and Invoice Ninja pushed some updates last night to fix it. v5.11.17 supposedly corrected the issue but Maihai needs to update his template. FYI for anyone seeing this 01/09/25 

focalboard is broken by default, creates db and files in /opt/focalboard/data while mapped '/data' via unraid path is at /data

to fix I have changed container path from /data to /opt/focalboard/data

Edited January 11, 20251 yr by kronox

HELP!

getting certificate signed by unknown authority.

I am testing this with my locally hosted minio server.

Thanks....

On 1/4/2025 at 9:10 AM, tenletters said:

Has anyone run into this after install for Backblaze_Personal_Backup? Nothing happens if I click in the taskbar. I went into install apps and to c and tried to run the installer there as well. Nothing happens. The error log is empty. 

 

 

I ran into this issue as well.  I ran the installer on another machine and copied the Backblaze directory contents into the corresponding folder under appdata.  
For me the folder was \appdata\Backblaze_Personal_Backup\wine\drive_c\Program Files (x86)\Backblaze

19 hours ago, Broof56 said:

I ran into this issue as well.  I ran the installer on another machine and copied the Backblaze directory contents into the corresponding folder under appdata.  
For me the folder was \appdata\Backblaze_Personal_Backup\wine\drive_c\Program Files (x86)\Backblaze

and it ended up working? I don't have a second NAS. I ended up using opendrive. It started seeming like a bad idea to have to rely on this pluging for backups.

Last Update to the InvoiceNinja_v5 breaks the docker.  It always die at start with this error : 

 

(76): Fatal Error "opcache.preload" requires "opcache.preload_user" when running under uid 0
Processing Event: ver:3.0 server:supervisor serial:0 pool:shutdown poolserial:0 eventname:PROCESS_STATE_EXITED len:74
Thu Jan 23 22:26:13 2025 (81): Fatal Error "opcache.preload" requires "opcache.preload_user" when running under uid 0

 

Any update comming to fix this ??  Thanks !

 file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  self.warnings.warn(
Fri Jan 24 15:00:07 2025 (75): Fatal Error "opcache.preload" requires "opcache.preload_user" when running under uid 0
Fri Jan 24 15:00:08 2025 (80): Fatal Error "opcache.preload" requires "opcache.preload_user" when running under uid 0
Processing Event: ver:3.0 server:supervisor serial:0 pool:shutdown poolserial:0 eventname:PROCESS_STATE_EXITED len:74

Same here

Hi @Pducharme and @GordoPepper,  I ran into the same problem earlier today and learned that a fix was available.  After a force update, it worked again.

 

 See post:

 

 

Setup seedsync (not nerdtools and LFTP is dead there) and i can pull from my seedbox but I am finding that the speed is extremeley inconsistant and more often very slow. If i were to do LFTP via the old method via user scripts i would max out my gigabit connection 100% of the time. WIth this I am maxing out at between 6MB/s and 45MB/s. I've tried to increase the number of connection but no change. 

Is there a specific setting of connection number that I need to play to max out my connection? 

On 1/16/2025 at 9:21 PM, Broof56 said:

I ran into this issue as well.  I ran the installer on another machine and copied the Backblaze directory contents into the corresponding folder under appdata.  
For me the folder was \appdata\Backblaze_Personal_Backup\wine\drive_c\Program Files (x86)\Backblaze

You did that on another windows machine?

Is the Deemix docker dead?  Mine seems to be updated, and is running fine, but I'm unable to download.  It says I need to login, but I'm unable to do so.  I've logged in at the Deezer site with no problems, but the instructions on the docker help page about how to obtain an ARL seem to be outdated.  For example, Chrome no longer displays a 'lock' icon next to URLs.  Anyone got this working?

I want to enable remote write reception on my prometheus.
I added the flag to post arguments

--web.enable-remote-write-receiver

This leads to the following error:
 

level=ERROR source=main.go:593 msg="Error loading config (--config.file=prometheus.yml)" file=/prometheus/prometheus.yml err="open prometheus.yml: no such file or directory"

 

Appdata is set to /mnt/user/appdata/prometheus/data
Config is set to /mnt/user/appdata/prometheus/etc

Container runs fine without the post argument.

 

How can I get prometheus running with remote write reception enabled?

im using the adminer docker. when i import a gz file,

It gives me this error,  Too big POST data. Reduce the data or increase the 'post_max_size' configuration directive.

I tried adding the following variables and it did not work.

MEMORY=512M

UPLOAD=4096M

 

 

Does anyone know how to increase the import upload limit. Thank you very much!!!

 

On 1/4/2025 at 3:10 PM, tenletters said:

Has anyone run into this after install for Backblaze_Personal_Backup? Nothing happens if I click in the taskbar. I went into install apps and to c and tried to run the installer there as well. Nothing happens. The error log is empty. 

 

 

Also having this issue, although I can't even see the taskbar.

On 3/3/2025 at 4:50 AM, augot said:

Also having this issue, although I can't even see the taskbar.

Since it got updated the other day neither can I.

Re: Backblaze

Same blank blue desktop here, for the last couple of updates.

The pre-existing backup config is still working however - I can see upload activity from the docker, and Backblaze web account shows new data appearing as normal.

 

So - just a UI/VNC error it seems. 

 

UPDATE:

Half-assed workaround - I found opening the *non* HTTP VNC address (usually port :5901) in a 3rd party VNC viewer caused the Backblaze app window to display.

After this has been done once, the `standard` Unraid HTTP web VNC (usually port :5801) will work thereafter.

 

The taskbar is still absent however.

 

Hopefully someone with more VNC-fu than me can work out whatever weird resolution/scaling/render hangup is causing the base issue.

 

 

Edited March 12, 20251 yr by kurai

For those looking to get Xibo 4.2.1 (latest) running.
-you will need to remove any current cms or xmr containers/images you currently have running.

From the app store install the 'Docker Compose Manager'
 

Create a directory for Xibo CMS

mkdir -p /mnt/user/appdata/xibo4/xibo-docker-4.2.1
cd /mnt/user/appdata/xibo4/xibo-docker-4.2.1

Download Xibo CMS Docker Files

wget https://github.com/xibosignage/xibo-cms/releases/download/4.2.1/xibo-docker.zip
unzip xibo-docker.zip
rm xibo-docker.zip

Ensure all required directories exist:

mkdir -p /mnt/user/appdata/xibo4/{custom,backup,web/theme/custom,library,web/userscripts,ca-certs}

Configure the Environment Variables

Copy the environment configuration file:

 

cp config.env.template config.env

Edit the config.env file:

nano config.env

Modify the following settings:

## Database Configuration (External MariaDB)
MYSQL_HOST=your-mariadb-ip
MYSQL_PORT=3306
MYSQL_DATABASE=xibo4
MYSQL_USER=xibo4
MYSQL_PASSWORD=your-secure-password

## XMR Configuration
XMR_HOST=tcp://your-mariadb-ip:9505

## SMTP (Email) Configuration
CMS_SMTP_SERVER=smtp.gmail.com:587
[email protected]
CMS_SMTP_PASSWORD=your-email-password
CMS_SMTP_USE_TLS=YES
CMS_SMTP_USE_STARTTLS=YES

## Web Server Configuration
CMS_SERVER_NAME=xibo.yourdomain.com

## File Upload Limits (Optional)
CMS_PHP_POST_MAX_SIZE=2G
CMS_PHP_UPLOAD_MAX_FILESIZE=2G
CMS_PHP_MAX_EXECUTION_TIME=300

 

Configure Docker Compose in Unraid

cd /mnt/user/appdata/xibo4/xibo-docker-4.2.1 && nano docker-compose.yml

Paste the following docker-compose.yml into the editor:

version: "3.8"

services:
  cms-xmr:
    image: ghcr.io/xibosignage/xibo-xmr:1.0
    container_name: xibo-xmr
    networks:
      - proxynet
    ports:
      - "9505:9505"
    restart: always
    mem_limit: 256m
    env_file: config.env

  cms-web:
    image: ghcr.io/xibosignage/xibo-cms:release-4.2.1
    container_name: xibo-cms
    networks:
      - proxynet
    depends_on:
      - cms-xmr
    volumes:
      - "/mnt/user/appdata/xibo4/custom:/var/www/cms/custom:Z"
      - "/mnt/user/appdata/xibo4/backup:/var/www/backup:Z"
      - "/mnt/user/appdata/xibo4/web/theme/custom:/var/www/cms/web/theme/custom:Z"
      - "/mnt/user/appdata/xibo4/library:/var/www/cms/library:Z"
      - "/mnt/user/appdata/xibo4/web/userscripts:/var/www/cms/web/userscripts:Z"
      - "/mnt/user/appdata/xibo4/ca-certs:/var/www/cms/ca-certs:Z"
    restart: always
    environment:
      - MYSQL_HOST=your-mariadb-ip
      - MYSQL_PORT=3306
      - MYSQL_DATABASE=xibo4
      - MYSQL_USER=xibo4
      - MYSQL_PASSWORD=your-secure-password
      - XMR_HOST=tcp://your-mariadb-ip:9505
      - CMS_USE_MEMCACHED=true
      - MEMCACHED_HOST=cms-memcached
      - CMS_SMTP_SERVER=smtp.gmail.com:587
      - [email protected]
      - CMS_SMTP_PASSWORD=your-email-password
      - CMS_SMTP_USE_TLS=YES
      - CMS_SMTP_USE_STARTTLS=YES
    env_file: config.env
    ports:
      - "8976:80"
    mem_limit: 1g

  cms-memcached:
    image: memcached:alpine
    container_name: xibo-memcached
    networks:
      - proxynet
    command: memcached -m 15
    restart: always
    mem_limit: 100M

  cms-quickchart:
    image: ianw/quickchart
    container_name: xibo-quickchart
    networks:
      - proxynet
    restart: always

networks:
  proxynet:
    external: true

Save and exit (CTRL+X, then Enter).

Now, run:

cd /mnt/user/appdata/xibo4/xibo-docker-4.2.1
docker compose up -d

 

Once running, open your browser and visit:

http://your-unraid-ip:8976

 

Default Login:

Username: xibo_admin
Password: password

 

Change the password after logging in.

On 3/10/2025 at 5:04 PM, kurai said:

Re: Backblaze

Same blank blue desktop here, for the last couple of updates.

The pre-existing backup config is still working however - I can see upload activity from the docker, and Backblaze web account shows new data appearing as normal.

 

So - just a UI/VNC error it seems. 

 

UPDATE:

Half-assed workaround - I found opening the *non* HTTP VNC address (usually port :5901) in a 3rd party VNC viewer caused the Backblaze app window to display.

After this has been done once, the `standard` Unraid HTTP web VNC (usually port :5801) will work thereafter.

 

The taskbar is still absent however.

 

Hopefully someone with more VNC-fu than me can work out whatever weird resolution/scaling/render hangup is causing the base issue.

 

 

I tried this and unfortunately it didn't work for me - other VNC viewers give me the same blank blue desktop as the one in my browser (Firefox).

Hey, I noticed it was mention in a older post but wanna bring up again.
Traccar is missing Volume path.

This needs to be added or else Traccar deletes the database when it updates.
I had it happen twice now thinking it was a fluke but the docker container was missing this path.
--volume /opt/traccar/data:/opt/traccar/data:rw \

 

The Hexoblog container is basically unusable at this point.

 

Each time that you start it, it expects a new directory and to initialize an entirely new blog.

You have to give it a new appdata/hexoblog/config directory every time you start it.

 

Then you have to copy over its files to the new DIR whilst the container is running and delete the old DIR for your blog. If the container stops for any reason or you need to restart your machine. You have to do this process all over again...

 

The maintainer has also said that they won't update this container anymore. So it's for all intensive purposes out of date and unmaintained. RIP.

Last update also seems to be: Nov 22, 2022

 

The container should be removed from the Unraid apps library.

Edited March 25, 20251 yr by plantsandbinary