Unfortuneately, when I try to open a base on my fresh install, it always ends whith an infinite loading screen.
I can go back and create another base, put I am not able to access any base via the browser.
what I tried so far:
-several reinstalls
-differend VM
-seatable 1.6 (insteat of latest)
mariadb container is working
the only error after docker compose up i get is:
seatable | nginx: [emerg] open() â/etc/nginx/sites-enabled/defaultâ failed (2: No such file or directory) in /etc/nginx/nginx.conf:25
Hi hoeber,
welcome to the SeaTable forum!
The nginx conf for SeaTable is not in the default file in /etc/nginx/sites-enabled. The nginx conf for Seatable is in the nginx.conf in /opt/seatable/seatable-data/seatable/conf.
The default in /etc/nginx/sites-enabled shoud be a symlink to /etc/nginx/sites-available. The content of the symlinked file is this:
server {
listen 80 default_server;
listen [::]:80;
server_name _;
Can you check if this file is where it is supposed to be and if your file is equivalent? Please note: my configuration file is for the domain seatable.de. Whereever I used âseatable.deâ as a domain name, youâd have to use your domain name. Additionally, the letâs encrypt certificate is registered during the docker-compose.
hi rdb,
thanks for the quick and thorough help!
i have to admit, i am still quite a newbie to the whole container business so please bare with me when i ask stupid thinks.
in the seatable container, there was so no â/etc/nginx/sites-availableâ, so i created the file with the content you provided.
i also created the symlink âln -s /etc/nginx/sites-available /etc/nginx/sites-enabledâ inside the container.
i pasted the content of your nginx.conf into mine and changed your domain to my local ip.
maybe here also lies a obstacle, my current environemnt only allows me to access the server from within the network or via vpn. i have a static ip for the vm and can, for now, live without a valid letsencrypt cert. (i cannot open ports)
with this in mind, i guess the paste of your nginx.conf has to fail, right?
when i docker-compose up I get:
seatable | nginx: [emerg] cannot load certificate â/shared/ssl/fullchain.pemâ: BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file o,ârâ) error:2006D080:BIO routines:BIO_new_file:no such file)
also i cannot acces the seatble anymore.
so i removed everything an started from scratch. first time i do docker-compose up I get:
seatable-mysql | 2021-03-16 9:16:31 3 [Warning] Aborted connection 3 to db: âunconnectedâ user: ârootâ host: â172.30.0.5â (Got an error reading communication packets)
maybe this the culprit?