Beiträge von Smiggel

    As said before. I had the same issue here. I have PiBox with a Pi4 CM.

    I run the official OMV installation on RaspberryPi OS Lite I believe. I set it up using the instructions on the OMV website. All according to plan. It ran always just fine. Even the updates never caused problems.

    Today I updated from 7.4.x to 7.5.0. After that the Ethernet connection completely disappeared. Had the same issue some others here. I could not ping the NAS and did not see it in the connected device list.

    Eventually I was able to borrow a keyboard. I had a monitor. When I booted the system I noticed that the system boot took really long because it tried to get a network connection. However, it seems DCHP, IPv4 and IPv6 were not set at all. So it took about 2 minutes before the system continued to boot without an ethernet connection.

    I was able to run omv-firstaid. I setup IPv4 and IPv6 (don't use it) for ETH0. Saving took really long too. About two to three minutes too. After it saved I rebooted my device and then I could access the NAS again.

    Hopefully this helps debugging for future updates and other users.

    Same issue here. :(

    Is there any other way to set a config value on the disk? I have a monitor, but no functional keyboard atm. I can mount the drive when I put my PiBox in a different mode and access the files on the disk. Only not remote and through a keyboard.

    same...
    lets wait for an answer in Upgrade to OMV Failed

    Looks like the update aborts because of the files /etc/default/nfs-common, /etc/default/nfs-kernel-server and /etc/nfs.conf


    I suppose what you have to do:

    Code
    sudo rm /etc/default/nfs-common /etc/default/nfs-kernel-server /etc/nfs.conf
    sudo apt-get install -f
    sudo omv-salt deploy run nginx phpfpm

    Thanks for this one! Forgot to mention I needed it, in order to get my packages running again. I indeed had a problem with it.

    Glad to be of help. I pulled the trigger on this upgrade two months ago and other than a few quirks like these two, I am unable to remember if anything else got broken badly enough that I had to post about them.


    What I expect now that OMV 7.0 was officially released just days ago, I suspect a lot of folks were waiting for that commit to do the upgrade and are only now diving in. Hopefully there won't be a flood of problems or some that are more difficult.

    I would expect that these kind of problems would have been fixed as they were reported months ago.. It's too bad, that these problems are still here.

    Excellent. Glad I remember things like this and was able to find the posts.

    I am glad you remember it too! :)

    Docker is up and running now too. All images are running again. That's a huge relief. I was scared I have to start all over again.

    Thank you so much for helping out!

    May or may not be applicable to your architecture, but worth a try. This happened to me too.


    Yes! That worked! :) I can access the admin now.

    Problem is, that I can not login at all. Not through the web interface and not through the ssh terminal.

    Do you have any solution for that? I can only access my data through SMB.

    I ran OMV on a PiBox with OMV flashed on the EMMC

    My OMV upgrade failed:



    The web interface give's an 502 - Bad gateway error when trying to login.

    SSH refuses all the passwords and account.

    How can I login now? Is there any fix for this?

    Same here. Tried the upgrade from 6 to 7.


    After that it exited. I can see the web interface but cannot login because of a 502 Bad gateway error.

    SSH is also no longer working. My key was registered before in OMV 6, but's gone now. Also my password is no longer accepted. :(

    I am trying to setup Vaultwarden on my NAS. I do not want it to be accessible from outside of my home network. So, it only has to run locally or when I am connected to my network at home through VPN.

    I setup a docker environment:


    version: "2.1"

    services:

    vaultwarden:

    image: vaultwarden/server

    container_name: vaultwarden

    volumes:

    - /data/configs/Vaultwarden:/data/

    ports:

    - 8888:80

    restart: unless-stopped


    I can load the web interface, but when I want to create an account, I get the message that the server requires an SSL connection

    Zitat

    This browser requires HTTPS to use the web vault

    Check the Vaultwarden wiki for details on how to enable it

    I only can't seem to figure out how to get it working and can't find a good tutorial online.

    Can someone here tell me how to do it simply or point me to a good tutorial?