Posts by Rayman

  • Can't access anymore Portrainer webinterface

    Yes, I was able to solve it...


    Did the following steps:


    1.

    Code
    docker stop portainer

    2.

    Code
    docker rm portainer

    3.

    Code
    docker run -d -p 9443:9443 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce


    Went into the WebUI and turned off force ssl.

    The problem here was, that the port for SSL is not active within OMV Extras. Will this be changed? It only maps the ports 8000:8000 and 9000:9000 but not 9443:9443.

    Maybe can be added in further releases.

  • Can't access anymore Portrainer webinterface

    Quote from Zoki

    How are you accessing your server?


    The name of the error message (at least in chrtome) is misleading. it may well be that you are talking to a non existing server / port.

    Internal IP adress, everything else is working, also the containers, but not portrainer over the same port like before.


    http://192.168.10.45:9000


    So it has to do witht he force SSL and I try now to find the config, where it is located to turn off the force ssl.


    Output of docker container ls




    Code
    CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                   PORTS                                                                                                                                                                                                      NAMES
bc358dbe9b11   portainer/portainer-ce         "/portainer"             4 minutes ago   Up 4 minutes             0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp, 9443/tcp                                                                                                             portainer

  • Can't access anymore Portrainer webinterface

    Hello all together,


    I changed today the ssl setting to force ssl without giving any kind of certificates to it.

    Now I can't access it anymore and always getting an website timeout "ERR_CONNECTION_REFUSED".


    I used to install it via OMV and tried to remove it and reinstall it again - no luck, still can't access it.

    Any chance to change to config? I was not able to find it somewhere for portrainer and have no luck in accessing it :(


    Thanks,

  • Wireguard - Connects but no Internet

    Well... It was like 99% of cases the problem in front of the configuration page... I set the opening ports on the wrong device, now its working :)

    I used the QR Code.

    Thanks!


    Btw.: is there any kind of usefull good GUI for Wireguard?

  • Wireguard - Connects but no Internet

    Hello,

    I just installed WIreguard and struggeling already a few hours with Wireguard installation via Portainer. I can connect to Wireguard, but get no internet back from my VPN/can't browse any webpages.


    Thats the config:


    This is my Stack



    This is my wg0 conf:




    Thats the log from portainer:



    I can't see any errors in there, can you do?


    Thanks in advanced :)

  • Offset Error at installation

    Hello together,


    after I had some problems from upgrading 3.x to 4.x I thought why not an fresh install.


    I tried to install OMV 4.X from an USB Stick to my SSD. But I always get an error at the "one or more drives found" installation screen. After that I get an "deb/sda1" can't get mounted to "/"..... Offset Error 3584 bytes.





    Then: "Do you want to format the drive" I click on yes, but it won't get me into the partition menu.


    Are you able to help me?
    With an normal Debian 9 Installation all is going well and I can get into the partition menu.



    Anwsers in german or english :)



    Thank you for your help,



    ----------------------------



    Guten Morgen,


    ich versuche seit Ewigkeiten OMV 4 zum laufe zu bringen.
    Doch leider erhalte ich immer wieder eine Offset startet bei 3584 bytes Fehlermeldung:





    Wenn ich auf "Ja" klicke komme ich keinen Schritt weiter. Kann mir jemand helfe?
    Eine Debian 9 Installation geht ohne Probleme durch.


    Viele Grüße

  • Can't mount RAID10 "more filesystems detected"

    Hello folks,


    I upgraded a few days ago from OMV 3.* to OMV 4.
    But now I can't mount anymore my RAID10. Do you have any sugesstions?







    Error of sudo mount /dev/md0 /srv/dev-disk-by-label-Raid10


    Code
    sudo mount /dev/md0 /srv/dev-disk-by-label-Raid10
mount: /dev/md0: more filesystems detected. This should not happen,
use -t <type> to explicitly specify the filesystem type or
use wipefs(8) to clean up the device.


    This is the blkid output:


    Code
    root@NAS-Server:~# blkid
/dev/sdc: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="01cdd2a3-b86b-691b-a213-b5ca3cbd878c" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sdb: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="48c7850e-4c34-6651-7bb2-8224c4062565" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sda1: UUID="0a228258-4d3a-4cfe-b87e-b837f4f19183" TYPE="ext4" PARTUUID="c66cdb84-01"
/dev/sda5: UUID="b3c59904-4ca4-49f1-80c1-ec4998c43471" TYPE="swap" PARTUUID="c66cdb84-05"
/dev/sde: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="2c0c01de-3547-50aa-d14c-b77b426ae2a7" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sdd: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="ba632853-5ba6-3b24-b0f0-245c66d33fa8" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"


    Code
    root@NAS-Server:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid10 sdd[4] sde[0] sdb[3] sdc[2]
15627790336 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
bitmap: 0/117 pages [0KB], 65536KB chunk


unused devices: <none>


    Output of: sudo mdadm --detail /dev/md0



    Should work, shouldn't it?


    Would be awesome to get help!


    Have a good day,

  • Problem after upgrading - no omv installation found


    Thank you!!!! This did indeed help. I needed to remove apache and nginx did worked again :)


    The only thing which does not yet work is my RAID. Somehow I can't mount it anymore?




    This is the blkid output:

    Code
    root@NAS-Server:~# blkid
/dev/sdc: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="01cdd2a3-b86b-691b-a213-b5ca3cbd878c" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sdb: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="48c7850e-4c34-6651-7bb2-8224c4062565" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sda1: UUID="0a228258-4d3a-4cfe-b87e-b837f4f19183" TYPE="ext4" PARTUUID="c66cdb84-01"
/dev/sda5: UUID="b3c59904-4ca4-49f1-80c1-ec4998c43471" TYPE="swap" PARTUUID="c66cdb84-05"
/dev/sdd: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="d939cc33-0157-cae7-2fa5-813087994cfe" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"
/dev/sde: UUID="10ee0e11-06f4-bdcc-2402-7b704ab53d25" UUID_SUB="2c0c01de-3547-50aa-d14c-b77b426ae2a7" LABEL="NAS-Server:RAID10" TYPE="linux_raid_member"


    Should work, shouldn't it?

  • Problem after upgrading - no omv installation found

    Hello folks,


    I got an problem with OMV.
    I updated from omv3 to omv4 with the usual upgrade command. After I upgraded I got the following error:



    Apache is running. I can't access OMV throught the website. But the data is still there in www.
    I also cant start the nginx server. It got an error:


    Code
    collectd[977]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)



    Anything I can do? My OMV backup is pretty old and when I try to run any OMV command I get:


    Code
    root@NAS-Server:~# omv-release-upgrade
-bash: omv-release-upgrade: Command not found.


    Can anybody help me? I dont know any further.


    Good day,
    Rayman

  • Problem after configurating sabnzbd as proxy http

    Quote from Sc0rp

    Re,

    Wie hast du das gemacht/versucht?


    DIrekt über das Webinterface gibt es einen Button. DIesne habe ich halt genutzt. SABNZBD war schon eingerichtet.


    Quote from Rayman

    Doch leider gab es wohl einen Fehler und ich kann weder auf OMV noch auf das SABNZBD Interface drauf zugreifen. Kann mir wer helfen?


    omv-firstaid ... stellt i.d.R. das Netzwerk wieder her, sodass der Zugriff auf die OMV-WebGUI wieder gegeben ist.
    Sry, no time 4 english translation ...


    Sc0rp
    [/quote]


    Das kommt:


    Code
    ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr
/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf sabnzbd setsettings 2>&1' 
with exit code '1': nginx: [emerg] invalid number of arguments in "proxy_set_hea
der" directive in /etc/nginx/openmediavault-webgui.d/sab.conf:4


    EDIT:
    Network repair brachte etwas.


    Danke!

  • Problem after configurating sabnzbd as proxy http

    Hallo Liebe Community,


    ich nutze OMV schon etwas länger. Nun wollte ich SABNZBD als http_proxy laufen lassen, sodass ich ohne Port aufs Webinterface drauf zugreifen kann.
    Doch leider gab es wohl einen Fehler und ich kann weder auf OMV noch auf das SABNZBD Interface drauf zugreifen. Kann mir wer helfen? :)


    Vielen Dank!



    Hello,


    I just configured SABNZBD with as using proxy_http.
    After enabeling it and restarting the server I cant access anymore OMV, sabnzbd webpage etc.


    Any idea where I can reverse these changes?