Still see 4.6.3 after upgrade to 4.7.0

[setevoy2]

After upgrading to 4.7.0 - Firefly III still displays 4.6.3 version used.

Description of my issue:

I have Firefly III running in Docker from my Docker Compose file:

version: '3.2'

services:
  firefly_iii_app_prod:
    image: jc5x/firefly-iii
    environment:
      - FF_DB_HOST=dbHost
      - FF_DB_NAME=firefly_iii_prod
      - FF_DB_USER=firefly_iii_prod
      - FF_DB_PASSWORD=dbPass
      - FF_APP_KEY=appKey
      - FF_APP_ENV=local
      - FF_APP_URL=http://money.domain.org.ua
      - APP_URL=http://money.domain.org.ua
      - TRUSTED_PROXIES=**
    ports:
      - "9090:80"
    volumes:
      - type: volume
        source: firefly_iii_prod_export
        target: /var/www/firefly-iii/storage/export
      - type: volume
        source: firefly_iii_prod_upload
        target: /var/www/firefly-iii/storage/upload
    restart:
      always

volumes:
  firefly_iii_prod_export:
  firefly_iii_prod_upload:

Behind NGINX as reverse proxy with SSL and with MariaDB database on a remote DB server.

Steps to reproduce

1. Stop with docker-compose stop
2. Pull latest image with docker-compose pull
3. Started FF with docker-compose start
4. Executed commands as per documentation:

• docker exec -it fireflyiii_firefly_iii_app_prod_1 php artisan migrate
• docker exec -it fireflyiii_firefly_iii_app_prod_1 php artisan firefly:upgrade-database
• docker exec -it fireflyiii_firefly_iii_app_prod_1 php artisan firefly:verify

But in the bottom still see version 4.63.

On the Administration page after clicking "Check for updates" - I have the "A new version is available. You are running v4.6.13, the latest version is v4.7.0 which was released on January 31, 2018." message, but - I see the Russian language in Options, which was added (afaik) in 4.7.0.

Please click the version number in the right corner of any Firefly III page to get debug information.

This returns me the error:

"Unfortunately, this error was not recoverable. Firefly III broke. The error is:
file_get_contents(/var/www/firefly-iii/storage/logs/ff3-apache2handler-2018-02-08.log): failed to open stream: No such file or directory"

But log files are present in the container:

15:15:00 [root@ip-172-31-43-63 /opt/firefly-iii] # docker exec -ti fireflyiii_firefly_iii_app_prod_1 ls -l /var/www/firefly-iii/storage/logs/
total 20
-rw-r--r-- 1 www-data www-data 866 Feb  1 20:24 ff3-apache2handler-2018-02-01.log
-rw-r--r-- 1 www-data www-data  71 Feb  2 15:59 ff3-apache2handler-2018-02-02.log
-rw-r--r-- 1 www-data www-data  71 Feb  4 20:37 ff3-apache2handler-2018-02-04.log
-rw-r--r-- 1 www-data www-data  71 Feb  5 17:33 ff3-apache2handler-2018-02-05.log
-rw-r--r-- 1 www-data www-data 866 Feb  8 15:14 ff3-apache2handler-2018-02-08.log

[JC5]

You're still on the old version somehow, I have no other explanation. Are you sure the pull command pulled in the latest version?

[setevoy2]

@JC5 Yup, when I did pull - it pulled new layers. Not sure how to check it - tried to find where version is specified but can't find anything not in files, not in database's tables.
Maybe worth to try rm current images and run pull again, although don't think this will change anything.

# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
jc5x/firefly-iii    latest              779189aaebef        9 days ago          681MB
jc5x/firefly-iii    <none>              dbb2bccd8dd7        4 weeks ago         737MB
jc5x/firefly-iii    <none>              62e3933cc995        5 weeks ago         862MB

P.S. And again - I see Russian lang added in Options - and it was added in 4.7, isn't it?

[JC5]

Yes, so somehow you seem to have half an installation?

[setevoy2]

Seems so... :)
Can deleting and pulling image solve it? How safe is it? And - what about volumes - they seem to have some cache - maybe delete and recreate them again? Again - how safe is it - not sure about data stored there.

[JC5]

Strange, strange! Could it already work to restart your entire docker host?

As long as you keep the MySQL container up and running, or back it up as well, you should be fine. But if you're not an advanced docker user this may be asking for trouble.

The page for Preferences, it shows 4.7.0 in the bottom?

It could be all browser cache of course due to your reverse proxy.

[setevoy2]

Well...
I created DB dump to a new database.
Stopped running FF container.
Updated Compose with the new database.
Started FF, and:

# docker exec -ti fireflyiii_firefly_iii_app_prod_4_7_1 php artisan firefly:verify
In Encrypter.php line 195:
The MAC is invalid.  

If try to execute firefly:upgrade-database - have:

In Preference.php line 64:
Could not decrypt preference #5. If this error persists, please run "php ar
tisan cache:clear" on the command line.

php artisan cache:clear doesn't help...

And the bad thing is that I removed the old container and did no backup...

PS Using old APP_KEY also didn't help...

[setevoy2]

Hey! I did it! :D
OK, that was my fail with APP_KEY.
So, I restored DB again, set back APP_KEY from first service (why in hell I changed it at all?), re-created containers - and have 4.7.0 now :-)
Thanks!
As usually - Stackoverflow is my saviour, just googled "The MAC is invalid", found this discussion - and understood what I did wrong :-)

[JC5]

Glad to hear it works! :D