Trouble installing OMV on pi4 : No access to GUI

  • Hi,


    I've been using omv on a raspberry pi 4 for a few weeks now. However I decided to do a clean install. I followed the exact same method. Found here : Installing OMV5 on Raspberry PI's, Armbian SBC's, & i386 32-bit platforms.
    The Raspian buster lite install worked fine. However after the omv install, which seemed to go well, I could access the gui. I can still ssh the pi. But impossible to access the web gui, it gives me a 502 bad gateway.


    I'm really running out of ideas here.
    Here's what I've tried unsuccessfully:


    - use another browser
    - clear browsing history
    - re do a full clean install
    - use another, new SD card
    - assign another ip to the rasp pi (static)
    - tried omv-firstaid clear cache
    - tried omv-firstaid port set up



    Nothing worked. I am really clueless here. I had used the exact same process for the previous install a few weeks ago and it worked perfectly.


    Any ideas ?

  • I just attempted the install about 3 hours ago and I did it again just now because I could not figure out what the issue was. I made an account on this forum just to say that I am having this exact same issue too.


    I downloaded the latest Raspbian Lite image from the Raspbian website and also verified the SHA-256 hash to make sure it was valid.

    • Offizieller Beitrag

    You guys are tyrants! Your R-PI's should get Christmas day off.
    ________________________________________


    Seriously, there may be a repository problem. I was doing test builds on Armbian where OMV suddenly stopped installing. (It connected to a web page, but it was "Welcome to nginx".)


    I'm in the process of an R-PI test build, but all of you may have to wait until tommorow or the next day. You know what they say, "it" happens.


    I'll post again when the script finishes.

    • Offizieller Beitrag

    Next is a quick 32-bit build to check the box, but,, I'd try again in a day or two. (It's a holiday.)


    In the User Guide, there's a section for cloning SD-cards.
    If you have two cards (and you should have two cards) build until you have a clean install, then clone the card before getting extensively into a config. If something goes wrong, a full rebuild would not be required.

  • I have exactly the same problem too. I'm also using Raspbian buster lite on a RPI 4, with 4Gb, and a 32Gb SD card.


    I used this tutorial: https://github.com/OpenMediaVa…ing_OMV5_on_an%20R-PI.pdf
    Also same process here in video form:

    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.


    After the wget step and a sudo reboot. I am unable to connect to the web interface - same as others have reported. ssh still work afterwards. Not sure how to troubleshoot the web UI. Any clues?


    I also saw a number of Python 3 deprecated warning messages for collections during the last wget stages. Is this a clue perhaps?

  • I'm having the exact same problem as well. Nginx is running but not binding to a port.


    /etc/nginx/openmediavault-webgui.d is empty
    /etc/nginx/sites-enabled is empty
    /etc/nginx/conf.d/ is empty
    /etc/nginx/sites-available contains default


    I know zero about Nginx. ****The virtual host configs****
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;


    Enabled the default site and restart Nginx, Nginx is now binding to port 80.

  • I have exactly the same problem too. I'm also using Raspbian buster lite on a RPI 4, with 4Gb, and a 32Gb SD card.


    I used this tutorial Adden-B-Installing_OMV5_on_an R-PI.pdf!


    first i used the latest image! (2019-09-26-raspbian-buster-lite.zip)
    then there is an image from the archive exactly as in the instructions. (2019-07-10-raspbian-buster-lite.zip)
    with the same result!
    I also used "omv-firstaid" to connect port 80, with the result:
    502 Bad Gateway nginx
    best regards


    uwe from Berlin/de

  • I installed OMV5 on RPi4 yesterday 10AM UTC+1, it worked and I saw the GUI. I had some issues while configuring OMV and had to reinstall it, because I could't connect via SSH after a reboot (I did not get the micro-HDMI cable yet).


    After reinstall (maybe 8PM UTC+1) I can't access the GUI. Since then, I tried flashing the SD and reinstalling OMV like 5 times, because I thought, I am too stupid to properly install it.


    Now I see this thread. Good to know, it's propably not my fault.


    So far, I used this "manual": Link


    After install I can't connect via browser. After configuring the port in omv-firstaid I get the same problem with 502 Bad Gateway nginx.



    I am pretty new to that whole Linux stuff but used a RPi2 with OMV4 very successfully.

  • I have successfully used an RPi3 + and RPI4 1Gb with OMV4.
    Of course I wanted to try OMV5 right away and gave me an RBI4 with 4 Gb for Christmas!


    best regards


    uwe from Berlin/de

  • I'm experiencing the same problem here. Installed OMV5 on Rpi 3B using the "Adden-B-Installing_OMV5_on_an R-PI.pdf" tutorial.


    At first, I couldn't access the webgui at all, but after using "omv-firstaid" to connect to port 80, I got the "501 Bad Gateway" error.


    Used "2019-09-26-raspbian-buster-lite" as host OS on my Rpi 3B.


    I checked the services:


    pi@raspberrypi:~ $ systemctl status openmediavault-engined
    ● openmediavault-engined.service - The OpenMediaVault engine daemon that process
    Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled;
    Active: active (running) since Thu 2019-12-26 13:09:16 GMT; 14min ago
    Process: 853 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS)
    Main PID: 866 (omv-engined)
    Tasks: 1 (limit: 2200)
    Memory: 8.6M
    CGroup: /system.slice/openmediavault-engined.service
    └─866 omv-engined


    Dec 26 13:09:16 raspberrypi systemd[1]: Starting The OpenMediaVault engine daemo
    Dec 26 13:09:16 raspberrypi systemd[1]: openmediavault-engined.service: Supervis
    Dec 26 13:09:16 raspberrypi systemd[1]: Started The OpenMediaVault engine daemon
    lines 1-13/13 (END)
    ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request
    Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2019-12-26 13:09:16 GMT; 14min ago
    Process: 853 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS)
    Main PID: 866 (omv-engined)
    Tasks: 1 (limit: 2200)
    Memory: 8.6M
    CGroup: /system.slice/openmediavault-engined.service
    └─866 omv-engined


    Dec 26 13:09:16 raspberrypi systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request...
    Dec 26 13:09:16 raspberrypi systemd[1]: openmediavault-engined.service: Supervising process 866 which is not our child. We'll most likely not no
    Dec 26 13:09:16 raspberrypi systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    lines 1-13/13 (END)
    ● openmediavault-engined.service - The OpenMediaVault engine daemon that processes the RPC request
    Loaded: loaded (/lib/systemd/system/openmediavault-engined.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2019-12-26 13:09:16 GMT; 14min ago
    Process: 853 ExecStart=/usr/sbin/omv-engined (code=exited, status=0/SUCCESS)
    Main PID: 866 (omv-engined)
    Tasks: 1 (limit: 2200)
    Memory: 8.6M
    CGroup: /system.slice/openmediavault-engined.service
    └─866 omv-engined


    Dec 26 13:09:16 raspberrypi systemd[1]: Starting The OpenMediaVault engine daemon that processes the RPC request...
    Dec 26 13:09:16 raspberrypi systemd[1]: openmediavault-engined.service: Supervising process 866 which is not our child. We'll most likely not notice when it exits.
    Dec 26 13:09:16 raspberrypi systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.



    Nginx is up and running:


    pi@raspberrypi:~ $ systemctl status nginx
    ● nginx.service - A high performance web server and a reverse proxy server
    Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2019-12-26 13:25:55 GMT; 1s ago
    Docs: man:nginx(8)
    Process: 1673 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 1675 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Main PID: 1676 (nginx)
    Tasks: 5 (limit: 2200)
    Memory: 2.9M
    CGroup: /system.slice/nginx.service
    ├─1676 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
    ├─1677 nginx: worker process
    ├─1678 nginx: worker process
    ├─1679 nginx: worker process
    └─1680 nginx: worker process


    Dec 26 13:25:55 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server...
    Dec 26 13:25:55 raspberrypi systemd[1]: Started A high performance web server and a reverse proxy server.


    My root folder has 12G available so space is also not the issue:


    pi@raspberrypi:~ $ df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/root 15G 1.9G 12G 14% /
    devtmpfs 459M 0 459M 0% /dev
    tmpfs 464M 40K 463M 1% /dev/shm
    tmpfs 464M 6.3M 457M 2% /run
    tmpfs 5.0M 4.0K 5.0M 1% /run/lock
    tmpfs 464M 0 464M 0% /sys/fs/cgroup
    /dev/mmcblk0p1 253M 52M 201M 21% /boot
    folder2ram 464M 2.2M 461M 1% /var/log
    folder2ram 464M 0 464M 0% /var/tmp
    folder2ram 464M 0 464M 0% /var/lib/openmediavault/rrd
    folder2ram 464M 732K 463M 1% /var/spool
    folder2ram 464M 0 464M 0% /var/lib/rrdcached
    folder2ram 464M 4.0K 464M 1% /var/lib/monit
    folder2ram 464M 0 464M 0% /var/lib/php
    folder2ram 464M 1.3M 462M 1% /var/cache/samba
    tmpfs 93M 0 93M 0% /run/user/1000



    I've read a thread from 2015 on this forum https://forum.openmediavault.o…ead/7383-502-bad-gateway/, the solution to the same "502 Bad Gateway" error was to install php5-pam_1.0.3-2_armhf package. Could it be possible it's a similar issue this time?


    Edit 1:
    I've checked the Nginx logging /var/log/nginx/openmediavault-webgui_error.log:


    2019/12/26 14:57:50 [crit] 4941#4941: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:192.168.178.164, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "192.168.178.143"
    2019/12/26 14:58:16 [crit] 4966#4966: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:192.168.178.164, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "192.168.178.143"
    2019/12/26 14:58:45 [crit] 4966#4966: *3 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 14:59:15 [crit] 5003#5003: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 14:59:46 [crit] 5025#5025: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 15:00:17 [crit] 5035#5035: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 15:00:47 [crit] 5057#5057: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 15:01:18 [crit] 5072#5072: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"
    2019/12/26 15:02:19 [crit] 5099#5099: *1 connect() to unix:/run/php/php7.3-fpm-openmediavault-webgui.sock failed (2: No such file or directory) while connecting to upstream, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.3-fpm-openmediavault-webgui.sock:", host: "127.0.0.1"


    Since these errors are php errors, I'm suspecting more and more that this issue has something to do with php package.


    Ran command apt list installed | grep php7.3


    php7.3-fpm/stable,now 7.3.11-1~deb10u1 armhf [installed,automatic]


    Does anyone have any idea what the cause can be? Thanks in advance.



    Does anyone know what to do?

    • Offizieller Beitrag

    I think it's that Santa bloke delivering new toys to the grown up's, then parts of the 'net' have had the day off :D

    Hey there! It's Boxing day - don't forget about your colonists. :)

  • I want to add the following.


    Yesterday during the day I could install and run everything, but because I want to start it from SSD I had to install it a lot of times.
    The problems started in the evening. That is when the troubles began and I couldn't start OMV5 again.
    So something happened during the day.


    Now I will go back to OMV4. I still have the image and this is working.

Jetzt mitmachen!

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