Issues upgrading to 5.3

Admin Talk Upgrade
1

I upgraded from 5.2 to 5.3 and followed the extra steps here: Extra Upgrade Notices - SeaTable Admin Manual

The issue is when ever i start the server and try to hit its url i get:

Page unavailable

Sorry, but the requested page is unavailable due to a server hiccup.

Our engineers have been notified, so check back later.

Looking at the logs the only thing i see is:

[2025-09-01 11:36:18] [ERROR] log.py[line:241] Internal Server Error: /
Traceback (most recent call last):
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/utils/deprecation.py", line 133, in __call__
    response = self.process_request(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/seahub/base/middleware.py", line 81, in process_request
    cur_note = cache.get('CUR_TOPINFO') if cache.get('CUR_TOPINFO') else \
                                           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/cache/backends/redis.py", line 187, in get
    return self._cache.get(key, default)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/cache/backends/redis.py", line 99, in get
    value = client.get(key)
            ^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/commands/core.py", line 1790, in get
    return self.execute_command("GET", name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/client.py", line 1255, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 1427, in get_connection
    connection.connect()
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 636, in connect
    self.on_connect()
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 738, in on_connect
    auth_response = self.read_response()
                    ^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 848, in read_response
    response = self._parser.read_response(disable_decoding=disable_decoding)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 335, in read_response
    result = self._read_response(disable_decoding=disable_decoding)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/redis/connection.py", line 360, in _read_response
    raise error
redis.exceptions.AuthenticationError: invalid username-password pair or user is disabled.

I added REDIS_PASSWORD to my .env file, but i see no entries to add a username. Is there something I’m missing?

2

Please confirm that you have these entries in your yml files:

services:
  seatable-server
    environment:
      - REDIS_HOST=${REDIS_HOST:-redis}
      - REDIS_PORT=${REDIS_PORT:-6379}
      - REDIS_PASSWORD=${REDIS_PASSWORD:?Variable is not set or empty}


  redis:
    environment:
      - REDIS_PASSWORD=${REDIS_PASSWORD:?Variable is not set or empty}

In addition, verify that you removed all redis configurations from the configuration files and that you use 5.3.12.

3

Yes those are in the yml files. I copied the configuration directory from the git repo and modified them with my save locations. I remove the redis references that where mentioned in Extra Upgrade Notices - SeaTable Admin Manual in the special notes, manual sections. ( i didn’t use the script) i confirmed once that they were removed but i will again today as a safety measure.

4

I was able to get the server running. I changed the password on my DB and Redis to remove any special characters. On my server, I removed the Redis docker images and data file and restarted it. Once i started the server up again it loaded. the only issue now is it can not connect to the the bases.

5

Something must be wrong with your setup. Please add my public ssh key to your server and I will have a look:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAGELD+NYiPZbyYAlsP4A+Y8+47TndHb7qGOcBhXtaa5 cdb@seatable.io

Are you sure, there is no special or custom configuration at your server?