Universal app page for editing a single data record is not saved

User Talk Apps
1

Hello everyone,

We have a Seatable installation on our local servers. The Seatable application runs stably and shows no abnormalities when editing bases and tables.
When creating apps, the problem has now arisen that it is not possible to create pages with ‘Single Record’ in the universal app. The page is created in the app, but all fields etc. that are added to the page are not saved. As soon as you leave this newly created single record page in the app editor (e.g. switch to another page) or when you use the preview of the app, all added fields are deleted again and the single record page is completely empty.

Does anyone have a similar problem?

Thank you very much for your feedback!

2

I tested the “Single Record” page within the universal app with a simple test base in the local version of Seatable. And I uploaded the same base in the cloud version of Seatable.

Local installation
I have the same problem here. I can setup the page and e.g. add all table colums/field. But the changes are not safed and when I try to use the app page it appearce empty with no field or entrance.

Cloud version
All field and functions are there.

This means that even if the fields, columns and other changes within the app are not displayed and do not work on the local installation, the app is saved correctly and a ‘simple’ upload to the cloud version will work and show full functionality.

Unfortunatly I can´t upload pictures here in the forum.

Furthermore, when testing the app functions, I noticed that the statistics/charts do not work in the app when installed locally. The error message “Internal server error” is displayed.
If I call up the statistics directly in the table view as a dashboard during the local installation, the problem does not exist and I get the desired statistics and charts displayed.

Is there obviously a problem with the app functionality in the local installation? Since the same base works in the cloud without any problems, I assume that our installation still has a bug.

Does any of the Seacloud administrators have any idea what we need to do with our installation to prevent the error from occurring?

Thank you very much!

Best regrads,
Christian

3

(Obviously) no.

Agreed. Check your log files.

4

Thank you very much for the response.

Can you please give some advice regarding the log files? Which log file is needed? Is there any specific information we need to review or any specific entrance to be found?

Thanks

5

Search for errors.

Check dtable-db.log first, but not exclusively.

6

Thank´s!

I will contact my IT. Would it be possible to send you the Log-Files in case we will not find the solution?

As hint: We use 100% local appraoch (“Air gap installation”) without Internet connection of the Seatable server. Maybe this may contribute to the issue.

Regards,
Christian

7

Hello,

first evaluation of the log files showed an error within dtable_web.log:

Traceback (Most recent call last):I
Flle “/opt/seatable/seatable-server-latest/dtable-web/seahub/dtable_apps/unlversal_app/apls.py” , llne 3289, ln post
response = requests.get(url, tlMeout=TIMEOUT)
Flle “/opt/seatable/seatable-server-latest/dtable-web/thlrdpart/requests/apl.py”, llne 73, ln get
*return request(“get”, url, paraMs=paraMs, *kwargs)
Flle “/opt/seatable/seatable-server-latest/dtable-web/thlrdpart/requests/apl.py”, llne 59, tn request
*return sesston.request(Method=Method, url=url, *kwargs)
Flle “/opt/seatable/seatable-server-latest/dtable-web/thlrdpart/requests/sesslons.py”, llne 589, ln request
*resp= self.send(prep, *send_kwargs)
Flle “/opt/seatable/seatable-server-latest/dtable-web/thlrdpart/requests/sesslons.py”, llne 703, ln send
*r = adapter.send(request, *kwargs)
Flle “/opt/seatable/seatable-server-latest/dtable-web/thlrdpart/requests/adapters.py”, llne 517, ln send
ralse SSLError(e, request=request)
requests.exceptlons.SSLError: HTTPSConnectlonPool(host=‘docXXXe1.XXX.zz’, port=443): Max retrles exceeded wlth url: /seafhttp/ftles/a17b83d9-6a98-42Sa-bde1-ba1cc2ab8fc2/lkDc.json (Caused by
SSLError(SSLCertVerlflcatlonError(l, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certlflcate verlfy falled: unable to get local lssuer certlflcate (_ssl.c:1131)’)))
2025-02-11 11:84:26 rERRORl dianoo.reouestr241l - Internat Server Error: /aot/v2.1/untversal-aoos/965Sab52-e93a-4998-afd5-535f656b9c68/stattstlc/

Possibly we might have an SSL issue. Are there any general instructions for this type of error message or how to avoid the error?

Thank´s! :pray:

8
9

Hi,

We are struggling to get the mandatory “globally trusted wildcard certificate” because our local domain uses .zz

Does anyone have any idea how to solve this problem?

Kind regards,
Christian