[Support] binhex - Krusader


Recommended Posts

Posted (edited)

So I've been using Krusader for ages without making any active changes, but I'm running into this error today:

 

noVNC encountered an error:

 

http://((SERVER)):6080/app/webutil.js

readSetting@http://(SERVER):6080/app/webutil.js:150:30 initSetting@http://(SERVER):6080/app/ui.js:710:27 initSettings@http://(SERVER)):6080/app/ui.js:131:12 start@http://((SERVER)):6080/app/ui.js:57:12 prime/<@http://((SERVER)):6080/app/ui.js:45:27

 

I was running 6.8.3, so I upgraded to 6.9.3; same error.

 

I ran a force update on binhex-krusader; same error.

 

Has anyone else run into this? I was using it to transfer files less than a week ago, and absolutely haven't changed anything sense (outside of running a successful parity check yesterday). Any ideas on ways to resolve would be greatly appreciated!

 

 

tower3-diagnostics-20220510-1114.zip

Edited by wheel
Attached Diagnostics
Link to comment
  • 2 months later...

I'm trying to set this up and after 2 clean installs, I just cannot seem to make this work. There are no errors or logs that would be useful but I can't connect using WebUI button:
 

```

This site can’t be reached

<internal IP? refused to connect.

```

 

None of my other containers are using 6080 port.

 

Anyone else seen this and how do I fix this?

Edited by Howboys
Link to comment
On 7/17/2022 at 2:17 PM, Howboys said:

I'm trying to set this up and after 2 clean installs, I just cannot seem to make this work.

How long are you waiting after the container is started? I've noticed an extended startup time needed, sometimes close to a minute or more.

Link to comment
19 hours ago, JonathanM said:

How long are you waiting after the container is started? I've noticed an extended startup time needed, sometimes close to a minute or more.

 

Just tried again and waited 7 minutes and same result. This is all I see in the logs:

 

2022-07-18 22:07:36.185241 [info] System information Linux 757f3f29298e 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-07-18 22:07:36.213199 [info] OS_ARCH defined as 'x86-64'
2022-07-18 22:07:36.244516 [info] PUID defined as '99'

 

EDIT: I let the container sit overnight and now the UI works fine. So it takes somewhere between 7 minutes and 9 hours for the container to be fully functional. :)

Edited by Howboys
Link to comment
  • 4 weeks later...

Any idea why extracting (at least 7z) is SUPER slow with this docker? (at least in my setup)

And by slow I mean slow even for UNRAID.

It is way faster to open the 7z (that resides on the array) over network on my Windows PC and extract it to the USB disk I want, than opening the same 7z in krusader "locally" and extracting to same USB disk mounted directly (with unassigned devices plugin) to my server.

 

Any ideas?

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.