FileBrowser plugin: Not reachable at port 3670 although running and accessing share with supposedly sufficient privileges

Solution that worked for me: (i previously had docker/portainer installed, and removed these)

It seemed there were some firewall rules still present in IPTables, so to clear them:

iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -t nat -F
iptables -t mangle -F
iptables -F
iptables -X

for IPv6 this is:

ip6tables -P INPUT ACCEPT
ip6tables -P FORWARD ACCEPT
ip6tables -P OUTPUT ACCEPT
ip6tables -t nat -F
ip6tables -t mangle -F
ip6tables -F
ip6tables -X

restart the host, or restart the filebrowser. You should be fine!

change port to 3671 and Reboot OMV worked for me

I have two installs of OMV on the great Argon EON NAS enclosures and RasPi 4, 8Gig - they work very well!

On both NAS I have installed File Browser through the Plugins feature/menu choice. Both are openmediavault-filebrowser 6.0.7-1 and the arm64 version.

On one NAS I can click on the 'Open UI' tab and I am taken to the File browser web GUI and can log in and work away - great ! love it!

On the other NAS I go though the same process and click on the 'Open UI' tab and the browser opens up a new page but I get the message "This site can’t be reached" and I do not get the login page to enter the File Browser credentials.

I have:-

• uninstalled File Browser and rebooted.
• Reinstalled File Browser and rebooted, enabled and configured. No change - can't get to the login page.
• change the port number to 3671 and rebooted - No change still unable to get to the file browser login page.....

I guess I am missing something but cannot find it. The NAS is working fine and I can get to all shares with Windows File Explorer.

Any Clues?

Thanks

I have 'done good!'

Now both instances of File Browser on two separate Argon EON / RasPi4 8GIG / OMV / 4xSSDs cannot get to the File Browser web GUI and I have absolutely no idea why the second one stopped working or why the other one would not work in the first instance after install (and it seems that in 2.2k views no one else has any ideas - oh well....)

Uninstall Docker Engine

1. Uninstall the Docker Engine, CLI, containerd, and Docker Compose packages:
   Code

   $ sudo apt-get purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras

2. Images, containers, volumes, or custom configuration files on your host aren't automatically removed. To delete all images, containers, and volumes:
   Code

   $ sudo rm -rf /var/lib/docker
   $ sudo rm -rf /var/lib/containerd

I don’t understand why it’s like that. I spent 2 days figuring it out and finally did as above and it worked again.

Perhaps as a friend said, there was a conflict between Podman and Docker

OK, with the hint above I have now restored the file browser functionality.

I did not follow the instructions above. What worked for me was to delete all the containers/files in Compose, then uninstalled Compose and I was then able to access File Browser.

It is a bit of a PITA to now have to recreate the Compose files/containers.... Such is life.

Nope! I just reinstalled Compose and that broke File Browser again!

Yep - I have done it a couple of times - I uninstall Composer and File Browser works. I reinstall Composer and File Browser does not work. I will try the suggestions above.

Another update....... Compose and File Browser cannot be installed together on my system, the way I have installed them. There is some incompatibility.

I give up!

Same here i would love to use both on my machine, but for the moment docker wins.

Simple stop of docker service is not enough to have access to port 3670. This indicates some configuration issue.

I followed votdevs hint and added --iptables=false on the commandline of docker.service.

nano /lib/systemd/system/docker.service

[...]

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/dockerd --iptables=false -H fd:// --containerd=/run/containerd/containerd.sock
ExecReload=/bin/kill -s HUP $MAINPID
TimeoutStartSec=0
RestartSec=2
Restart=always

[...]

systemctl daemon-reload

systemctl restart docker.service

reboot

After this reboot access to all docker containers and to file browser port was possible.

Unfortunately this endangers dockers security concept and could not be the final solution.

Zitat von kamranmiskeen

change port to 3671 and Reboot OMV worked for me

DUDE! I've been struggling for 3 hours! this is it. Saved me

nevermind....still hitting wrong credentials issue. Still, progress