Changing color of list or swimlane not possible when Wekan is behind a reverse-proxy and using URL-Path

[RowhamD]

Issue

If I access my Wekan-installation "directly" with the ip-address of the internal server, there is no color-change-problem.

But if I access the very same installation through my nginx-reverse-proxy and if there is an additional path in the URL, I can not change the color of a list or a swimlane anymore.

Server Setup Information

• Did you test in newest Wekan?: v6.38
• Did you configure root-url correctly? yes - see below
• Deployment Method (Snap/Docker/Sandstorm/bundle/source): Docker-Image from quay.io
• What webbrowser version are you using? Firefox 91.0

Reproduction Steps

• make basic setup via docker-image especially with: - ROOT_URL=http:https://<internal-ip>:<port>/
• access wekan via http:https://<internal-ip>:<port>/
• color-changing will work correctly

change to reverse-proxy:

• docker-compose down
• edit docker-compose.yml: - ROOT_URL=https://yourdomain.de/path/
• docker-compose up -d
• access wekan via https://yourdomain.de/path/
• color-changing of cards still works
• color-changing of lists and swimlanes does not work anymore

part or my nginx-conf:
    location /path {
      proxy_pass          http:https://<internal-ip>:<port>;
      proxy_set_header    Host               $host;
      proxy_set_header    X-Real-IP          $remote_addr;
      proxy_set_header    X-Forwarded-For    $proxy_add_x_forwarded_for;
      proxy_set_header    X-Forwarded-Host   $host;
      proxy_set_header    X-Forwarded-Server $host;
      proxy_set_header    X-Forwarded-Port   443;
      proxy_set_header    X-Forwarded-Proto  https;

Logs

Docker-logs are silent when this problem occurs.

The access.log of my nginx-reverseproxy shows maybe something interesting:
There is the line

<ip> - - [<date>] "GET /pwa-service-worker.js HTTP/1.0" 404 153 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0"

between many other lines like

<ip> - - [<date>] "GET /path/sockjs/info?cb=z8trkurnwd HTTP/1.0" 200 79 "https://yourdomain.de/path/b/G5cGznHx5dzbLWRZR/admintest" "Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0"

Obviously there is a call to "/pwa-service-worker.js" which is returned with a "404".

Maybe the correct call should point to "/path/pwa-service-worker.js"?

Maybe there is at least one line in the Wekan-code which is not respecting the "ROOT_URL"-setting correctly when generating the calls for the "pwa-service-worker.js"?

Maybe #4376 is related to this?

[As this is my first port here: Many thanks for this great piece of software and for all the work with it!]

[xet7]

There are still bugs with sub-path/sub-url. Using domain or subdomain works.

[cautiouscoyote]

Any chance this is going to be debugged anytime? Since there has been no dialogue here for over one-and-a-half year now.

Seeing the same behaviour here with a subfolder path, running on Ubuntu, using snap. No Docker.
WeKan version as reported in the webUI: 6.09.0.
This is "latest/stable" as reported by the "snap info wekan" CLI command.

Coloring is secondary of course, but I wonder what else is broken this way...
Switching to domain or subdomain is not an option for me.

[xet7]

@cautiouscoyote

I have designed WeKan Studio to fix this and some other issues. Sometime all WeKan platforms will be upgraded to WeKan Studio.

[cautiouscoyote]

@cautiouscoyote

I have designed WeKan Studio to fix this and some other issues. Sometime all WeKan platforms will be upgraded to WeKan Studio.

OK, cool. So I suppose a number of issues can be better solved by starting over from scratch, right.
This 'WeKan Studio' however seems very, very new and little info is available as of yet.
Can you elaborate on the roadmap for this project?
How solid do you expect that "sometime" to be? I suspect we should not hold our breath for it, right ;)

Thanks for all the effort and support though!

[cautiouscoyote]

Interestingly, I noticed recently that coloring of columns and swimlanes does indeed stick when using Chrome/Chromium/Brave as a browser, while it does not when using Firefox.

Also, when changed colors in Chrome/Chromium/Brave and then dowing a page refresh in Firefox, the new colors show in the latter as well.