I tried finding that hairpining thing in my router, but no luck. My router is TP-Link WR1043ND. It should have NAT loopback by default.
Hairpining is NAT loopback.
I tried finding that hairpining thing in my router, but no luck. My router is TP-Link WR1043ND. It should have NAT loopback by default.
Hairpining is NAT loopback.
Reboot and see.
No, seems it's not required for SSD drives...
But it will not hurt to use it anyway.
You can install that plugin at any time.
Don't disable your containers; that might not prevent them from creating files. Look at each one of their compose files and see if you have any volume statements that are doing it.
Can you determine the owner of that folder?
I have no help for your problem, but I am curious to know what services you had exposed to the internet that allowed you to be attacked.
Although the drive device labels /dev/sdX can and often do change from boot to boot, the filesystem UUIDs used by SnapRAID in its configuration file will not. Look in that configuration file across multiple boots to see this.
And don't confuse Device names with OMV-Names. When specifying OMV-Names don't use device labels.
Much depends on the hardware in use and drive connectivity. But here's a data point from my use case:
32GB SSD drive connected by USB 2.0 - dd backup takes 12 minutes.
I wish OMV would allow more user control over Postfix, at least enough for it to act as a mail server for the localdomain and its users. I used to have a main.cf file that allowed for this but got tired of having to restore it everytime OMV decided to overwrite it.
I just prefer that all those notification emails would be delivered locally and not have to be relayed out thru a third party mail service, gmail for example.
I'll combine my reply here with a feature request:
Given an email address and PGP public key, encrypt the notification emails with PGP. This way I don't care if they travel thru gmail, etc or are delivered locally - my email client doesn't care.
My server with its dozen disks is locked in a safe. That doesn't prevent it from being attacked over the network though. But neither do encrypted disks once unlocked and mounted.
I go to Network > Interfaces > + > Wi-Fi to enter the menu to configure. I have a device USB dongle in slots wlan0 and wlan1 with addresses that look like [xx:xx:xx:xx:xx:xx]. I believe this is IPV6.
That is not an IPv6 address. It is a network device MAC address.
QBT_WEBUI_PORT is supported and so is QBT_TORRENTING_PORT and other variables. The scripts in this "qbittorrentvpn" container do not use any variables that start with "QBT_", so you can add those to your compose/run script.
What is the purpose of these two variables? What does using them offer? What is the penalty for not using them?
Login into your running container, run: ps -e.
I didn't say anything about the binary. I said that the images are not the same, and that's where big differences in options can come in.
I don't know how to convince you of this but... Dyonr .... didn't .... care!!! Please believe me on this. I don't blame him either, I really don't, not when you can use compose with Gluetun and qBittorrent and be done with it. I only started modifying it to add a conf switcher, I should have stopped there :-/.
Actually I'm wrong again, QBT_TORRENTING_PORT=xxxx is apparently supported. Here's the --help print for qbittorrent-nox:
qbittorrent-nox is not dyonr/qbittorrentvpn.
Alles anzeigenYeh, it's one of the few... https://github.com/qbittorrent/docker-qbittorrent-nox
Sadly, there isn't one for the torrent port :-/.
These are the few I see listed:
EDIT: actually this isn't the official doc :-/, sorry just noticed. It does work however.
But QBT_WEBUI_PORT isn't listed as an available option or environment variable in Dyonr's image.
Your image or any image with that exact "iptables.sh" file. Here's yours: https://github.com/gderf/docke…ittorrent/iptables.sh#L85 Every rule with a port uses 8080...
Sample:
Well, I am running on 7070 but don't use a QBT_WEBUI_PORT= statement. Is that even supported?
services:
qbittorrentvpn:
image: gderf/qbittorrentvpn:latest
container_name: qbt
cap_add:
- NET_ADMIN
environment:
- VPN_ENABLED=yes
- VPN_TYPE=wireguard
- ENABLE_SSL=no
- PUID=1001
- PGID=100
- LAN_NETWORK=192.168.1.0/24
- NAME_SERVERS=8.8.8.8,8.8.4.4
- UMASK=022
- HEALTH_CHECK_HOST=one.one.one.one
- HEALTH_CHECK_INTERVAL=30
- HEALTH_CHECK_SILENT=1
- HEALTH_CHECK_AMOUNT=10
- INSTALL_PYTHON3=no
- RESTART_CONTAINER=yes
ports:
- 7070:8080/tcp
- 8999:8999/tcp
- 8999:8999/udp
volumes:
- /srv/d0/docker/docker-config/qbittorrentvpn:/config
- /srv/mergerfs/multimedia/.tmp/qbittorrent-downloads:/downloads
restart: unless-stopped
Alles anzeigen