Skip to content

Authorization in the Wetty Docker container via Tinyauth, using the Synology reverse proxy for the external domain and SSL certificates #582

Description

@NSGrid

Hi everyone, maybe someone can give me some advice why I can't seem to get the redirect to the Wetty-SSH container to work properly (it launches an SSH session in the browser to access the Synology command line)?

Here’s an example. This is how an SSH session starts when I open the Wetty Docker container directly via its local IP address. In my case, it’s 192.168.0.7:8888.
583785156-9d49df5f-0e5c-4601-ad15-da0afbfe9517

When I try to configure access authorization for the Wetty Docker container using your Tinyauth, I get this (see the attached screenshot). Authorization via Tinyauth succeeds, and I’m redirected to the Wetty container, but the SSH session doesn’t start inside it.
583785099-e5a6cbb7-eb75-47cb-a6bc-cd7a764f6017

test.domen.ru replaced my original domain here as an example

You can review the Docker Compose and Nginx configuration files. Since, as the developer explained to me earlier, a helper container is required to configure the Synology reverse proxy, the configuration here looks like this:
Synology reverse proxy (external domain and SSL certificates) > Nginx auxiliary container + Tinyauth container > Wetty service container
compose.4.yaml
nginx.9.conf.txt

P. S. Since the previous setup without Tinyauth container
Synology reverse proxy (external domen and SSL certs)> NGINX-alpine container with basic authentication > Wetty container
worked, the SSH-session started normally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions