502 Bad Gateway when opening base after editing dtable_server_config.json

Hi everyone,
i am not able to solve or unwind a problem occurring after updating dtable_server_config.json file. Thanks for having a look at this :slight_smile:

best, tim

My Setup:

  • SeaTable Edition: Enterprise
  • SeaTable Version: 5.0.7

Description of the Problem:

  • updated to the latest version of SeaTable self-hosted enterprise edition, version 5.
  • forced usage of API-Gateway endpoints by changing dtable_server_config.json
    added
   "redirect_list_rows_api": true,
    "dtable_web_service_url": "https://portal.mydomain.de/"

<html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body> </html>

Logs and checks:

  • Api-Log
    [2024-07-16 13:28:32] [info] dtable-api-gateway started

  • Dtable-Web-log

[ERROR] seahub.api2.endpoints.admin.utils[45] - get dtable db stats error: HTTPConnectionPool(host='127.0.0.1', port=7777): Max retries exceeded with url: /api/v1/stats/?from=dtable_web (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1bcb1624f0>: Failed to establish a new connection: [Errno 111] Connection refused'))
Traceback (most recent call last):
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/opt/seatable/seatable-server-latest/dtable-web/thirdpart/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

error with port 7777 means that your dtable-db component is not reachable. Can you check if dtable-db started and provides his service at this port? Can you ping dtable-db? Ping dtable-db Server

thanks, cdb! dtable-db started (according to .conf on port 7777) but i can’t ping it.

likewise to the linked Thread from first post the problem disappeared. i checked several config files but i didn’t make any changes. but finally i can enter my bases and seatable works fine…

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.