Posts by bbddpp

    I think you did a good job. Plus there are so many permutations of server out there and they all have their issues. I am using OpenMediaVault which is seems has some of its own quirks.

    I'm having a few issues that maybe you can clue me in on. I'm new to the world of port forwarding and I have a weird double router situation going on but I am having some strange issues with my local IP when I try and access nextcloud.

    All I am trying to really do is access it locally, without having to use my DuckDNS, and that seems to be failing for some reason after running these container scripts. I am sure this is user error.

    I figured I'd go to https://LOCALIP:457 and see my NextCloud admin backend. I just see a "welcome to your swag instance" page. I believe that also happens when I go to https://DUCKDNSADDRESS:457. I can't seem to find ANY way to get back to the nextcloud admin backend (only the standard settings screen you see as an admin USER if that makes sense).

    I also figured I'd go to http://LOCALIP:80 or just https://LOCALIP and browse my nextcloud locally. That also doesn't work. This must be a port forwarding issue here.

    I'll share this link here for anyone who stumbles upon my issue. This info helped me fix my issue with large file sizes. I believe it has to do with timeouts set on nginx either on the letsencrypt side or the nextcloud side.…tsenrcypt-unraid/71375/10

    What is not mentioned in many tutorials for newbs (like me) is that these are 3 separate apps here, and all 3 have their own cofig files buried deep in the docker appdata folders. So if you are having trouble, make sure you are in the right config file for the right docker. This one is (1) nextcloud (2) mariadb and (3) swag. Both nextcloud and swag have some manual config file work to do to speed it up and fix some other issues, and I may tweak some more but I've learned that getting into these files and making some changes can be very helpful.

    I think we just need to make sure we are clear with which dockers' configs are changed, you did a pretty good job at that in your walkthrough, I have seen some areas that just say "modify the nginx proxy config" instead of being very clear what the file path and filename would be, etc, that kind of stuff is always helpful!

    KM0201, thank you again!

    I got it, thanks again for the post. I'm having a lot of other issues with Nextcloud regarding uploads and downloads of large files, but I am trying to work through all the manual config and issues that seem to need done here. I'm not really effectively seeing great logging yet so trying to turn all that on as well.

    What happened with the docker-compose is just that it never quit at the end of the script, I just ended the ssh window and it was fine (instead of doing a CTRL-C which deleted all the containers).

    All in all, things are up and running anyway. I just need to now figure out the speed issues and more importantly the manual config changes needed so that files larger than 1 GB that I am trying to share out via sharelinks don't fail at the recipient end. There must be a reason that's happening and a config change I am missing, even though I have added a lot of stuff from help guides on resolving such issues.

    Thanks again for getting me this far, your post was the easiest and best to use I have seen to get all this running quickly.

    Hey I got this ALMOST working by forwarding 80 and 443 back to the main router from the Verizon one. So, progress.

    Only issue is the docker compose script huge RIGHT at the end after "Server ready" - everything looks to be running but the compose didn't end gracefully. Did I miss a step or a command on my compose up or compose.yml file?

    This intrigues me for sure. Before I go that crazy. I set up IIS on port 80 on my desktop. Theoretically then if I forward 80 to 80 any on both the DMZ router (FIOS providing the WAN) and the real router (USG) and got port 80 open is that progress?

    So far, I have been stuck forwarding a port from the USG into the FIOS router and getting that router to forward it out to the world sadly.

    Thanks, wasn't ready to sleep so been cracking at it. Thanks for being honest. I had a feeling this was a problem since I was 99% sure I had the port forwarding set up right on my router.

    I do have access to the other router, but putting the port forwards in there a second time (they were there on both routers then) didn't work unless there's a secret sauce. I needed to keep my Verizon FIOS router in for WAN signal only, I use my USG to manage my network. So I was doing the port forwards on the USG but they were likely getting stuffed at the FIOS router on the way out.

    If you know a config I can make to make the forwarding make it up all the way that would be great. The only thing the Verizon router was doing so far was acting as a passthrough for my WAN and the USG's static WAN I assigned was in its DMZ to allow that to work.

    Thanks, figured it out. That was the easier part than the port forward it seems. The compose doesn't seem to be able to get out to see what it needs to see despite having my router set up. I will try again tomorrow. My router is behind a second router as a DMZ (long story, not double NAT tho) and I'm wondering if the port forwards aren't making it out through the DMZ.

    I have to thank you all for this, I think this is the best thread on installing this I have seen. I have one request / issue though.

    I am still on OMV4 (I know, I know, just too scared to upgrade in place and lose things).

    Can the above stacks be translated into docker-compose commands that I can run on OMV4? I have a ton of other dockers running and stood up AdGuard this way with just a very long docker-compose and have to imagine this is possible since I don't have the magic that is OMV5 and portainer.

    Thanks all, great thread.

    OMV4, used another thread here to attempt to install Home Assistant with Supervisor ( and it failed. Attempts to now remove the docker result in this error. Any help on how I can get this docker to go away?

    Error #0:
    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; docker rmi ab17f27e217b' with exit code '1': in /usr/share/php/openmediavault/system/
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/ OMV\System\Process->execute()
    #1 [internal function]: OMVRpcServiceDocker->deleteImage(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('deleteImage', Array, Array)
    #4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Docker', 'deleteImage', Array, Array, 1)
    #5 {main}

    John, were you able to preserve your dockers or anything else when you started over? I'm considering doing the same thing and just saying the heck with trying to upgrade in place. It sounds a bit problematic. Hopefully future OMV versions won't be so different that an upgrade in place works, but it sure looks like too many changes under the hood from 4 to 5 to make this one as joyful a task.

    That said, I love how this software continues to grow and get better all the time! You guys rock.

    Both excited and scared about this given that I have held off dealing with 5 at all with my stable 4 install and all my dockers.

    That said it is time.

    I'm thinking since I can preserve all my data from my dockers, I can (hopefully?) not have to start over with all my plugins like radarr, sonarr, and plex using the config I have saved from the dockers with portainers. Hopefully I am thinking along the proper lines here.

    If that's the case, it seems like starting with a fresh omv5 install and manually adding my drives back in will be the CLEANEST way to do this -- Note I don't use any RAID or zfs pool at all, each drive is separate without any redundancy, because I am crazy and hate wasting space.

    Other than the crazy approach to the data, is my head in the right place otherwise? Just seems cleaner (though maybe more dangerous) to install on a fresh formatted SSD then re-install my dockers using portainer and just manually put humpty dumpty back together again, rather than try and upgrade on top. Which admittedly seems potentially problematic and not necessarily the ideal way to move from OMV4 to OMV5.

    And by the way massive thanks to everyone for continuing to maintain for free to less, what I have found to be the absolute best solution for me for serving my home.

    This must be an issue recently introduced in OMV v4 that appears after a reboot, I see a couple other posts from others with this issue, and I still can't figure it out.

    My problem very similar to this thread however slightly different results (or I am slightly further along).

    Failed to start networking

    I also have 2 hardwired Ethernet interfaces, also seeing a docker0 interface, which does have some (not my domain) IPs getting assigned to it when

    Raise network interfaces, the error did show to me on an earlier boot, I've noticed in subsequent boots it has gone away, and the interface raise seems to be happening. I have even got as far as not seeing the "No network interfaces exist" error go away on the console login screen, however I think it's just getting fooled into thinking docker0 is an active interface. Running omv-firstaid and answering no to both the IPV4 and IPV6 questions for eth0 to re-set it active does not seem to have made a difference.

    I have run the flush command on eth0 as suggested. My eth0 port on the back of my server is lit up like crazy so I know it's getting data in from the router as always.

    ifconfig -a shows docker0 first, with IP some weird addresses, followed by eth0, eth1, lo, and vethc5460f2 as other interfaces, and none of these have IPs.

    What other commands or file content can I share (may need to be screenshots, I can't think of an easy way to get text off of something I can't see on my network)...Would love to get running again.


    Few more things I tried with no luck.

    - Changed cable to eth1 port, and ran omv-firstaid to change default from en0 to en1. Port shows as 1000 GB and ON, still gets no IP.
    - Flushed eth1 and restarted networking. Networking service restarted, no IP granted to eth1.
    - Added my previously set static IP to hosts file even though I realize this is not needed or may do nothing, rebooted, no IP.
    - Changed routers completely (used different router).
    - Changed network cables.

    Something has happened that has caused OMV/debian to no longer want to dole out an IP address to this machine despite it verifying connectivity. I'm up for any ideas on what else I can try here. All the others who had this issue seem to have reinstalled from scratch as that's the only fix. I really don't want to do that. I haven't backed up my OS settings in forever and really don't feel like starting fresh.

    There has to be some other stuff I can try.

    Putting an SSD into my OMV system, standalone drive just to hold my Plex library data folder (not media) because Plex is getting slow.

    How can I format this SSD to ext4 but using a blocksize of 512K so I'm not wasting space? The plex DB has so many tiny files it's taking up triple the space it needs to at 4096K blocksize (500GB on disk vs around 150 actual GB of data).

    Is this as simple as unmounting the file system and running a shell command on the empty volume and remounting?


    Title pretty much says it all. Manual grabs or forcing an automatic search seems to work. Automatic searching (used to be every 30 minutes give or take) using Radarr or Sonarr to check the sources for new releases (I have been using has stopped working as of around 4 days ago. Anyone know what I might be able to do?