OMV unreachable

  • I installed omv earlier with succes.
    Then i installed unifi docker and image
    With succes
    Then i installed pihole docker and image
    However after starting pihole i couldnt reach the gui
    i looked in logs and it said something about port already taken
    i watched into omv and there i saw the same port "80"
    i deleted this and tried again


    What i have now is:
    - unifi controller is accesible
    - pihole is accesible
    but i cant reach omv anymore !


    Think i did something very wrong :p


    Please help (running on raspberry pi 3b+)

    • Offizieller Beitrag

    If you want pihole to listen on port 80, you need to change the port that the OMV web interface is on. Change one or the other.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    How do i change ports of omv

    The General Settings tab or omv-firstaid.


    dockers/images?

    Change the port forwarding that you setup.


    I can chose any combination of numbers freely for ports?

    Pretty much.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    i dont see the port forwarding in the setup of the image..

    Your best option is to stop pihole from the cli e.g. docker stop container name that should allow you to log into the GUI again then delete the pi-hole container and check out the guides section for installing pi-hole.

  • i see this in the logs from pihole



    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    [s6-init] ensuring user provided files have correct perms...exited 0.
    [fix-attrs.d] applying ownership & permissions fixes...
    [fix-attrs.d] 01-resolver-resolv: applying...
    [fix-attrs.d] 01-resolver-resolv: exited 0.
    [fix-attrs.d] done.
    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 20-start.sh: executing...
    ::: Starting docker specific checks & setup for docker pihole/pihole
    WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server
    WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 1.1.1.1)


    nameserver 1.1.1.1
    Assigning random password: ZXqbNhez
    Existing PHP installation detected : PHP version 7.0.33-0+deb9u5


    Installing configs from /etc/.pihole...
    Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
    Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf...[K [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
    chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
    Setting password: ZXqbNhez
    + pihole -a -p ZXqbNhez ZXqbNhez
    [✓] New password set
    Using default DNS servers: 8.8.8.8 & 8.8.4.4
    DNSMasq binding to default interface: eth0
    Added ENV to php:
    "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
    "ServerIP" => "192.168.99.3",
    "VIRTUAL_HOST" => "192.168.99.3",
    Using IPv4 and IPv6
    ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))






    I dont see any dns setting int he image setup inside omv

  • ?( I take you have done the first part of my suggestion? The second part Pi-Hole how to is here I don't use docker for pi-hole any more mine runs on a RPi.

    im reading the pdf file


    it says i need to setup inside omv settings a network interface?
    then i need to configue a macvlan?
    true?
    i didnt do that at all, i didnt even set a network interface inside OMV
    i gave it a static ip through my unifi controller



    i can do all that if its needed, but you say you dont use dockers at all, maybe i go that way?


    What i actually want


    a pi running:
    - pihole
    - unifi controller
    - home assistant


    thats all
    someone told me to use OMV first and use dockers
    perhaps thats not the best way?


    im not sure, doubting to go further with omv, or just reroll everythin and heading other way using raspbian or hassio
    or whatever?


    edit: when reading further i even see that pihole should not have the same ip as the Omv server running
    is that true? in my case, the raspberry pi has ipadres X but the pihole on it, has the same, thats not good?

    • Offizieller Beitrag

    i didnt do that at all, i didnt even set a network interface inside OMV
    i gave it a static ip through my unifi controller

    That's fine, but Pi-Hole should be set up as per that How-To as it works, but you need to create a MacVlan if you want technical why's I'll tag the author.


    when reading further i even see that pihole should not have the same ip as the Omv server running
    is that true?

    Yes, that's why you are having issues Pi-Hole needs/requires it's own ip address hence the MacVlan.


    in my case, the raspberry pi has ipadres X but the pihole on it, has the same, thats not good?

    No idea sorry, my Pi-Hole install runs on Diet-Pi on RPi but that's all it runs and it uses unbound so to answer the second part it's using the ip I set up for Diet-Pi. To use Pi-Hole within docker on OMV it requires it's own ip address within your network and the only way to assign that ip is through a MacVlan.

  • Ok
    im gonna delete the container en start over


    Couple of questions:
    - here: https://forum.openmediavault.o…ic-NZBGet-ruTorrent-Sona/


    It says i need a docker person. I didnt do that yet. Should i do it? (cause i installed unifi controller also without that
    I need to install all dockers with macvlan?


    - Second when installing pihole, that manual says i need to configure a direct dns server, so i dont have conflicts. But i dont see the settings of the ip4 there. Which ip do i need to fill in?
    Where can i find those settings?

    • Offizieller Beitrag

    It says i need a docker person. I didnt do that yet. Should i do it?

    Only if docker container specifies a PGID and a PUID Pi-Hole does not.


    I need to install all dockers with macvlan?

    No just Pi-Hole


    Second when installing pihole, that manual says i need to configure a direct dns server, so i dont have conflicts. But i dont see the settings of the ip4 there. Which ip do i need to fill in?
    Where can i find those settings?

    System -> Network -> Interfaces


    As you have set OMV's IP through your unifi controller the above may well be blank, I know of the unifi controller;


    Does that run your DHCP
    Does the unifi controller give you the name of OMV's network interface
    To set up the MacVlan it will require the parent interface name -> Page 6 of the howto
    OMV will require a public dns


    I'm going to send a PM to person who created the howto.

    • Offizieller Beitrag

    Suggestion:


    1. Reinstall OMV4 in accordance with this guide. (You can stop anywhere after the initial setup, if you don't want to setup network shares right off of the bat.)
    - At this point, In accordance with the guide's section on OS backup, buy a 2nd SD card and backup your boot drive SD-card.
    2. Install the Docker plugin.
    3. Install Pi-hole in Docker, using this guide. (Don't setup Unbound at this point.)
    - If all is working well backup your new working configuration to the spare SD-card again.
    __________________________________________________________


    Since Pi-hole is controlling DNS for your LAN, the above is the logical order.
    When the above is working properly, then continue with your add-on processes, backing up your SD-card at the successful conclusion of each add-on.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!