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 _;
location / {
return 404;
}
location ^~ /.well-known/acme-challenge/ {
default_type âtext/plainâ;
root /var/www;
}
location = /.well-known/acme-challenge/ {
return 404;
}
error_page 502 403 404 /error.html;
location = /error.html {
root /var/www;
}
}
Then please check the existence and content of the nginx.conf in SeaTableâs conf folder. This is what mine looks like:
log_format seatableformat â$http_x_forwarded_for $remote_addr [$time_local] â$requestâ $status $body_bytes_sent â$http_refererâ â$http_user_agentâ $upstream_response_timeâ;
upstream dtable_servers {
server 127.0.0.1:5000;
keepalive 15;
}
server {
if ($host = seatable.de) {
return 301 https://$host$request_uri;
}
listen 80;
server_name seatable.de;
return 404;
}
server {
server_name seatable.de;
listen 443 ssl;
ssl_certificate /shared/ssl/fullchain.pem;
ssl_certificate_key /shared/ssl/privkey.pem;
proxy_set_header X-Forwarded-For $remote_addr;
location / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_read_timeout 1200s;
access_log /opt/nginx-logs/dtable-web.access.log seatableformat;
error_log /opt/nginx-logs/dtable-web.error.log;
}
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break;
proxy_pass http://127.0.0.1:8082;
client_max_body_size 0;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_request_buffering off;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
proxy_send_timeout 36000s;
send_timeout 36000s;
access_log /opt/nginx-logs/seafhttp.access.log seatableformat;
error_log /opt/nginx-logs/seafhttp.error.log;
}
location /media {
root /opt/seatable/seatable-server-latest/dtable-web;
}
location /socket.io {
proxy_pass http://dtable_servers;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_redirect off;
proxy_buffers 8 32k;
proxy_buffer_size 64k;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy true;
access_log /opt/nginx-logs/socket-io.access.log seatableformat;
error_log /opt/nginx-logs/socket-io.error.log;
}
location /dtable-server {
# add_header Access-Control-Allow-Origin *;
if ($request_method = 'OPTIONS') {
add_header Access-Control-Allow-Origin *;
add_header Access-Control-Allow-Methods GET,POST,PUT,DELETE,OPTIONS;
add_header Access-Control-Allow-Headers "deviceType,token, authorization, content-type";
return 204;
}
rewrite ^/dtable-server/(.*)$ /$1 break;
proxy_pass http://dtable_servers;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Forwarded-Proto $scheme;
access_log /opt/nginx-logs/dtable-server.access.log seatableformat;
error_log /opt/nginx-logs/dtable-server.error.log;
}
}
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.
Let me know if this works.