Questions[dsm](server)

On a Synology NAS with DSM 7.0 I have created through the Graphical UI a dedicated admin user (as recommended in Synology's setup procedure), then I have enabled ssh login and now I can ssh into the Synology. So far so good. However when logging in via ssh I get a strange message before the prompt appears:

Could not chdir to home directory /var/services/homes/<my-admin-user>: No such file or directory

Why's this happening? Is the DSM 7 operation system of my NAS not properly configured?

And how do I fix it? Do I just create the user's home directory?

Additional info

The path /var/services/homes exists, but it is a symlink to /volume1/@fake_home_link which does not exist.

To run docker with the reverse proxy Traefik v2 on a Synology NAS, I need to be able to use port 80 and 443 on the host system. The Operation System of the NAS DSM uses its own reverse proxy, nginx, which thries to occupy the ports on its own. Under DSM 6.2 I could change the port 80 and 443 by using a boot script (change-ports.sh), like described here, so that the ports went free and could be used by docker Traefik reverse proxy.

#! /bin/bash

HTTP_PORT=81
HTTPS_PORT=444

sed -i "s/^\( *listen .*\)80/\1$HTTP_PORT/" /usr/syno/share/nginx/*.mustache
sed -i "s/^\( *listen .*\)443/\1$HTTPS_PORT/" /usr/syno/share/nginx/*.mustache

After upgrading Synology NAS 918+ to DSM 7, I'm no longer able to "free" port 80 and 443. Obviously the script doesn't work and Nginx (from DSM) is always blocking the port.

The Question is, how to reach the docker reverse proxy Traefik again, by using port 80/443 under the new OS DSM 7.

I administer a network of 10 workstations for a small non-profit (also, I'm very inexperienced, forgive me if it's a silly question), and everything has been managed so far as if they were home PCs used by multiple persons, on some workstations a handful of employees even share a single user.

I'm considering introducing Active Directory for managing the user accounts, but we currently don't have a Windows server. A couple of Synology disk stations have been bought, and I'm wondering if I can deploy AD on it? Or is a Windows Server OS necessary for that?

Search results I've found all speak of "integrating" a Linux server or disk station into an AD domain, not using it as a domain controller.

How do I check what OS is installed on my Synology NAS?

uname -a informed me that my NAS is:

aarch64 GNU/Linux synology_rtd1296_rs819

..but how do I know what version of the Synology OS it's running? Wikipedia tells me that Synology used to use an OS based on BSD, but today it's "Linux-based". I tried to get the version from all the usual places, but none of these files exist:

1. /etc/issue
2. /etc/redhat-release
3. /etc/release

How do I determine what is OS version of Disk Station Manager that my Synology NAS is currently running via the command-line?

I'm trying to access my synology nas web ui behind a nginx reverse proxy running on my raspberry. Nginx reverse proxy is working for other stuff, like my ghost blog. I copy/pasted the settings to access my nas's 192.168.0.123:5000 via nas.my.domain, but I got a "Synology / Sorry, page not found" instead of DSM's login prompt.

Here is my nginx's settings

upstream nas {
       server 192.168.0.123:5001;
       # server 192.168.0.123:5000; KO
       # server 192.168.0.123; KO
}

server {
        listen 80;
        return 302 https://$server_name$request_uri;
}

server {
    server_name nas.my.domain;

    listen 443 ssl http2;
    # listen [::]:443 ssl http2;

    access_log  /var/log/nginx/nas.access.log;
    error_log   /var/log/nginx/nas.error.log;

        ssl_certificate /etc/letsencrypt/live/nas.my.domain/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/nas.my.domain/privkey.pem;
        include /etc/nginx/include/diffie-hellman;

        client_max_body_size 2m;

        location ~* \.(?:ico|css|js|gif|jpe?g|png|ttf|woff|)$ {
            access_log off;
            expires 30d;
            add_header Pragma public;
            add_header Cache-Control "public, mustrevalidate, proxy-revalidate";
            proxy_pass https://nas;
        }

        location / {
            proxy_set_header HOST $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-NginX-Proxy true;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
            proxy_pass https://nas;
            proxy_redirect off;
            proxy_buffering off;
        }

}

And inside the nas I set up Control Panel / External Access / Advanced with nas.my.domain http = 80 and https = 443.

Any ideas please to fix or troubleshoot this ?

Best regards,