I am using Debian 12 with latest docker version.
There is portainer as a UI available.
I am also running Apache2 as a reverse proxy for RC
LiveChat is configured in version 7.3.3. and working.
I have tested and checked logs but there is no obvious reason to find, that explains why the livechat wouldn’t work anymore.
The chat icon itself has been modified in the RC-settings which means, that I replaced the logo and changed the position to be on the left side.
These settings does not apply anymore after updating from 7.3.3 to any later version!?
Is there some kind of cache to be cleaned up prior to fire the new version up!?
What licence? = starter, so basically no support but as mentioned: When using 7.3.3 no issues occur. When changing . env & docker.yml to use 7.7.4 (latests) and firing that one up, chat icon on website is there but states, that the offline form is unavailable. And internally, when logging in to RC via Browser or using the App, the livechat icon is green an active. Am I really the only one?! Interesting…
How many users? = 10
No real cache to clean.
I would rm all old containers to cleanup a bit.
Most likely issue is firewall/reverse proxy (always) = I understand that but sounds confusing, since RC 7.3.3 works with all the firewall settings and apache2 reverse proxy but when stopping container and switching to 7.7.4. the icon on website is present but states offline form unavailable and so on.
I cannot change a running reverse proxy server if RC 7.7.4. seems to have an issue with the offline form.
Check on the browser using the live chat and see what errors it shows.
= I am trying to set up a staging environment to see what happens.
Can I post a link of a screen recording here ? A link will no be removed?
I am modern and would like to provide a video of the issue.
This is described in the docs (and I wrote the original). Rocket do not test big version jumps… Each one usually has db changes.
For a peaceful life and easier debugging do 7.3.x > 7.4.x etc and check changelogs thoroughly as you go. Use the latest release of each eg 7.3.4 > 7.4.2 etc Check the tags for the correct version.
(I have one installed and upgraded from something like 0.30 - it has step upgraded through each release, even if I have actually missed using one or two)
Also note downgrading is a very bad idea. Because of the DB changes. Backup/restore is the only way to do it. Especially on big jumps like you tried.
With 10 users you don’t need anything complex. Personally I run a separate test version on a small vm & test website. I can use an almost duplicate setup to my main and test.
That I don’t know. Check changelogs as there are frequent changes. Unlikely to be related to your connection issue.
“Modern” ? Hmmm.
You can, but it isn’t going to fix anything. We already know basically what your issue is.
The answers almost certainly lie in your Rocket history, browser and apache logs. The “old” but still current hard yards of debugging.