HELP with App semi-broken after upgrading to 3.11.5

rfernandez

Hi,
I'm running on Docker in a VPS.
I was in 10.6.
In my development environment I had upgraded to 11.2 a while ago.
I tried to deploy a new version of the app to the VPS (10.6), and it told me I had to upgrade r3 version to be able to upgrade.
I tried to do so, but I discovered 11.2 is no longer available.
I did the upgrade to 11.5.

[+] Building 129.9s (11/11) FINISHED
 => [internal] load local bake definitions                                                                                             0.0s
 => => reading from stdin 621B                                                                                                         0.0s
 => CACHED [internal] load git source https://github.com/r3-team/r3_docker.git#main                                                    0.2s
 => [internal] load metadata for docker.io/library/ubuntu:25.04                                                                        0.3s
 => CACHED [1/5] FROM docker.io/library/ubuntu:25.04@sha256:27771fb7b40a58237c98e8d3e6b9ecdd9289cec69a857fccfb85ff36294dac20           0.0s
 => [4/5] ADD https://rei3.de/downloads/REI3_3.11.5_x64_linux.tar.gz .                                                                 6.9s
 => [2/5] RUN bash -c 'mkdir -p /opt/r3/data/{certificates,files,temp,transfer}'  && apt-get update  && apt-get install imagemagick  118.4s
 => [3/5] WORKDIR /opt/r3                                                                                                              0.8s
 => [4/5] ADD https://rei3.de/downloads/REI3_3.11.5_x64_linux.tar.gz .                                                                 0.5s
 => [5/5] RUN tar -xvf REI3_3.11.5_x64_linux.tar.gz r3 config_template.json  && sed -i "s/localhost/r3_db/g" config_template.json  &&  3.5s
 => exporting to image                                                                                                                 5.0s
 => => exporting layers                                                                                                                4.7s
 => => writing image sha256:bfb973c8daf7d6cd3fc8c737006cd085a238e44dc8cc94957a574d7e311fdabe                                           0.1s
 => => naming to docker.io/library/r3:3.11.5                                                                                           0.1s
 => resolving provenance for metadata file                                                                                             0.0s
[+] Running 3/3
 ✔ r3                     Built                                                                                                        0.0s
 ✔ Container r3.11.5_db   Started                                                                                                      3.7s
 ✔ Container r3.11.5_app  Started

After the upgrade but before applying the new version of the app, something unexplainable happened.
The application took the header, colors, title, etc. from another application I have running on the same server (in a different docker container).

I know it sounds nonsense, as each application has its own database, and are on separate directories, but that is what happened.
Also the Configurations page in my user profile shows blank (no configuration at all)

I have other applications running on the same server, and none of those showed similar behavior.

After this, I tried applying the new version of the app (the one I had on development environment), and it applied the changes to the functionality of the application. However the UI customization remained changed, and the Configuration page continues to show nothing.
I would really appreciate your thoughs on this, and if there is a way to solve it (at least make the Configuration page show values again)

Thank you!

gabriel

I am sorry, but I personally will not support deeper Docker issues as my Docker skills are very limited and it takes forever to troubleshoot. If anyone else wants to take a crack at it, please feel free.

Personally I would redo the containers and recover a backup - this is usually faster than trying to troubleshoot the issue in any specific Docker environment.

rfernandez

I really don't think this is a Docker issue.
In this scenario Docker is a collateral fact. I described it in detail to provide a clear scenario.
This looks like a building issue, because what the yml does is to build the image from the git repository and step over the previous version, it doesn't use a pre-built image.
What I'm getting in the browser console is a plain vue error, about an unhandled exception.

Never mind. I understand your point.

However I have to unmess whatever happened, and it would be of great help if you are so kind to just point me to the code files/database relations involved in the display of the Configuration screen and its values. That will reduce my guesswork significantly.

Thank you!

gabriel

rfernandez What I'm getting in the browser console is a plain vue error, about an unhandled exception.

Web files (like vue.js) are merged into the r3 binary during compilation. This makes upgrades quite robust, as there is just a single file to update. If you are having vue errors, you could post them and then we could see if we can learn something from that.

rfernandez if you are so kind to just point me to the code files/database relations involved in the display of the Configuration screen and its values. That will reduce my guesswork significantly.

I am not sure what you mean by "Configuration screen" - the screenshot kinda looks like the personal user settings. There are dozens of relations connected to the user. Going through them individually is not going to help as the r3 database must be consistent to work correctly - either it works and the DB is fine or the DB is broken and r3 would not boot. As mentioned before, r3 only is a single file - so trying to identify and fix files connected to the user settings screen does not work.

From the described symptoms it sounds much more like a borked browser cache. If the r3 binary is broken, the service does not start. If the DB is so broken that you need to look at relations, the service would very likely not start - unless you somehow selectively deleted data.

If the r3 service successfully boots and is reachable, you should be able to login. If not, you should at least see errors in the browsers console log.

lsw-fabian

rfernandez Had a cache issue a while ago, that looked pretty similar (multiple instances on one server) but after a cache reset the issue was gone.

rfernandez

gabriel It is indeed the user preferences screen.
I see. That eliminates a lot of paths.
So the problem must be somewhere else, as the app starts ok and I'm able to log in.

I'll give the problem some space to see if I can come up a fresh perspective.
Thank you!

rfernandez

lsw-fabian Hi Fabian,
Thank you very much for you comments.
By cache you refer to browser cache, or some other cache?

lsw-fabian

rfernandez Yes, i just wiped the browser cache