Embedding of views don't seem to working after 6.2 update

User Talk Views
1

Your Setup:

  • SeaTable Cloud, Dedicated or Self-hosted?
  • SeaTable Version (only necessary for self-hosted):
    You can find your SeaTable Server version at https://your-server-url/server-info

Describe the Problem/Error/Question:

Please describe your issue as precise as possible. If helpful, you can also provide:

  • Screenshots
  • Diagrams with Excalidraw
  • Base structure details using this script.

Error Messages:

If there are any error messages shown in the browser console, please include them for better readability by wrapping them in a code block.

Example of a code block for error messages

After this morning’s update of Seatable Cloud to 6.2 embedding of shared views to webpages doesn’t seem to be working anymore.

The links themselves work fine, but when embedding, I get the message: “cloud.seatable.io refused to establish the connection”.

2

Sorry for the inconvenience! This was a configuration error on our side.
We have already applied a fix.

Can you confirm that this has fixed the issue?

3

Everything is now again working as it should be.

Thank you so much!!

4

@sha anything that might affect self-hosted instances after the update, or specific to you cloud installation?

5

@abaer The modification that broke the ability to embed views/apps/forms was caused by the removal of the X-Frame-Options header for certain routes. This is handled entirely at the reverse proxy layer (= Caddy for default installations) and not within the seatable-server container.

This was the faulty commit: ALLOWALL is not a valid value for the X-Frame-Options header · seatable/seatable-release@09f1fac · GitHub

I reverted this change yesterday and applied these changes to cloud.seatable.io: Revert "ALLOWALL is not a valid value for the X-Frame-Options header" · seatable/seatable-release@a8939b6 · GitHub

Therefore self-hosted instances are only affected if you’ve upgraded to SeaTable v6.2 between the initial release of v6.2 (July 21) and the latest release made yesterday and you’re using Caddy (or you’ve ported the header changes to your own reverse proxy configuration).

6

Thank you! I’ll double-check when I transfer the settings to Traefik.