Upgrade flaresolverr docker container

Today I noticed CAPTCHA was not getting resolved in Jackett but without obvious reason. I thought that flaresolverr rlease I was using was outdated so I wanted to try to update it to latest one. First I have checked what I have running:

# docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED        STATUS        PORTS                    NAMES
f144c092302c   a88ebf3195a5   "/usr/bin/dumb-init …"   4 months ago   Up 10 hours   0.0.0.0:8191->8191/tcp   flaresolverr

Pulled new image:

docker image pull ghcr.io/flaresolverr/flaresolverr:latest

Checked if the images are there:

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED        SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago    574MB
ghcr.io/flaresolverr/flaresolverr   <none>    a88ebf3195a5   4 months ago   569MB

Stop and delete the container:

docker stop f144c092302c
docker rm f144c092302c

Once container has been stopped and deleted. I have started a new instance:

docker run -d   --name=flaresolverr   -p 8191:8191   -e LOG_LEVEL=info   --restart unless-stopped   ghcr.io/flaresolverr/flaresolverr:latest

Check if new container is running:

# docker ps
CONTAINER ID   IMAGE                                      COMMAND                  CREATED         STATUS        PORTS                              NAMES
e8ec7ca07cf3   ghcr.io/flaresolverr/flaresolverr:latest   "/usr/bin/dumb-init …"   3 seconds ago   Up 1 second   0.0.0.0:8191->8191/tcp, 8192/tcp   flaresolverr

Cleanup of the unused image:

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED        SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago    574MB
ghcr.io/flaresolverr/flaresolverr   <none>    a88ebf3195a5   4 months ago   569MB

# docker image rm a88ebf3195a5

# docker images
REPOSITORY                          TAG       IMAGE ID       CREATED       SIZE
ghcr.io/flaresolverr/flaresolverr   latest    5d07ec0ae1eb   4 weeks ago   574MB

Fix WordPress update not completing

I tried recently to update WordPress to release 6.3 but it was constantly failing in my setup with nginx/php-fpm7.4.

Easiest way to fix it is to find this part of your site config in nginx:

        location ~ \.php(?:$|/) {
                include snippets/fastcgi-php.conf;
                fastcgi_pass php;
        }

and append it with fastcgi timeout settings:

        location ~ \.php(?:$|/) {
                include snippets/fastcgi-php.conf;
                fastcgi_read_timeout 600;
                fastcgi_send_timeout 600;
                fastcgi_connect_timeout 600;
                fastcgi_pass php;
        }

dietpi fstab network

Here is what I use to mount:

sshfs#[email protected]:/mnt/HD/HD_a2/owncloud /mnt/dietpi_userdata/owncloud_data fuse defaults,allow_other,_netdev,x-systemd.automount 0 0
192.168.0.X:/mnt/HD/HD_a2 /mnt/backup nfs nofail,noauto,x-systemd.automount
//192.168.0.X/USBDisk1_1 /mnt/torrents cifs cred=/var/lib/dietpi/dietpi-drive_manager/mnt-torrents.cred,iocharset=utf8,uid=dietpi,gid=dietpi,file_mode=0666,dir_mode=0777,vers=1.0,nofail,noauto,x-systemd.automount

How to fix autounpack in rutorrent

If your autounpack is not working after rtorrent has finished with the download make sure that tasks folder has permissions 0777.

chmod 0777 /var/www/rutorrent/share/settings/tasks

Midnight commander mc not showing in default colors in GNU screen

If you are using GNU screen and you notice that while MC is showing in default blue color for root but not for the user the easy fix would be to try this:

TERMCAP='' /usr/bin/mc --skin=default

If this works for you and mc is showing in color then you can setup an alias in your .bashrc like:

alias mc='TERMCAP="" /usr/bin/mc --skin=default'

do the reload of .bashrc with:

source .bashrc

Then the next time you run mc from with your user it should be displayed in default color instead of black and white.