[GH-ISSUE #1681] Error updating to 1.13.1 #1322

Closed
opened 2026-02-27 11:16:31 +03:00 by kerem · 2 comments
Owner

Originally created by @animalillo on GitHub (Feb 23, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1681

Impacted versions

  • Modoboa: 1.13.0
  • installer used: Yes
  • Webserver: Nginx

Steps to reproduce

Install 1.13.0 and update following the steps specified at https://modoboa.readthedocs.io/en/latest/upgrade.html to 1.13.1

Current behavior

Errors appear:

(env) modoboa@mail:~/instance$ python manage.py check --deploy
System check identified some issues:
WARNINGS:
?: (modoboa-amavis.W001) AMAVIS_DEFAULT_DATABASE_ENCODING does not match the character encoding used by the Amavis database.
HINT: Check your database character encoding and set/update AMAVIS_DEFAULT_DATABASE_ENCODING.
?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_BROWSER_XSS_FILTER, and SECURE_SSL_REDIRECT settings will have no effect.

System check identified 2 issues (3 silenced).
(env) modoboa@mail:~/instance$

Expected behavior

No errors shown. Update finishes correctly and is reflected on the web UI

Originally created by @animalillo on GitHub (Feb 23, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1681 # Impacted versions * Modoboa: 1.13.0 * installer used: Yes * Webserver: Nginx # Steps to reproduce Install 1.13.0 and update following the steps specified at https://modoboa.readthedocs.io/en/latest/upgrade.html to 1.13.1 # Current behavior Errors appear: > (env) modoboa@mail:~/instance$ python manage.py check --deploy System check identified some issues: > WARNINGS: > ?: (modoboa-amavis.W001) AMAVIS_DEFAULT_DATABASE_ENCODING does not match the character encoding used by the Amavis database. > HINT: Check your database character encoding and set/update AMAVIS_DEFAULT_DATABASE_ENCODING. > ?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_BROWSER_XSS_FILTER, and SECURE_SSL_REDIRECT settings will have no effect. > > System check identified 2 issues (3 silenced). > (env) modoboa@mail:~/instance$ # Expected behavior No errors shown. Update finishes correctly and is reflected on the web UI
kerem 2026-02-27 11:16:31 +03:00
Author
Owner

@tonioo commented on GitHub (Feb 25, 2019):

@animalillo Those are just warnings, it does not mean your upgrade has failed. Why do you think it has fail?

<!-- gh-comment-id:466932608 --> @tonioo commented on GitHub (Feb 25, 2019): @animalillo Those are just warnings, it does not mean your upgrade has failed. Why do you think it has fail?
Author
Owner

@animalillo commented on GitHub (Feb 26, 2019):

Because it was still displaying the same version on the web UI and the update warning...
I guess i had to open a new session or something was cached out preventing that to update but now it seems to display the proper version number!

Thank you for checking, seems to be workinng and updated.

<!-- gh-comment-id:467575051 --> @animalillo commented on GitHub (Feb 26, 2019): Because it was still displaying the same version on the web UI and the update warning... I guess i had to open a new session or something was cached out preventing that to update but now it seems to display the proper version number! Thank you for checking, seems to be workinng and updated.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/modoboa-modoboa#1322
No description provided.