Posts by raulfg3

Hello, my experience until now:

I used for several years swag+ Heimdall to expose my dockers to internet, but recently I discover nginx proxy manager and config & access & manintenance is really better

so first of all, some usefull links:

GitHub - NginxProxyManager/nginx-proxy-manager: Docker container for managing Nginx proxy hosts with a simple, powerful interface

Docker container for managing Nginx proxy hosts with a simple, powerful interface - NginxProxyManager/nginx-proxy-manager

github.com

Nginx Proxy Manager

Docker container and built in Web Application for managing Nginx proxy hosts with a simple, powerful interface, providing free SSL support via Let's Encrypt

nginxproxymanager.com

Nginx Proxy Manager

Docker container and built in Web Application for managing Nginx proxy hosts with a simple, powerful interface, providing free SSL support via Let's Encrypt

nginxproxymanager.com

PD: All my exposed dockers have his own user&password login, and I can define user & password on Nginx proxy manager to protect some dockers that do not have built in password login.

Let's encryt is really easy to generate an maintain too.

my proxymanager.yml for example is:

services:
  proxymanager:
    image: 'docker.io/jc21/nginx-proxy-manager:latest'
    container_name: proxymanager
    networks:
      my-net:
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
      - DISABLE_IPV6='true'
    ports:
      - '70:80'
      - '81:81'
      - '444:443'
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/Dockers/proxymanager:/data
      - CHANGE_TO_COMPOSE_DATA_PATH/Dockers/proxymanager/letsencrypt:/etc/letsencrypt
    restart: unless-stopped
networks:
  my-net:
    external: true

All my dockers run my-net created on omv-compose webGUI in bridge mode

Quote from fbeye

? If there is a crash, is hardware or software better. I don't know.

If crash the RAID controller is best the software RAID, because is independent of the controller, if you use Hardware RAID and your card dies, probably you need a new card equal to the died one

ok, no problem, my mistake to suppose that 7.2.4 have the button.

I'll wait until where it be release, in 7.2.5 I suppose.

sorry , but delete icon is not show:

update 7.2.4 details:

try to change to 64KB , 256B is clearly too low:

ethtool -g eno1
Ring parameters for eno1:
Pre-set maximums:
RX: 256

Hello, Y delete some dockers on my install and still appears on the restore section of compose-plugging, is good, but perhaps, add a delete button so i can delete manually really old or not usefull backups are a good addon.

ej:

please read or show videos how tailscale works.

is not OMV related.

revise BIOS & CRON, and please consider to do a new fresh install of OMV7.

aditionally, you need to know UUID & GUID of your user / files, to assing correctly permission on new OMV, best way is start to create users in order ( first user is always UUID=1000, second created user in webGUI is UUID=1001 , and so on.

what is your NAS IP?.

en other computer in explorer use http://yourNASIP to log in OMV .

if is your first time user is admin and password is openmediavault, try to change to not use default values.

votdev say: Then you can create a new file system on top of the MD device file.

yes, see my signature:

Thread

[HOWTO] create a self signed cert to use HTTPS with multiples CN and IP

I use the well explained method described here:
Spanish https://magmax.org/blog/creand…ntidad-certificadora-ssl/
English https://datacenteroverlords.co…sl-certificate-authority/



more info on: https://support.citrix.com/article/CTX227983


But I modified some things to use SAN: https://geekflare.com/san-ssl-certificate/


1 - Create a private key for CA

(Code, 1 line)



2 - self firm this key for CA

(Code, 1 line)


you generate 3 files on root (I use winSCP to show files):
…

raulfg3

Jun 9th 2019

Quote from BernH

Here is your error

OMV uses NGINX on port 80, but it is wanted by NGINX PROXY MANAGER (not the same as NGINX that OMV uses, they are different softwares). You need to either change the port of OMV to something else, or change the container port of NPM to something else and adjust your router port forwards so that 80 external maps to the NPM port, which the compose file will then remap to 80.

Personally, I just change my OMV port to avoid all the port flipping between the router and NPM container.

I resolve it in the same way that swag do:

I redirect port 443 to port 444 and port 80 to port 90 on the router.

and then use redirection on the proxymanager.yaml file:

eg:

services:
  proxymanager:
    image: 'docker.io/jc21/nginx-proxy-manager:latest'
    container_name: proxymanager
    networks:
      my-net:
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
      - DISABLE_IPV6='true'
    ports:
      - '70:80'
      - '81:81'
      - '444:443'
    volumes:
      - CHANGE_TO_COMPOSE_DATA_PATH/Dockers/proxymanager:/data
      - CHANGE_TO_COMPOSE_DATA_PATH/Dockers/proxymanager/letsencrypt:/etc/letsencrypt
    restart: unless-stopped
networks:
  my-net:
    external: true

more info:

your error : network 1ba61672e8a71ae42804c3221f79284c5f5f3366f38008d0c26061d1b7d1a58a not found

you need to configure OMV-Compose to use your current ethernet NIC :

Try to use

reinstall Docker button.

and check that apropiate driver name is used on macvlan (parent):

Quote from patrick1963

Hello all,

I also have a slow photoprism when i add new photo's (6000+). Which variables should i tweak? (my server has 32 Gb ram)

Greetz: Patrick

please ask this in the photoprism forum.

strange characters on your yaml file.

yaml file espect spaces only, no allowed tabs or other estrange codes.

I use notepad++ to indent my yaml files on windows. please revise your yaml file.

please create first your MacVlan named "RedPiHole" in OMV-compose webGUI:

Then use this stack:

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
# Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
# version: "3"  Version is obsolete on latest compose
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: pihole
    # domainname: $URL                    # <-- Update on enviromen.env file
    networks:
      RedPiHole:                        # <-- MACVlan Name You need to create first in Portainer WebGUI.
        ipv4_address: 192.168.1.2       # <-- Update to your desired Pihole IPv4 I use 192.168.1.2 that is free
# https://www.youtube.com/watch?v=4741-YR31fM
# https://www.youtube.com/watch?v=o7nn6Tv-PAw
    cap_add:
      - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN)  
    ports: 
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
      - "80:80/tcp"
    environment:
      ADMIN_EMAIL: tipitao@youremail.com
      FTLCONF_LOCAL_IPV4: 192.168.1.2   # <-- Update (match ipv4_address of PiHole)
      # VIRTUAL_HOST: pihole.$URL    # <-- Update (match hostname + domainname)
      WEBPASSWORD: !kF%+dI]/}90P<y          # <-- Add password (if required)
      PIHOLE_DNS_: 8.8.8.8;8.8.4.4      # <-- Change by your prefered DNS service like 1.1.1.1
      TZ: Europe/Madrid                 # <-- Your Time Zone here
      IPv6: "false"
# Volumes store your data between container upgrades
    volumes:
      - '/Nvme/Dockers/Pihole:/etc/pihole'
      - '/Nvme/Dockers/Pihole/dnsmasq.d:/etc/dnsmasq.d'    
#   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped

networks:
  RedPiHole:
    external: true

good luck.

If works fine, your Pihole must have 192.168.1.2 as IP, and you can configure your router to use it to serve by DHCP to other devices like TV, Phones, etc... BUT not for your OMV install.

OMV must be in static mode or at least have his own DNS resolver like 8.8.8.8

PD: I´m from Madrid so if still have problems send me a PM.

sorry i do not see advanced settings in your screen shots:

please read my post, perhaps can help: RE: [HOWTO] install PIHOLE on OMV using portainer WEBGUI on a MacVlan

MacVlan MUST be created on OMV-Compose webGUI PRIOR to use it on pihole docker.

pues parece bastante claro: tienes problemas en el disco /dev/sdd1 tendrás que ejecutar un fsck manual y si no lo soluciona, pensar en una nueva instalación.

PD: También podría venir el problema del disco de algún problema previo de la placa/cable SATA, etc...