File browser issues after updating to 6.4.0-1 / 6.4.0-2

  • Hello


    After updating to 6.4.0-1 resp. 6.4.0-2 the file browser plugin does not work anymore.


    OMV runs on a Raspberry Pi 4 with file browser plugin 6.0.4.-1 enabled.


    Port is 3670 and forwarded by the router. Certificate had been enabled.


    File browser worked fine under these parameters until the update(s).


    The UI link in the file browser settings does not point to the IP address followed by the port 3670 anymore, but to MyIP/#/services/filebrowser. Adding the port manually does not help. The browser results in an error message stating that the address isn't available.


    Any idea why this happens?


    Cheers


    Juergen

  • Output ip a


    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

    valid_lft forever preferred_lft forever

    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether dc:a6:32:d9:3c:d8 brd ff:ff:ff:ff:ff:ff

    inet 192.168.178.102/24 brd 192.168.178.255 scope global dynamic eth0

    valid_lft 863842sec preferred_lft 863842sec

    inet6 fd00::dea6:32ff:fed9:3cd8/64 scope global dynamic mngtmpaddr noprefixroute

    valid_lft 7045sec preferred_lft 3445sec

    inet6 fe80::dea6:32ff:fed9:3cd8/64 scope link

    valid_lft forever preferred_lft forever

    3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether dc:a6:32:d9:3c:d9 brd ff:ff:ff:ff:ff:ff

    4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 02:42:d9:b6:a4:5d brd ff:ff:ff:ff:ff:ff

    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

    valid_lft forever preferred_lft forever

    inet6 fe80::42:d9ff:feb6:a45d/64 scope link

    valid_lft forever preferred_lft forever

    5: vethc4cae716@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 02:72:6d:68:4f:c3 brd ff:ff:ff:ff:ff:ff link-netns cni-1cf4cb89-3931-d453-b648-febe27942d35

    inet 172.16.16.1/32 scope global vethc4cae716

    valid_lft forever preferred_lft forever

    inet6 fe80::72:6dff:fe68:4fc3/64 scope link

    valid_lft forever preferred_lft forever

    7: vethef3cc42@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default

    link/ether b6:02:2f:fd:88:2d brd ff:ff:ff:ff:ff:ff link-netnsid 1

    inet6 fe80::b402:2fff:fefd:882d/64 scope link

    valid_lft forever preferred_lft forever


    Output podman ps -a


    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

    f72aeafdd015 k8s.gcr.io/pause:3.2 About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp dc2b8f8386ab-infra

    ec216b5c3e1c docker.io/library/caddy:latest caddy run --confi... About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp filebrowser-proxy

    e0c96ac9c489 docker.io/filebrowser/filebrowser:latest About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp filebrowser-app

  • Please, use codeboxes when posting outputs:

    Code
    Output podman ps -a
    
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
    f72aeafdd015 k8s.gcr.io/pause:3.2 About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp dc2b8f8386ab-infra
    ec216b5c3e1c docker.io/library/caddy:latest caddy run --confi... About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp filebrowser-proxy
    e0c96ac9c489 docker.io/filebrowser/filebrowser:latest About an hour ago Up About an hour ago 0.0.0.0:3670->8443/tcp filebrowser-app

    Everything looks correct so, what happens when you open a browser, on the same LAN with:

    https://192.168.178.102:3670



    And, are you running anything on docker?

    docker ps -a

  • votdev

    Added the Label OMV 6.x
  • Weird, I seem to be having the same exact issue.


    Same as OG, all is standard.

    ;


    Code
    docker ps -a
    CONTAINER ID   IMAGE                           COMMAND        CREATED        STATUS          PORTS                                                           NAMES
    4aab54daf21e   jwetzell/guacamole              "/init"        40 hours ago   Up 45 minutes   0.0.0.0:9001->8080/tcp, :::9001->8080/tcp                       guacamole-guac2-1
    d4d0952782a4   portainer/portainer-ce:latest   "/portainer"   40 hours ago   Up 45 minutes   8000/tcp, 9443/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp   portainer
  • The suggestion that worked for him, did not for me.


  • I am actually having the same issue. I just installed the FileBrowser plugin for the first time after updating (on 6.4.3-1). On the first attempt it crashed during install so I uninstalled and rebooted my OMV device. On the second go, it installed fine but when I go to open the web ui, it times out. I ran the command posted above and that did not resolve my issue either.


    ip a


    podman ps -a

    Code
    CONTAINER ID  IMAGE                                     COMMAND  CREATED         STATUS             PORTS                   NAMES
    7a439206b90b  k8s.gcr.io/pause:3.2                               15 minutes ago  Up 15 minutes ago  0.0.0.0:3670->8080/tcp  ebdd9f28fd04-infra
    668adb8c943c  docker.io/filebrowser/filebrowser:latest           15 minutes ago  Up 15 minutes ago  0.0.0.0:3670->8080/tcp  filebrowser-app


    docker ps -a

  • Well this may be a coincidence or a glitch or whatever, but I resolved it this way.


    Everything was updated.. Everything was patched, and everything was correct and configured PERFECT (I can prove this in a moment). Nothing I did would filebrowser load, just timed out.


    Because I was trying to get my ZFS plugin to work, I was told I had to install the proxmox kernel. I did so, rebooted, and for shyts n giggies I clicked OPENUI for filebrowser, BAM it worked.

    What reason would FB only work under the proxmox? Just a glitch or is there something else going on?

  • Well this is weird, though FB loads and from within I create a new user, it will not let new user, or even admin/admin make any changes, says "403 Forbidden".


    I went in and added user to the permissions for that drive.... It is still owned by root but I gave read/write to the user.

    I noticed during install it made filebrowser uer but under OMV/Users, I do not see filebrowser user.

  • Never thee mind, found this, works now.


Participate now!

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