Network error.. Developer edition on own VP server behind a web server

I have followed the procedure explained in Install SeaTable Enterprise on your own server behind a web server

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:

server {
listen 80;
listen [::]:80;
server_name <domain.com>;

location / {
proxy_pass http://<domain.com>:880;
}
}

to the nginx conf file.

Any suggestions to get the installation done correctly?

A normal installation shouldn’t have a CORS problem. Just to clarify: to enable CORS you can visit Integrate with Seafile - SeaTable Admin Manual for instructions.

I’m not sure why, are 80 and 443 already taken on your server?

I am installing Seatable under a sub-domain. If I use 80 and 443, I get the below error while running docker-compose up:
TypeError: a bytes-like object is required, not ‘str’

Plesk uses 80 and 443 for webserver.

The CORS related directive you have specified is already there in the nginx conf file on the host as well as in the seafile nginx.conf file.

Thanks for your reply. I’m sure someone with better expertise than me will answer you soon!

Just curious again: Did you specify the dtable-server address in your dtable_web_settings.py?

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…

  1. 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?

  2. 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.

Proably a caching problem.

docker-compose down → modify docker-compose.yml → docker-compose up -d

It depends. Did you use certbot? Why not run a certbot --dry-run? Or did you use the Plesk extension.
On a different note, I am not sure how this is a question for the SeaTable forum.

1 Like

Sorry for my delayed acknowledgement of your excellent responses… I used Plesk for installing the Let’s Encrypt certificate. I agree it is not a relevant question in this forum.

Yes, the time-zone change in the docker-compose.yml worked fine. In fact, everything works if your instructions from Install SeaTable Enterprise on your own server behind a web server are followed to a T. That’s what I did.

Thank you for your help! This is easily the best German software I have come across in years! My sincere appreciation!

Hi Jungfrau, I am very happy to hear that you enjoy using SeaTable.
The credit however does not go to Germany, but to China :wink: You must thank @daniel.pan and his team.

I have thanked @daniel.pan… Great work indeed… Nice to know about the collaborative work folks! :+1:

1 Like

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