Posts by vcdwelt

    Hi,

    i have configured a Wetty Docker in combination with swag.

    It took some time to figger out, how it will work. And finally i found, it was very easy to do. Maybe this will help someone who is struggling with the same problem :)

    At the end it was the missing env option "- BASE=/" in Docker config of wetty


    wetty.subdomain.conf


    wetty.yaml

    Hi,

    i have an issue with Linuxserver SWAG Container. The integrated Fail2ban bans me frequently.

    Happens on different Container, when accessing about subdomain. In the Logs it is used portainer for example, but happens also on other Containers accessed trough SWAG.

    In the example i opened the Portainer Page and got the Portainer Login Page, but this is enough to trigger Fail2ban. Also happens on other containers, when Login Pages appears. Why is a login Page triggering the Fail2ban Unauthorized?


    jail.local:

    fail2ban.log:

    Code
    2024-11-04 12:30:53,464 fail2ban.filter         [799]: INFO    [nginx-unauthorized] Found 80.80.80.80 - 2024-11-04 12:30:53

    access.log:

    Hi,

    i'm currently installing my OMV Server completely new, to start a new clean enviroment.


    Most things are up and running, but now i have a problem with Installing Nextcloud/MariaDB Docker.


    Swag is already running in his own container with bridge Network "swag_default" where i connect all my other Docker Files (Plex, Calibre-Web,...). Working so far fine.


    My Yaml:


    The Error i receive on Configuration:


    Config.php


    Okay, had the same idea on SD and Pendrive. Other Solutions e.g. unraid are forcing users to use a pendrive for the OS Part. Also my Raspi is running for years with the same old SD Card :)


    I think it's worth a try ^^


    Also found the topic on how to use the omv-regen command in Forum. I think i will order a SD Card and give it a try. If it fails badly i still have my old SSD in place to swap it in.

    Sounds interesting. I will consider this Solution.

    The Server has also an internal USB Port, which i can use for a USB Stick with OS.


    What is better (and more durable) for OS Instalation, a usb stick or a miscrosd card?

    Can i also clone the ssd to an USB Stick or MicroSD Card?

    Hi,

    i have a OMV Running fine for over some years (including several Updates since OMV 2 or 3).

    Spec:

    HP Micro Server gen 8

    4x HDD (Data)

    1x SSD (OMV)

    1x MicroSD (Forward Booting to SSD, because Server can't boot from the SATA Port, the SSD is connected).


    Now i want to exchange the SSD for a bigger one.

    What is the best way to do so, without loosing any Data or Configuration. I'm note really deep into Linux OS, just scratching on the surface.


    It was a long way, the Server was running as it is actually and i'm afraid of crashing the Server.

    Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):

    Code
    sudo mkdir -p /etc/default/grub.d
    echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' | sudo tee /etc/default/grub.d/apparmor.cfg
    sudo update-grub
    sudo reboot

    Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

    Thanks a lot. Worked for me also :saint::thumbup:
    You saved my day ^^

    So first test seems fine :love:


    Added the value:

    Code
    ExecStartPre=/bin/sleep 30

    in the file:

    Code
    /etc/systemd/system/multi-user.target.wants/docker.service
    (-> /lib/systemd/system/docker.service)


    Bootet twice and worked both times without any manual tasks. :saint:

    Ok, what Info should i post exactly? I try to list some points you mentioned


    My OMV is running since OMV 4, Updated to OMV 5 and finally to OMV 6.


    Not sure where the mountpoints inside /medie com from. They are there for a long time. But as far i remember, i have created them by hand.


    Hardware is a HP Microserver with 4 build in HDD Bays and a SSD conencted also internal.

    HDD's are for Data only, SSD is used for OMV (Incl. Configs and Docker files...).


    No USB Devices connected.


    But maybe your idea, the /media mount points not ready on starting docker, sounds logical for me.

    So maybe it is enough to set the Docker.service start delay a little higher. Or settings the Host Path instead of /media/Disk_? directly to the real path /srv/dev_disk_by...

    Hi,

    since a few days i have a strange problem. For my feeling this appears since the last Kernel Update.


    Information:

    Version: 6.0.30-1 (Shaitan)

    Kernel: Linux 5.18.0-0.bpo.1-amd64


    Scenario:
    Server is booting and seems to be running fine. But Plex and some other Containers (e.g. SABnzbd) can't connect to the Storage configured insite the Container. A simple Restart (in Portainer) of the affected Container solves the problem until the next reboot.
    Happens not on every Server Boot, but nearly on all (~90% i would think).


    Any hints where i could start problem solving.

    I'm still a Linux beginner :/ and a Docker noob 8|


    This are the mount points

    No, sadly not. Or something isn't working correctly.


    For my understanding the IP Range is only used to check for the services/Ports listed below.

    Check IP x.x.x.x if Port xxx is used.


    Because if there is no active access on any of the listed Ports, the Server is is shutting down.

    eg. 192.168.178.188 was turned on (no Stndby or something) but Server was shutting down anyways.


    I'm opern for any idea which can solve my request, must not with use of the plugin (would be nice, but must not).

    Hi,

    trough playing around with Kernels and Configs i have installed the Proxmox Kernel trough the OMV-Extras Plugin. But i don't need it, because i don't use Proxmox at all.

    Now how i could start a clean uninstall of the Proxmox Kernel?


    And how is the proper way to remove old Kernels i don't use anymore?

    Yes it is possible with some tricks, but can have very bad consequences (as described on heise articel). Also i won't flash a modded Bios on my Server, too much fear 8|


    Once configured it is no problem anymore, until the next OMV Update :/8)