Mirror not valid?

  • Not sure how to do that. I forgot to post the following apparently:

    Okay. I tried TrueNAS Core and it worked fine. I am guessing that Debian may not be able to handle server motherboards or something. I wasn't able to set up my rackmount with OMV either in a previous post, though that was because of a DOA SAS PCIE controller. It makes no sense otherwise.

    Basically I can get TrueNAS to work out of the box, but not OMV. I also think there is something wrong, but the only thing I can think of is the server motherboard causing issues. TrueNAS, which typically is used on server hardware, has no issues. People are probably not using this kind of equipment for their servers. A pro CPU, server motherboard, and ECC RAM are very atypical. I will be switching to TrueNAS scale for better software support so I can try to debug whatever is happening. Just let me know what steps you want me to take.

    I'll check tomorrow and see if I can find out.

  • Tried both Firefox and Brave. Along with https://192.168.50.192:80/ in case they were too stupid to go to the port. Firefox at least gives me SSL_ERROR_RX_RECORD_TOO_LONG, which going off of forums means that the SSL was not configured properly or has expired?

    Of course it fails, normal https port is 443. Default is for OMV WEbUI to be accessed via http port 80. The nmap output shown in #13 looks normal for a fresh install of OMV. So not wishing to contradict anything crashtest has said, but by just using http://192.168.50.192 when you had reached the stage of #17 above may have shown you had a working OMV install.


    If things were still not working as expected, then the key services to check are running at the OVM CLI post-install are both nginx and php-fm. Sorting out network config post-install can be done at the CLI using omv-firstaid. You have the luxury of using the separate BMC/IPMI NIC on this board for installs, so I don't understand why you started by using a wireless connection, as this is often problematic for installs.


    Out of interest, which m/board do you have? Is it the X570D4I-2T or X570D4I-NL? This ITX sever m/board may not be in common use with OMV, but there are plenty of people who've install OMV on other server m/board both supermicro and asrock rack.

  • Of course it fails, normal https port is 443. Default is for OMV WEbUI to be accessed via http port 80. The nmap output shown in #13 looks normal for a fresh install of OMV. So not wishing to contradict anything crashtest has said, but by just using http://192.168.50.192 when you had reached the stage of #17 above may have shown you had a working OMV install.


    If things were still not working as expected, then the key services to check are running at the OVM CLI post-install are both nginx and php-fm. Sorting out network config post-install can be done at the CLI using omv-firstaid. You have the luxury of using the separate BMC/IPMI NIC on this board for installs, so I don't understand why you started by using a wireless connection, as this is often problematic for installs.


    Out of interest, which m/board do you have? Is it the X570D4I-2T or X570D4I-NL? This ITX sever m/board may not be in common use with OMV, but there are plenty of people who've install OMV on other server m/board both supermicro and asrock rack.

    I swear to god it is always the stupidest crap that you overlook. Yeah. Now it decides to work. Do you know if https will be supported in the future?

    Since it looks like TrueNAS removed apt which I kinda need, at least this will make things much easier. Thank you so much!

  • I swear to god it is always the stupidest crap that you overlook. Yeah. Now it decides to work. Do you know if https will be supported in the future?

    Since it looks like TrueNAS removed apt which I kinda need, at least this will make things much easier. Thank you so much!

    You can switch OMV webUI to 443 https only under "System| Workbench".

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!