Posts by ANYmal

    Hi!


    If you are using openvpn-as (docker), you have to login in admin web-interface https://IP:943/admin - User Managment - User permissions, select an account, that has to be connected to local network. Then More settings (icon with a pencil), Access control:

    Use NAT

    Allow Access To these Networks: subnet IP/mask (e.g. 10.0.0.0/16)

    For sure turn in option 'all server-side private subnets'


    Save settings + update running server.

    I've get some errors with this plugin, and after uninstall it's dissapears.
    OMV4.1.34-1 with 4.15.18-25-pve kernel


    Errors:

    I'm sorry for misunderstanding. Let's make it clear.
    I want to be able to connect to my Nextcloud from Internet. OMV-GUI available only from innerspace.


    -----------------case1------------------------
    NAT rules on router 443-443, 80-80.


    Docker network rules for:


    letsencrypt 443-443, 80-80


    nextcloud 444-443, 8080-80


    VERIFICATION = http
    ------------------------------------------------


    Letsencrypt can verifying, but NC on 444 port and don't answer from outerspace.


    -----------------case2------------------------
    NAT rules on router 443-443, 80-80.


    Docker network rules for:


    letsencrypt 443-443, 90-80


    nextcloud 444-443, 8080-80


    VERIFICATION = dns
    ------------------------------------------------


    443 port still belongs to LE =(


    Maybe virtual host is the answer (nextcloud.domain.ru)? But it will be redirects on 444 port that wil be closed. Yes, I can open it on my router, but I don't want more holes outside. Paranoia detected =)


    I have own IP&domain. CNAME record is required for this.