martialblog/docker-limesurvey

Resources managemet issue

Saddamus opened this issue · 11 comments

Hello. I use apache image with reverse proxy from kubernetes ingress. I can not use add / edit resources. Interface does not react, browser displays errors like:
Failed to launch 'kcact:upload' because the scheme does not have a registered handler
Is it proxy related issue ?

Hi, can you provide some details on your deployment? How the Container is deployed and maybe the Ingress configuration?

Hello, I used this hart:
https://github.com/martialblog/helm-charts/tree/master/limesurvey
Ingress: https://github.com/martialblog/helm-charts/blob/master/limesurvey/templates/ingress.yaml
In my case its made by nginx.
What may matter is that ingress does SSL, while deployment is non ssl - I didn't find any settings like "run unencrypted, but think you are ssl".

By resources you mean uploads? Can you describe how to recreate the issue?

Serveys -> Select one from the list -> resources.
There is option to import / export - this works, but menu below to upload, refresh, settings and listing files does not work.
image

My first guess would be the Persistent Volume permissions. If you are using the 5.* Image, it starts as user www-data, could be that the permissions on the volume are not correct.

image

Do you have any other suggestions ? Did you test this with reverse proxy (https) to non https docker apache image ?

It's not loading regardless if if I use reverse proxy or redirect pod to localhost and come over localhost url. This must be general issue. Does anybody else use it ?

Sorry, I haven't have the time for extensive debugging at the moment. We have some example of reverse proxy configuration in the repository, so yes that was tested. However, it's always been tricky with this application finding the right config.

Have you tested the various options for BASE_URL and PUBLIC_URL? Maybe setting the DEBUG option will help gathering some information about whats happening.

Yes, tested these parameters with no result. I just realized that this plugin is not enabled by default. Probably it was switched on by some of my colegues. The code of plugin is from 2014. To make things clear, im talkking about kcfinder - not this import / export stuff, but kcfinder that you can see below import / export on pasted screen at the beggining of this issue. Can you confirm that this plugin works properly on your docker image ?