But, instead of the Enterprise Edition, I have used the Developer Edition (due to the restriction on the number of users).
My VPS runs Plesk Obsidian on Ubuntu 20.04.
I have used these in the YAML file :
“880:80” #HTTP port
“4443:443” #HTTPS port
The installation goes through and I am able login, but, I get Network error while loading a Base. I checked the dtable_web_settings.py as suggested, and the URLs are mentioned correctly.
The error I get from the browser console is:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://<domain.com>/dtable-server/dtables/e3ed1885-9298-4b1a-89a1-9c1d14dfa2ff?lang=en. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 301.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://<domain.com>/dtable-server/dtables/e3ed1885-9298-4b1a-89a1-9c1d14dfa2ff?lang=en. (Reason: CORS request did not succeed). Status code: (null).
I have installed Let’s Encrypt using my own certificate.
I have added:
Yes, I did… All the 4 URLs changed to https as required. I changed the Let’s Encrypt certificate. The certificate works fine and I am able to get https which opens up the SeaTable login page. I don’t get an error while accessing a base anymore. The key issue is with correctly adding the Let’s Encrypt certificate which seems to take quite sometime to propagate. A bit of patience helps I suppose.
A couple of final questions about the installation…
how do I change the time-zone correctly? In a hurry, I forgot change it during the installation… Should I stop the Service and add it like America/Los_Angeles, for example replacing /Etc/UTC in the docker-compose.yml and restart the Service with command …seatable.sh restart?
will the Let’s Encrypt certificate I have added manually automatically get updated upon expiry? My certificate is issued from Plesk and it does the auto-update on the server.