Posts by drakula

Quote from Skyhi

Right now my NAS disappears once I go remote, and after I enable wireguard I have to enter the smb://Ip.address in my folder location bar. Is there a way to just have that saved so I can just click on it, instead of entering the details each time? (with password or not?)

Unless you do this already, please try to enable first wireguard, and then start your file manager. Which file manager is it?

There is a Linux Mint Forum, maybe somebody there knows how to fix the issue: https://forums.linuxmint.com/

Quote from Skyhi

So the results of my trial is, I tried to transfer a 75mb video file from my nas to my laptop. Never mind the fact it takes more then a minute to complete any task I ask like just trying to quarry the properties of the file, once I started transferring the file topped out at 185kb/s (it would have taken several minutes (more then 10) to complete the task. My phone is connected to the cell network with 5G.

So It is very slow to access my NAS (huge lag between clicking on anything) and really slow to transfer files even on what should be a fast network. Also It's not very convenient to have to type the smb ip address thing in, but i can live with it, just wonder if there is a easier way. Still don't understand why my nas disappears from my network folder even if i am using wireguard. Clearly it can be accessed but it never shows up as available.

1. did you tether the Linux Mint laptop to the cell phone via Bluetooth, or via Wifi?

2. did you use Wireguard on both the laptop AND the cell phone while tethering, or only on the phone?

maybe it is slow because of tethering via cell phone, just guessing...

Suggest to try remote access with your Linux Mint laptop:

- without cell phone tethering

- from an external wifi, like Starbucks, McDo, or from a friend or relative

- while using Wireguard on the laptop

Quote from Skyhi

Do you mean while on my local network or when I try when using wireguard while remote?... I can enter the smb://ip and find my nas drive locally.

while remote, when using wireguard.

does your your Linux Mint file manger (Nemo?) provide the option to access a SMB/CIFS share, by manually entering the IP address of your OMV server into the address bar, like this::

smb://192.168.x.x

suggest to:

1. not change any OMV ports and leave them default, because OMV is the NAS and controls the Docker containers via compose

2. change only the pi-hole ports in Docker compose that are overlapping with OMV or other containers

example based on https://hub.docker.com/r/pihole/pihole:

version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    # For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "81:80/tcp" # to access pi-hole via <IP-address>:81, and avoid conflicts with OMV GUI at port 80

in this example due to line 12 port setting you should be able to access in a browser:

1. OMV via <IP-address>:80
2. ip-hole via <ip-address>:81

Quote from ryecoaaron

The problem is that the extra click for up, down, or pull will ruin peoples lives. Sometimes making changes like this just isn't worth dealing with all of the anger.

People's reactions can't be worse than after the omv-extras 6.3/omv-compose 6.7 update.

I'm sure the mobile Docker compose users won't complain. Mobile usability would be much improved, and there is precedence with other plugins.

sorry, I don't know enough about this topic, maybe https://forums.plex.tv/ can help.

in case you use Chrome on Android you could set it to "Desktop site", and then it shows full width.

hello, maybe the Docker container needs to claim the Plex token, see here https://www.plexopedia.com/ple…ver/general/claim-server/

In Docker compose you can enter it as an environment variable:

version: "3.6"
services:
  Plex:
    container_name: plex
    environment:
      - "PLEX_CLAIM=**********"
      - "VERSION=latest"

no, I just look at the data that the weather stations from my neighbors submit to https://www.wunderground.com/wundermap

the motherboard BIOS is from 2018; you may want to update it and see if the issue still happens...

Quote from Skyhi

Questions, I am running everything for OMV and docker on my raspberry pi. Functionality wise for tailscale does it matter if it is installed right on the pi or ran in a container on a pi

does not matter, same functionality.

Quote from Skyhi

So with what I am trying to accomplish, would docker still be a possibility to run, pi-hole, tailscale, freshrss, omv and nas, and still have remote access to everything with my phone, and laptop like I was local while being "secure"?

Can't comment on the combination of Tailscale and Pihole in Docker containers, I have no experience with that, sorry.

However, OMV should run on top of Debian, and not in a container. Did not know that's feasible, unless I misunderstood your setup. You want OMV to control the Docker containers.

I think that setting up Tailscale, Pihole and the other applications as Docker containers under OMV is more flexible and safer than setting them up right in Debian.

If something fails, you just modify or delete the Docker container. Suggest to try it out.

And not trying to confuse things, but in case the setup of Pihole is not successful, and as a backup solution, you may want to check out NextDNS.com for the clients...

You need apttool plugin, and then you can install it like a regular Debian package.

Or ,manually via curl like here described: Tailscale on OMV 6

However, installed as a Docker container it would not affect the underlying Debian installation...

this one has a GUI: https://etcher.balena.io/

my understanding of 195 Hardware_ECC_Recovered is that bigger and increasing values are better.

1 Raw_Read_Error_Rate seems to be Seagate specific with no real meaning for the user.

And health assessment is PASSED in the SMART report. Also this specific drive can be considered OK and not related to the random reboots.

Unfortunately nothing suspect is left that should be analyzed as cause for the random reboots ...

is this useful: https://askubuntu.com/question…and-give-full-rw-to-guest

1. does the PI boot without the usb drives connected?
2. where is, or was, the OS installed, to the internal SD card, or to one of the external USB drives?
3. does the PI boot with a new OS image on a different SD card?
4. is the power supply specified to meet raspi4 current and voltage requirements?
5. does the PI show any lights when powered, or is it completely dead?
6. in case you have access to a different raspi4, does it boot from the SD card of the original PI?

Ueber Proxmox weiss ich gar nichts, aber die EXT4 Fehlermeldung besagt dass "/dev/sda1 is mounted".

Und fuer XFS: "Target was already mounted".

Gibt es in /etc/fstab schon einen mount Eintrag fuer das Laufwerk und die Partition? Und wenn ja, wer oder was hat das gemacht?

Your Frigate Docker configuration seem to have issues with the volume paths. "config.yml" should be a file, not a folder.

Please post your Frigate Docker compose file..