Synology NAS

[pjhaucke]

Is it possible to run 2fauth on a Synology NAS?

And when yes, how?

Best regards. PJH

[Bubka]

AFAIK, There is no package to deploy 2FAuth via the Synology package system.

But:

• You can run the 2FAuth Docker image if your NAS supports Docker
• You can enable the Synology Web server of your NAS and deploy 2FAuth like any other web application/site

[pjhaucke]

Hi thank you for that quick response.

I downloaded the 2faut/2fauth image to my docker containers and get it started.

The container is up and runs.

But how can I get it into the web station? There must be a document root directory and there must be a service.

And how can I start the 2fauth?

Tank you again. PJH

[Bubka]

I won't described here all steps to deploy a website on Web Station, there is the Synology Web Station documentation and many resources that cover this task on the Internet. You can also check the 2FAuth Documentation for prerequisites and the main steps.

Regarding the document root, it has to be [2fauth_source_dir]/public.

[pjhaucke]

Yes, thank you for supporting. I get 2fauth running (and working) in Synology Docker container yet.

Don't know how to use it, but will try to find some documentation.

Thank you and best regards. PJH

[pe1obw]

I tried to run 2fauth on a Synology DS220+. First, I manually created a directory /volume1/docker/2fauth, then chown and chmod as documented.
When I start the container, either on the command line in an ssh session with the proposed arguments, or using the Synology gui, I get an error message:

Running version latest commit c765bfd built on 2023-11-21T12:53:11Z
supervisord version: v0.6.8
PHP 8.1.22 (fpm-fcgi) (built: Aug  3 2023 23:11:21)
nginx version: nginx/1.22.1

   INFO  Configuration cached successfully.

INFO[2023-12-18T09:20:22Z] load configuration from file                  file=/etc/supervisor/supervisord.conf
nginx: [emerg] mkdir() "/var/lib/nginx/tmp/proxy" failed (13: Permission denied)

and the web server is not reachable. When I do sh in the running container (as root), I see that /var/lib/nginx/tmp is indeed not accessible.

# ls -lr /var/lib/nginx/
total 8
drwx------    6 1000     1000          4096 Nov 21 12:53 tmp
lrwxrwxrwx    1 1000     1000            10 Nov 21 12:53 run -> /run/nginx
lrwxrwxrwx    1 1000     1000            22 Nov 21 12:53 modules -> /usr/lib/nginx/modules
lrwxrwxrwx    1 1000     1000            14 Nov 21 12:53 logs -> /var/log/nginx
drwxr-xr-x    2 1000     1000          4096 Nov 21 12:53 html

any idea how to fix this?

[Bubka]

This kind of permission error coming from nginx has already been discussed in #57.

At that time, based on this discussion, I pushed a fix to set the client_body_temp_path nginx setting to /tmp.

In your case it is the proxy temp path that is read-only, so setting the proxy_temp_path nginx setting to /tmp/proxy would probably fix the issue.

Edit the /etc/nginx/nginx.conf file of your container et add the following right after client_body_temp_path /tmp 1 2; :

proxy_temp_path /tmp/proxy;

[pe1obw]

Thanks for the quick response! I added the line, and others for the fastcgi, uwsgi and scgi temp paths as well, and that did the trick!

By the way, while experimenting, I sometimes ended up with a symbolic link /2fauth/storage pointing to itself, but I can't reproduce it.