On 1/7/2025 at 5:35 PM, jimeez said:

OMG, thank you!

This no longer works for me and the background just shows an X when hovering over it.

On 1/23/2025 at 1:18 PM, Linguafoeda said:

does anyone know how to fix the issue with krusader where it takes 30+ minutes for it to actually load the web UI after starting the docker? i always run into this issue when i restart my server or restart the docker container for krusader, the web UI won't load until i give it 30+ minutes then it starts working.

bump

Hi when i try and change the file association, its doesn't keep and the dialog box continues to pop up. How do i fix this please?

 

Hello! 

 

I seem to have made my Krusader window "slip" up to the top of my browser window and I don't know how to bring it back down. Any help would be appreciated. 

 

 

EDIT: Found the solution here: 

 

Edited May 5, 20251 yr by urbanracer34
resolved.

On 5/5/2025 at 4:26 PM, urbanracer34 said:

Hello! 

 

I seem to have made my Krusader window "slip" up to the top of my browser window and I don't know how to bring it back down. Any help would be appreciated. 

 

EDIT: Found the solution here: 

 

Hallelujah!!!

 

Came here about to ask the same question and saw your post.

Suppose I could have read the pinned posts myself, but who does that?

Just installed binhex-krusader and getting consistently This site can't be reached.

The log states the following with the last line repeated.

2025-06-27 15:42:08,285 DEBG 'start' stderr output:

tint2: systray started

2025-06-27 15:43:18,837 DEBG 'start' stderr output:

192.168.25.10: SSL connection but '/self.pem' not found

I cannot figure out why it will not start. Stopped it, deleted it, re-created it, etc.

9 hours ago, RaidPC said:

192.168.25.10: SSL connection but '/self.pem' not found

your not showing the section regards https cert and key, so either try the url as http, or sort out the cert and key, one or both of them are not found.

I was up to 1am working on this and will try again. An interesting note is the other version in the CA community (Krusader) installed and worked with no issues. So indeed there has to be one unique setting that is different. Only thing I noted was from a video on installing this version is I set the media to /mnt. Basically only change I made to the defaults.

On 6/27/2025 at 5:46 PM, RaidPC said:

Just installed binhex-krusader and getting consistently This site can't be reached.

The log states the following with the last line repeated.

2025-06-27 15:42:08,285 DEBG 'start' stderr output:

tint2: systray started

2025-06-27 15:43:18,837 DEBG 'start' stderr output:

192.168.25.10: SSL connection but '/self.pem' not found

I cannot figure out why it will not start. Stopped it, deleted it, re-created it, etc.

I'm having the same issue, site can't be reached. Did you figure out what the problem is?

It works using http. When opening the WebUI is there any way to default to opening using http instead of https?

Open your template in Advanced View. What is your WebUI set as? Mine is http:

I completely forgot about advanced view. Thanks it works properly now

On 1/23/2025 at 1:18 PM, Linguafoeda said:

does anyone know how to fix the issue with krusader where it takes 30+ minutes for it to actually load the web UI after starting the docker? i always run into this issue when i restart my server or restart the docker container for krusader, the web UI won't load until i give it 30+ minutes then it starts working.

anyone have an update for this?

2 hours ago, Linguafoeda said:

anyone have an update for this?

Just tried it. Started the container, then launched the GUI. Both started in seconds.

6 hours ago, ConnerVT said:

Just tried it. Started the container, then launched the GUI. Both started in seconds.

any idea what could be causing the lag on my end where container doesn't launch until 30mins+ in?

2 hours ago, Linguafoeda said:

any idea what could be causing the lag on my end where container doesn't launch until 30mins+ in?

Are you using storage driver overlay2 for docker by any chance?, if so you probably are hitting this long standing bug/limitation:- https://github.com/docker/for-linux/issues/388

4 hours ago, binhex said:

Are you using storage driver overlay2 for docker by any chance?, if so you probably are hitting this long standing bug/limitation:- https://github.com/docker/for-linux/issues/388

I don't believe so, how would I know if I'm using that? Is it something I unintentionally turned on?

3 minutes ago, Linguafoeda said:

I don't believe so, how would I know if I'm using that? Is it something I unintentionally turned on?

i believe its now available as an option in unraid v7, sadly i cant tell you exactly where it is cos im still on v6, have a look at settings/docker in the unraid web ui it might be in there.

1 hour ago, binhex said:

i believe its now available as an option in unraid v7, sadly i cant tell you exactly where it is cos im still on v6, have a look at settings/docker in the unraid web ui it might be in there.

Docker storage driver:

native

I beleive i'm using just the native one in the docker settings tab. this has been an issue since i was on v6 too, but it takes like 30 mins for me to wait until the noVNC can even access krusader.

19 minutes ago, Linguafoeda said:

Docker storage driver:

native

I beleive i'm using just the native one in the docker settings tab. this has been an issue since i was on v6 too, but it takes like 30 mins for me to wait until the noVNC can even access krusader.

I'm having the same problem - and Docker is set to Native too.

Not only it will take forever for the GUI to come up, there are many times remote atttached directories will not populate either. I'll have to use MC via command line to move things around.

Greetings everyone,

Any ideas/comments?

Thanks

On 7/8/2025 at 11:10 AM, Glonch said:

I'm having the same problem - and Docker is set to Native too.

Not only it will take forever for the GUI to come up, there are many times remote atttached directories will not populate either. I'll have to use MC via command line to move things around.

Seems like I'm having the same issue. I accidentally stumbled over the issue because I only wanted to reboot krusader and noticed that its not coming up again since 1,5h.

On 7/8/2025 at 4:10 PM, Glonch said:

there are many times remote atttached directories will not populate either.

ok so this is interesting, so it might be that the time to start is due to remote mount points or shares being retried until a timeout is hit. if you remove all remote attached directories does the startup time improve?.

6 hours ago, binhex said:

ok so this is interesting, so it might be that the time to start is due to remote mount points or shares being retried until a timeout is hit. if you remove all remote attached directories does the startup time improve?.

FWIW - The link to the remote share was somewhat new and the delay to get into Krusader was already happening.

As a test, I removed the share, stopped Krusader, started Krusader - took ~8 mins for noVNC to display Krusader (stopwatch timing while refreshing).

Logs (I started the docker at 18:52)

text error warn system array login

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 503

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 504

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 505

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 506

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 507

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 508

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 509

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 510

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 511

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 512

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 513

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 514

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 515

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 516

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 517

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 518

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 519

2025-07-27 19:00:38,991 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 520

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 521

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 522

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 523

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 524

2025-07-27 19:00:38,992 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 525

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 526

error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 527

2025-07-27 19:00:38,992 DEBG 'start' stderr output:

error 3: BadWindow (invalid Window parameter) request 2 minor 0 serial 547

error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 548

2025-07-27 19:00:39,255 DEBG 'start' stderr output:

Sun Jul 27 19:00:39 2025

VNCSConnST: closing 127.0.0.1::44980: Clean disconnection

EncodeManager: Framebuffer updates: 6

EncodeManager: Tight:

EncodeManager: Solid: 13 rects, 2.31446 Mpixels

EncodeManager: 208 B (1:44509.7 ratio)

EncodeManager: Bitmap RLE: 1 rects, 1.875 kpixels

EncodeManager:

2025-07-27 19:00:39,255 DEBG 'start' stderr output:

95 B (1:79.0737 ratio)

EncodeManager: Indexed RLE: 4 rects, 3.076 kpixels

EncodeManager: 1.43945 KiB (1:8.37992 ratio)

EncodeManager: Tight (JPEG):

EncodeManager: Full Colour: 2 rects, 3.889 kpixels

EncodeManager: 2.16895 KiB (1:7.01486 ratio)

EncodeManager: Total: 20 rects, 2.3233 Mpixels

EncodeManager: 3.9043 KiB (1:2324.53 ratio)

Connections: closed: 127.0.0.1::44980

ComparingUpdateTracker: 7.14 Mpixels in / 108.504 kpixels out

ComparingUpdateTracker: (1:65.804 ratio)

2025-07-27 19:00:39,269 DEBG 'start' stderr output:

192.168.0.232 - - [27/Jul/2025 19:00:39] 192.168.0.232: Plain non-SSL (ws://) WebSocket connection

192.168.0.232 - - [27/Jul/2025 19:00:39] 192.168.0.232: Path: '/websockify'

2025-07-27 19:00:39,269 DEBG 'start' stderr output:

192.168.0.232 - - [27/Jul/2025 19:00:39] connecting to: localhost:5900

2025-07-27 19:00:39,273 DEBG 'start' stderr output:

Connections: accepted: 127.0.0.1::33266

2025-07-27 19:00:39,278 DEBG 'start' stderr output:

SConnection: Client needs protocol version 3.8

2025-07-27 19:00:39,282 DEBG 'start' stderr output:

SConnection: Client requests security type None(1)

2025-07-27 19:00:39,282 DEBG 'start' stderr output:

VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888

2025-07-27 19:00:39,291 DEBG 'start' stderr output:

VNCSConnST: Client pixel format depth 24

2025-07-27 19:00:39,291 DEBG 'start' stderr output:

(32bpp) little-endian bgr888

12 hours ago, Glonch said:

FWIW - The link to the remote share was somewhat new and the delay to get into Krusader was already happening.

OK two more test for you:

• Set networking to default - if the networking is not set to 'bridge' then please set it back to this then test and report back

• Try with new config - can you edit your existing container and change the host path for /config to something else, then click apply, test and report back

FYI - As you may be able to guess i cannot replicate this issue, krusader starts within 2-3 seconds for me, as i assume it does for most people.