Hi there!
I’m facing an issue after upgrading our system where an iFrame used to display a table, which is no longer working.
Previously, I was using an iFrame to embed a table to an external application (PRTG monitor). This setup worked flawlessly before the upgrade (version 4.2 → 4.3).
Could changes introduced in the upgrade (version 4.3) be conflicting with CSP settings and preventing the iFrame from displaying correctly?
Is it related to this in any way? (We are self-hosted)
Please have a look at your seatable-server.yml in /opt/seatable-compose. There you find all the settings for the content-security-policy. My recommendation is that you copy the seatable-server.yml to custom-seatable-server.yml and update the value according to your need.
Then stop all containers and restart.
cp /opt/seatable-compose
cp seatable-server.yml custom-seatable-server.yml
# change custom-seatable-server.yml
# change in .env the seatable-server.ymlt to custom-seatable-server.yml
docker compose down
docker compose up -d
Thank you, we got it to work!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.