New to Unraid, and I just installed the Krusader Docker and I am getting an error: Protocol Not supported by Krusader. I am using /mnt/ for the /media path.

 

6 minutes ago, springsman said:

New to Unraid, and I just installed the Krusader Docker and I am getting an error: Protocol Not supported by Krusader. I am using /mnt/ for the /media path.

 

screenshot / more details might be in order to put some reference to what you are saying

Please see screenshot attached.

This is the Docker setup

 

Edited December 7, 20187 yr by springsman
updated screengrab

I have been trying to get this to work for quite a while now, but still get the same error. Any ideas?

 

The only place I see anything about Protocols is in the screengrab attached. Not sure where to go from here.

4 minutes ago, springsman said:

I have been trying to get this to work for quite a while now, but still get the same error.

What, exactly, are you trying to accomplish when this error occurs?

Krusader does not show me any of the shares or files. Just the Protocol error. The screengrab attached is all I get.

 

might be useful then to also post your diagnostics

This is the log I just pulled:

 

Dec 7 21:13:14 Homenet-Unraid kernel: docker0: port 2(vethfad639d) entered disabled state
Dec 7 21:13:14 Homenet-Unraid avahi-daemon[12120]: Withdrawing address record for fe80::1c8a:8aff:fed8:27da on vethfad639d.
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered blocking state
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered disabled state
Dec 7 21:13:16 Homenet-Unraid kernel: device vethfe47e86 entered promiscuous mode
Dec 7 21:13:16 Homenet-Unraid kernel: IPv6: ADDRCONF(NETDEV_UP): vethfe47e86: link is not ready
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered blocking state
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered forwarding state
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered disabled state
Dec 7 21:13:16 Homenet-Unraid kernel: eth0: renamed from vethd9caef1
Dec 7 21:13:16 Homenet-Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfe47e86: link becomes ready
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered blocking state
Dec 7 21:13:16 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered forwarding state
Dec 7 21:13:17 Homenet-Unraid avahi-daemon[12120]: Joining mDNS multicast group on interface vethfe47e86.IPv6 with address fe80::30d5:9ff:fea6:926f.
Dec 7 21:13:17 Homenet-Unraid avahi-daemon[12120]: New relevant interface vethfe47e86.IPv6 for mDNS.
Dec 7 21:13:17 Homenet-Unraid avahi-daemon[12120]: Registering new address record for fe80::30d5:9ff:fea6:926f on vethfe47e86.*.
Dec 7 21:21:55 Homenet-Unraid kernel: vethd9caef1: renamed from eth0
Dec 7 21:21:55 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered disabled state
Dec 7 21:21:55 Homenet-Unraid avahi-daemon[12120]: Interface vethfe47e86.IPv6 no longer relevant for mDNS.
Dec 7 21:21:55 Homenet-Unraid avahi-daemon[12120]: Leaving mDNS multicast group on interface vethfe47e86.IPv6 with address fe80::30d5:9ff:fea6:926f.
Dec 7 21:21:55 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered disabled state
Dec 7 21:21:55 Homenet-Unraid kernel: device vethfe47e86 left promiscuous mode
Dec 7 21:21:55 Homenet-Unraid kernel: docker0: port 2(vethfe47e86) entered disabled state
Dec 7 21:21:55 Homenet-Unraid avahi-daemon[12120]: Withdrawing address record for fe80::30d5:9ff:fea6:926f on vethfe47e86.
Dec 7 21:21:59 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered blocking state
Dec 7 21:21:59 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered disabled state
Dec 7 21:21:59 Homenet-Unraid kernel: device veth1e10a28 entered promiscuous mode
Dec 7 21:21:59 Homenet-Unraid kernel: IPv6: ADDRCONF(NETDEV_UP): veth1e10a28: link is not ready
Dec 7 21:21:59 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered blocking state
Dec 7 21:21:59 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered forwarding state
Dec 7 21:21:59 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered disabled state
Dec 7 21:22:00 Homenet-Unraid kernel: eth0: renamed from vetha3b85af
Dec 7 21:22:00 Homenet-Unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1e10a28: link becomes ready
Dec 7 21:22:00 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered blocking state
Dec 7 21:22:00 Homenet-Unraid kernel: docker0: port 2(veth1e10a28) entered forwarding state
Dec 7 21:22:01 Homenet-Unraid avahi-daemon[12120]: Joining mDNS multicast group on interface veth1e10a28.IPv6 with address fe80::1099:84ff:fe92:b0f1.
Dec 7 21:22:01 Homenet-Unraid avahi-daemon[12120]: New relevant interface veth1e10a28.IPv6 for mDNS.
Dec 7 21:22:01 Homenet-Unraid avahi-daemon[12120]: Registering new address record for fe80::1099:84ff:fe92:b0f1 on veth1e10a28.*.

8 minutes ago, springsman said:

This is the log I just pulled:

 

That's not the diagnostics.  There's other files within the zip which may also be of use.  Also wouldn't hurt to additionally post the logs from Krusader

I am not familiar on where to pull these on this system. From within Krusader all I get is what I have posted in the Screengrab.

Tools - Diagnostics.  For the Krusader logs, see the first linked post in the Real Docker FAQ which will tell you how to grab them.

OK. I think the two attached files are what you are asking about.

homenet-unraid-diagnostics-20181207-2154.zip

Log for_ binhex-krusader.htm

Did you fix this? (Can't tell if this error was regarding the Krusader container or not though)

 invalid volume specification: '/mnt/disks/:UNASSIGNED:rw,slave': invalid mount config for type \"bind\": invalid mount path: 'UNASSIGNED' mount path must be absolute"

 

That is an SSD that I have in Unassigned Devices. It is not being used by anything at the moment.

But did you fix that entry in the template?  If yes, then at least binhex now has all the required info for him to be able to help with the actual problem.

I unmounted the SSD and restarted Krusader. Still the same error regarding Protocol.

This is what I have in the Krusader Settings. It does not refer to the SSD anywhere. Unless you mean some other Setting in another area.

Hi!

New to all this so please bear with me...

New install of unraid (v6.6.6) and new install of krusader. I can't see the WebUI?!

I can use the ip address... And I get: Directory listing for /

I click the vnc.html and the noVNC shows up.

 

I try to install binhex-emby, and the WebUI shows in that one.

 

Big thanks in advance!

33 minutes ago, MadMartigaN said:

Hi!

New to all this so please bear with me...

New install of unraid (v6.6.6) and new install of krusader. I can't see the WebUI?!

I can use the ip address... And I get: Directory listing for /

I click the vnc.html and the noVNC shows up.

 

I would remove the container, then reinstall it from the Apps Tab (do NOT use the Previous Apps section).  Your template on the flash drive is messed up / or you've changed it such that it no longed has the WebUI entry

16 hours ago, springsman said:

I unmounted the SSD and restarted Krusader. Still the same error regarding Protocol.

 

from your screenshot i can see you have switched privileged off, this is required for this container, please set it back to on (the default) and then retry.

Thank you. That did the trick. On the video from Spaceinvader1 (for the older Krusader version) it showed as Privileged as Off. thanks again for the reply.

6 hours ago, Squid said:

I would remove the container, then reinstall it from the Apps Tab (do NOT use the Previous Apps section).  Your template on the flash drive is messed up / or you've changed it such that it no longed has the WebUI entry

Thanks for your time!

 

I didn't touch anything on the flash drive?

I removed everything about binhex-krusader and a new docker.img. Reinstall it in a new folder. Unfortunately same problem?!

22 minutes ago, MadMartigaN said:

Reinstall it

How are you reinstalling.  What you saying with the app not having the webUI on the drop down doesn't make a ton of sense.