Posts by elsmandino

Brilliant - thank you.

I have managed how to schedule a task to run hourly but I am struggling a bit with the Linx command.

I have directory called Data, located as follows:

/export/Data

What command would I have to run if I wanted to do the following:

1. Remove the prefix of any directories (within Data) that start with "New:" - i.e. "New: Top Gear", would be come "Top Gear"

2. Remove any directories (again within Data) that were empty and had not been modified in the last 30 days

Thanks - I was hoping to do it things automatically on my Linux server.

Hi there.

I am having a bit of an issue with my recordings, at the moment.

The EPG data, that I am using, adds "New:" to the beginning of my file names, when they are first shown.

This stops them being scraped correctly and I cannot find a way for Jellyfin to automatically ignore the prefix.

I am thinking of changing the file name itself.

How is it best to do this on OMV?

Should I use a renaming program in docker or is there a better alternative?

Thanks ever so much.

It seems that the command, that you suggested, did the trick.

My system just needed a reboot and Wireguard immediately started working.

I then ran the Adguard docker and it works perfectly whilst Wireguard carried on working as well.

Ever so pleased - thanks again! Really appreciate it.

Thank you - yep, everything has been returned to before I started messing with Adguard.

My router's DNS has been put back to Auto and my Wireguard app has nothing has nothing in the DNS box (like it originally did when nothing was working).

I have also run

apt clean

I tried Wireguard, again, but still nothing.

Thanks mate.

I tried changing the DNS, tried uninstalling Wireguard from both OMV and my phone and reinstalling them.

No matter what I do, Wireguard never now works despite working flawlessly before for weeks.

I simply don't understand what I have done and thought that docker was supposed to prevent this.

I wish I had the knowledge to dig into the log files to work out what is going on but I literally do not know where to start.

Thank you - appreciate your time.

I have stopped the Adguard container and changed back all settings and I cannot work out why it is still messing things up - totally agree that it must be that doing the damage.

I guess that a full OS reinstall is going to be the only way forward.

Out of interest, do you use any alternatives to Adguard such as PiHole?

Thanks chente - I added my router's IP as the DNS and still nothing.

Really confusing.

I really want to avoid having to reinstall the OS, if at all possible.

I checked the Wireguard logs on the app and it again keeps showing the message

Fri Sep 13 19:38:23 GMT +1:00 2024
@set_meddtdata: update dataspace from GM (0x00000000

Over and over again - is that to be expected?

Thanks chente - I shall definitely try that.

What address do you think I should try?

I have changed all the settings back and my Wireguard tunnel still doesn't work - am really gutted as it worked perfectly before and I wish I hadn't messed around with it.

Is there any way to check Wireguard's logs to see what is suddenly doing wrong?

I think my main issue now is that I had a rock solid set up, ticking away nicely, until I messed around with Adguard and I suddenly have no external access to my network.

I used to use PiHole, without any issue, so I might go back to using that (though I have read that it is not quite as good).

I think my first step is to try and undo all the setting I made in my earlier post and see if I still external access - fingers crossed that everything will work again and I consider how best to proceed from there.

Thanks very much for your further input.

I followed the guide, that I linked (to set up MacVlan, and now have Adguard running with the following container variables:

services:
  adguardhome:
    container_name: adguardhome
    image: adguard/adguardhome:latest
    hostname: adguardhome
    restart: unless-stopped
    ports:
      - 53:53/udp
      - 53:53/tcp
      - 80:80/tcp
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/work:/opt/adguardhome/work
      - /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/conf:/opt/adguardhome/conf
    environment:
      - PUID=1001
      - PGID=100   
    networks:
      mynet:
        ipv4_address: 192.168.1.241
networks:
  mynet:
    external: true

Once I remembered to change my router's DNS to the new IP address, everything was running as expected but my Wireguard tunnel is still not working.

My only reason for wanting external access to my server, at the moment, is to use the HomeAssistant app while I am away from home.

However, I was hoping to also add some sort of back up for my photos at some point, when I am out.

As a test, I set up my Wireguard tunnel to only work with my Firefox app.

When the tunnel is down, the app works fine but when it is activated I cannot access anything.

It does seem that Adguard has somehow prevented my use of the Wireguard plugin.

Edit - as a test, I changed my router's DNS back to auto and stopped the Adguard Container.

My Wireguard tunnel still does not work, so there is some change that I have made that is stopping it from running all together.

I have looked at the logs, on my Wireguard app, and it keeps saying

"@set_metadata: update dataspace from GM" 

about 10 times per second, so something really odd is going on.

After a bit more research, I can see that a similar issue has come up before:

Issue with docker compose file - General - openmediavault

I am going to update my docker compose file with raulfg3's suggested code:

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
networks:
  MyMacVlan:
    external: true
services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    cap_add:
      - NET_ADMIN
    networks:
      MyMacVlan:                        # <-- MACVlan Name You need to create first in Portainer WebGUI.
        ipv4_address: 192.168.1.3       # <-- Update to your desired adguard IPv4
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/adguard/Work:/opt/adguardhome/work
      - CHANGE_TO_COMPOSE_DATA_PATH/adguard:/opt/adguardhome/conf
    restart: unless-stopped

I note that I need to set up a MACVlan as described on this page:

omv7:omv7_plugins:docker_compose [omv-extras.org]

The instructions seem quite complicated but do I need to follow the whole guide - i.e. does Adguard require communication between the container and the host? The guide says not, if you are using PiHole.

Thanks for that.

I have tried to mess around with my settings but the issue remains.

I am a bit of a novice when it comes to networking.

Quote from fbeye

Maybe has to do with setting the WG DNS to the ADGuard DNS IP? Such as DNS

Code

192.168.1.19

In WG?

Just throwing that out there, like always probably some 10 lines 40 responses will be the correct one.

Does this mean that I have somehow set things up so that my system is blocking itself?

Afternoon all.

I followed the OMV7 official guide to get Wireguard up and running on my server and have had no issues access my server, from outside my home network, using the Android Wireguard app.

I have recently, however, installed Adguard Home as a container:

services:
  adguardhome:
    container_name: adguardhome
    image: adguard/adguardhome:latest
    hostname: adguardhome
    restart: unless-stopped
    ports:
      - "192.168.1.19:53:53/udp"
      - "192.168.1.19:53:53/tcp"
#      - "192.168.1.19:3000:3000/tcp"
      - 8083:80/tcp
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/work:/opt/adguardhome/work
      - /srv/dev-disk-by-uuid-85c4513d-cfd9-4134-ad11-5d6552e81a81/appdata/adguardhome/conf:/opt/adguardhome/conf
    environment:
      - PUID=1001
      - PGID=100    

Whenever, I run the Adguard container, my phone immediately loses access.

I was not expecting this and cannot quite work out what the issue is.

Any advice on allowing the connection through would be much appreciated.

Thanks mate - really appreciate all your assistance with this.

I have certainly learnt a thing or two and I will definitely give winSCP a go, as well.

I have to admit, I still find permissions in Linux quite confusing.

I followed the Docker section in the OMV7 guide, exactly, and I set up a dedicated user called "appuser", which had a UID of 1001 and a GID 100.

I cannot quite work out why I needed

user: 1001:100

because I thought that all containers would automatically use the appuser ID automatically.

Thank you soooooooo much, Jata1.

I finally got it working, thanks to you.

I ended up adding

user: 1001:100

to compose but then the trick was to change the data file to

(sudo chown -R 1001:100 path/to/your/node-red/data)

Working perfectly, now.

Node-Red with HA is brilliant - I find it much easier to set up complicated automations, when I can visually see everything happening.

Thanks again!

I just do not get it.

I managed to get Node-Red running but I made a mistake and had to delete the folder and try again.

I am back to the original error, again.

I have never had so much of an issue with a container, before.

All I can tell is that this is causing the issue, but I just cannot seem to sort it out:

Running under Docker : Node-RED (nodered.org)

Finally figured it out.

In case it helps anyone else, the docker container defaults to assuming that the owner of the data folder is 1000 (which it is not in my case).

To get round this, I had to add "appuser" to my ssh group, ssh in and then create the data folder.

Damn - spoke too soon.

Still having this error and the docker keeps stopping:

node-red-1  | node:fs:3035
node-red-1  |   binding.copyFile(
node-red-1  |           ^
node-red-1  | 
node-red-1  | Error: EACCES: permission denied, copyfile '/usr/src/node-red/node_modules/node-red/settings.js' -> '/data/settings.js'
node-red-1  |     at Object.copyFileSync (node:fs:3035:11)
node-red-1  |     at copyFile (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:64:6)
node-red-1  |     at onFile (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:50:25)
node-red-1  |     at getStats (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:42:44)
node-red-1  |     at Object.copySync (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:32:10)
node-red-1  |     at Object.<anonymous> (/usr/src/node-red/node_modules/node-red/red.js:148:20)
node-red-1  |     at Module._compile (node:internal/modules/cjs/loader:1469:14)
node-red-1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
node-red-1  |     at Module.load (node:internal/modules/cjs/loader:1288:32)
node-red-1  |     at Module._load (node:internal/modules/cjs/loader:1104:12) {
node-red-1  |   errno: -13,
node-red-1  |   code: 'EACCES',
node-red-1  |   syscall: 'copyfile',
node-red-1  |   path: '/usr/src/node-red/node_modules/node-red/settings.js',
node-red-1  |   dest: '/data/settings.js'
node-red-1  | }
node-red-1  | 
node-red-1  | Node.js v20.17.0
node-red-1  | node:fs:3035
node-red-1  |   binding.copyFile(
node-red-1  |           ^
node-red-1  | 
node-red-1  | Error: EACCES: permission denied, copyfile '/usr/src/node-red/node_modules/node-red/settings.js' -> '/data/settings.js'
node-red-1  |     at Object.copyFileSync (node:fs:3035:11)
node-red-1  |     at copyFile (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:64:6)
node-red-1  |     at onFile (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:50:25)
node-red-1  |     at getStats (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:42:44)
node-red-1  |     at Object.copySync (/usr/src/node-red/node_modules/fs-extra/lib/copy/copy-sync.js:32:10)
node-red-1  |     at Object.<anonymous> (/usr/src/node-red/node_modules/node-red/red.js:148:20)
node-red-1  |     at Module._compile (node:internal/modules/cjs/loader:1469:14)
node-red-1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
node-red-1  |     at Module.load (node:internal/modules/cjs/loader:1288:32)
node-red-1  |     at Module._load (node:internal/modules/cjs/loader:1104:12) {
node-red-1  |   errno: -13,
node-red-1  |   code: 'EACCES',
node-red-1  |   syscall: 'copyfile',
node-red-1  |   path: '/usr/src/node-red/node_modules/node-red/settings.js',
node-red-1  |   dest: '/data/settings.js'
node-red-1  | }
node-red-1  | 
node-red-1  | Node.js v20.17.0

END OF LINE