Posts by TooGoooD

I've been using OMV since version 4 and on every major OS upgrade, I've looked in to other options and have never found a reason to switch. OMV does what its designed to do. throw in the plugins and the possibility is endless. it is progressively getting better also, i remember major OS upgrades were a mess in the past. now its fairly painless. I always recommend it to people over the other ones.

Thanks for all the hard work. it's appreciated!

Quote from jonebarker

There is a improved fork called FileBrowser Quantum which you can try. They also list the closest competitors and feature comparisons. Runnning via docker is much more flexible especially for mounting multiple directories.

i have seen that but it is in early stage of development and according to the dev it is not ready for production servers. but it looks like it has some new added features that look promising. if copyparty had a server UI it would be hands down the winner IMO.

🆘 Need Maintainers · filebrowser filebrowser · Discussion #4906

Hello! I have stepped down from this project a long time ago, and @o1egl has been maintaining it for years. However, none of us have as much time as we used to…

github.com

personally I always set up MOBAxterm to SSH in to the server and use the built in file browser, but i did find the FileBrowser app helpful during new installs for a quick fix until I get around to setup proper SSH keys.

are there any plans to replace this app now that is being discontinued?

looking at this comparison of the different available apps seems like a few decent options are available. https://github.com/9001/copypa…ovudstraum/docs/versus.md

Hello i am using SWAG to provide a SSL Cert to OMV and ran in to a Problem i am trying to find the best solution for.

To give you a bit of a background I am using SWAG with DNS wildcards, to provide certs to all the docker apps I am running.

everything is working as it should, I can access the OMV web Ui through omv.media.domain.com and all my apps that need to be open can be accessed through *app.media.domain.com

problem with this setup is when updating docker through the web UI, once docker goes down and forces a restart of SWAG the browser loses connection to the OMV web UI mid update. the site there for is inaccessible through omv.media.domain.com and the page errors out with a 503 server not accessible code. i am still able to connect to the server by the servers IP:Port address while it is inaccessible through the DNS address.

is this the draw back of using SWAG to provide OMV a ssl cert? or is there a work around?

this is my SWAG config file:

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    http2 on;

    server_name omv.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth (requires ldap-location.conf in the location block)
    #include /config/nginx/ldap-server.conf;

    # enable for Authelia (requires authelia-location.conf in the location block)
    #include /config/nginx/authelia-server.conf;

    # enable for Authentik (requires authentik-location.conf in the location block)
    #include /config/nginx/authentik-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable for ldap auth (requires ldap-server.conf in the server block)
        #include /config/nginx/ldap-location.conf;

        # enable for Authelia (requires authelia-server.conf in the server block)
        #include /config/nginx/authelia-location.conf;

        # enable for Authentik (requires authentik-server.conf in the server block)
        #include /config/nginx/authentik-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app 10.*.*.*;
        set $upstream_port ****;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above.
    }

    # REMOVE THIS LINE BEFORE SUBMITTING: Some proxies require one or more additional location blocks for things like API or RPC endpoints.
    # REMOVE THIS LINE BEFORE SUBMITTING: If the proxy you are making a sample for does not require an additional location block please remove the commented out section below.
    # location ~ (/<container_name>)?/api {
    #     include /config/nginx/proxy.conf;
    #     include /config/nginx/resolver.conf;
    #     set $upstream_app <container_name>;
    #     set $upstream_port <port_number>;
    #     set $upstream_proto <http or https>;
    #     proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    #
    #     # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above.
    # }
}

not breaking, and the update completes successfully. This is more of an FYI than anything.

this is the log of the pop up window of the web UI update management.

Setting up Salt environment ...
/usr/lib/python3/dist-packages/salt/utils/http.py:8: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13
  import cgi
/usr/lib/python3/dist-packages/salt/utils/jinja.py:9: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()
/usr/lib/python3/dist-packages/salt/grains/core.py:2711: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead
  ) = locale.getdefaultlocale()

you need to go from 5 to 6 once on 6 and you do a full update, do a 6->7 , can not go from 5 to 7 directly.

see this guide for how to set up your folders so all your apps can read and have access to them with out having to continually copy files. there are many guides on how to set up each app properly to work with this folder structure to not have any read/write issues.

https://trash-guides.info/Hardlinks/How-to-setup-for/Docker/

Hello the first line of your log informs you of the problem.

Quote

Code

Initramfs unpacking failed: 2STD-compressed data is corrupt 

sometimes bad RAM can cause this issue, have you tried to run a memtest?

Quote from votdev

If there is any useful information that could be displayed, you can be sure that I would have already included it in the user interface.

also receiving these notices right as i log in to omv, first thing in the day, there is never any option to attach to a process as its most likely exited already. However the notification lingers on and can confuse the user. possible fix would be to remove the notification if the background process has already finished.

try changing the port, then restart OMV, the default port seems to be used already, i haven't ran tests to see what is causing the problem, but after changing the port and restarting I was able to load the login page for file-browser.

any chance to add a feature request to add a Loading order to the containers?Some containers are dependent on others to be fully loaded prior to starting.

Hello everyone,

seems like there's been an update! have read this thread and also the two guides to get docker compose set up and working here:

Thread

Guide: Using the new docker plugin

This is for those of you struggling with the new docker plugin. It should hopefully help you transition to the new plugin, with the eventual goal of transitioning away from Portainer (the idea of the new plugin is to keep everything contained in the OMV webUI, and make support more consistent).

If you are transitioning from an install with the old plugin, verify where your containers are stored on your system. As root or sudo, execute the following command

(Code, 1 line)

and record the path in…

KM0201

May 30th 2023

with out issues and also the WIKI guide to get portainer back :

omv6:omv6_plugins:docker_compose [omv-extras.org]

Thank you for both of the write ups as they were helpful to understand and get everything in order.

however the portainer container quickly went in to an endless restart loop.

looking at the logs:

portainer | 2023/06/03 05:53PM FTL github.com/portainer/portainer/api/datastore/migrator/migrate_ce.go:101 > the Portainer database is set for Portainer Business Edition, please follow the instructions in our documentation to downgrade it: https://documentation.portaine….0-be/downgrade/be-to-ce/ |

The portainer example YAML is pulling from the Community Edition repo and anyone that has upgraded to the free edition of the Business Editon will be experiencing the same.

Solution:

either manually edit the example yaml and upload it.

or if you already installed the CE image:

under Services->Compose->Files

Click the portainer container to turn the background colour yellow.

click stop, to stop the container.

click Edit while still selected this should open up the yaml file and change the line image: portainer/portainer-ce:latest to  image: portainer/portainer-ee:latest  

save

click the pull button to download the correct image.

click the UP Arrow to start the image/portainer.

Ii'm sure there is a faster way but the steps remain the same.

Just wanted to say Thanks, the upgrade from 4 to 5 went smoothly with this script, the only issue i had was the old quota system was not loading because the new Systemd version was already loading it. quick google search solved this issue and now i'm on the latest and greatest as they say.

i'm looking for suggestions on how to get this to work. would like to add a shared folder on the file=server as an external drive in next cloud.
i would rather not open ports on the file-server to the WAN and go through the openvpn server on the Router and LAN to connect to next cloud.

next cloud does have a plugin for external storage that gives access to a number of protocols to connect to an external storage.

any suggestions/idea's are appreciated.