Beiträge von Toho531

  • Nextcloud online with lets encrypt & SSL

    Zitat von Zeb Aztian

    Noch hab ich keine Daten auf Nextcloud also wenn es da eine Installation gäbe sehr gerne :)

    - Hierbei müsstest du als Image (hinter docker.io) nextcloud:fpm angeben.

    - Ports werden nicht freigegeben

    - Aber viele Containerpfade gemeapped:

    Jeweils die zweite Zeile musst du anpassen.

    /var/www/html/custom_apps

    /srv/dev-disk-by-label-config/config/nextcloud/www/html/custom_apps


    /var/www/html/data

    /srv/dev-disk-by-label-Raid/nextcloud/data


    /var/www/html/themes

    /srv/dev-disk-by-label-config/config/nextcloud/www/html/themes


    /var/www/html

    /srv/dev-disk-by-label-config/config/nextcloud/www/html


    /var/www/html/config

    /srv/dev-disk-by-label-config/config/nextcloud/www/html/config

  • Nextcloud online with lets encrypt & SSL

    Zitat von Zeb Aztian

    Hi Morlan,


    ok wie mache ich das denn? Habe mir gerade das Portainer Manual mal angeschaut aber nichts gefunden

    D.h. ich muss nextcloud und Letsencrypt verbinden?

    Lege in Portainer ein neues Netzwerk an. Einfach Name angeben und als Driver bridge auswählen. Dieses neue Netzwerk musst du nextcloud und portainer zuweisen.

  • Nextcloud online with lets encrypt & SSL

    Schade ist, dass du den "normalen" nextcloud container benutzt. Mit dem Fpm-Container habe ich deutlich bessere Erfahrungen gemacht, weil dann nicht ein Webproxy auf den anderen weiterleitet.

  • Nextcloud online with lets encrypt & SSL

    Du gehst hier aber auch über Port 8080. Ich nehme mal an, dass in Portainer 8080 auf 80 gemapped ist. Die Zertifikate von letsencrypt sind aber beim Port 443 relevant. Wie sieht hier das Mapping aus?

  • Nextcloud online with lets encrypt & SSL

    Laufen letsencrypt und nextcloud jeweils in Docker Containern?

    Hast du deinen Router konfiguriert, damit die Ports von außen ins interne Netz weitergeleitet werden?

    Und welche Meldung bekommst du im Browser?

  • Wechsel von Raspberry 3 auf Raspberry 4

    I've done the same: switching from Pi3 to Pi4. Please consider to install a 64bit OS because the official Raspberry OS's is only 32 bit even the hardware is 64bit. Especially if you want to install php based stuff like Nextcloud you should habe a 64bit OS to avoid upload file size limits.

    Here's what I'm using:

    https://github.com/openfans-co…offical/Debian-Pi-Aarch64


    If you switch the OS adding existing storages without data loss isn't a problem.


    Best regards

  • Error applying notification settings

    Hi folks,


    After saving notification settings I have to apply them. This leads to the following error:


    Python
    [tt]
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run mdadm 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import Iterable, Mapping, namedtuple raspbian: ---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 14:58:10.122292 Duration: 1.206 ms Changes: ---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm is in the correct state Started: 14:58:10.123881 Duration: 113.535 ms Changes: ---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 14:58:10.237841 Duration: 34.126 ms Changes: ---------- diff: --- +++ @@ -23,4 +23,3 @@ MAILFROM root # definitions of existing MD arrays -ARRAY /dev/md/ETNAS:Mirror metadata=1.2 name=ETNAS:Mirror UUID=c4139c41:955a4e95:cb171f21:d17e9f49 ---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 14:58:10.274084 Duration: 325.003 ms Changes: ---------- pid: 5352 retcode: 0 stderr: stdout: ---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 14:58:10.600330 Duration: 16.947 ms Changes: ---------- pid: 5354 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout: Summary for raspbian ------------ Succeeded: 4 (changed=3) Failed: 1 ------------ Total states run: 5 Total run time: 490.817 ms
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run mdadm 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/modules/file.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working from collections import Iterable, Mapping, namedtuple raspbian: ---------- ID: remove_cron_daily_mdadm Function: file.absent Name: /etc/cron.daily/mdadm Result: True Comment: File /etc/cron.daily/mdadm is not present Started: 14:58:10.122292 Duration: 1.206 ms Changes: ---------- ID: configure_default_mdadm Function: file.managed Name: /etc/default/mdadm Result: True Comment: File /etc/default/mdadm is in the correct state Started: 14:58:10.123881 Duration: 113.535 ms Changes: ---------- ID: configure_mdadm_conf Function: file.managed Name: /etc/mdadm/mdadm.conf Result: True Comment: File /etc/mdadm/mdadm.conf updated Started: 14:58:10.237841 Duration: 34.126 ms Changes: ---------- diff: --- +++ @@ -23,4 +23,3 @@ MAILFROM root # definitions of existing MD arrays -ARRAY /dev/md/ETNAS:Mirror metadata=1.2 name=ETNAS:Mirror UUID=c4139c41:955a4e95:cb171f21:d17e9f49 ---------- ID: mdadm_save_config Function: cmd.run Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf Result: True Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run Started: 14:58:10.274084 Duration: 325.003 ms Changes: ---------- pid: 5352 retcode: 0 stderr: stdout: ---------- ID: mdadm_update_initramfs Function: cmd.run Name: update-initramfs -u Result: False Comment: Command "update-initramfs -u" run Started: 14:58:10.600330 Duration: 16.947 ms Changes: ---------- pid: 5354 retcode: 127 stderr: /bin/sh: 1: update-initramfs: not found stdout: Summary for raspbian ------------ Succeeded: 4 (changed=3) Failed: 1 ------------ Total states run: 5 Total run time: 490.817 ms[/tt]


    Do you have any idea how to fix that mess?


    Thank you very much

  • Omv5 and Letsencrypt plugin

    I found a great video regarding letsencrypt docker / portainer configuration:

    Externer Inhalt www.youtube.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.


    It's in french but even if I can't spreak french it's better unterstandable than many english videos. :)



    Now the question is just how to link the pem files to OMV. In case I re-new the certificates OMV should use them automatically.

  • Omv5 and Letsencrypt plugin

    Great answer! Thank you.


    Found the files in /config/letsencrypt/etc/letsencrypt/live/<><domain.name>/


    I don't wanted to use a folder on my data drives because for me this is all configuration stuff :)

  • Omv5 and Letsencrypt plugin

    Next question is: There is no folder /etc/letsencrypt so I cant't access the files:

    Code
    root@OMV:~# cd /etc/letsencrypt
bash: cd: /etc/letsencrypt: No such file or directory
root@OMV:~#


    In portainer container configuration I added the following volumes:

    /config/letsencrypt - /config


    One again - any ideas?