Posts by Irfilius

  • How to acsess omv user homes in nextcloud via local storage bin mounts

    I managed to set it up this way:

    in compose file mount location of user home dir

    Code
    NEXTCLOUD_MOUNT=/srv/dev-xxxxx/your_home_dir_from_omv/

    your_home_dir_from_omv is dir you set on OMV>users>settings

    In NextCloud need to enable external storage and after that in Administration settings >External storage add location of your user dir
    Folder name: for example MyOMVHome, name that will appear in NextCloud
    external storage: local

    Configuration: location of your username dir, like

    Code
    /srv/dev-xxxxx/your_home_dir_from_omv/username

    available for: pick nextcloud user

    your user home dir is owner by username and nextcloud user www-data will not have permissions.

    First i tried with ACL, but with that new files created with NextCloud are owned by www-data and your username will not be able to change that file
    So i created new user group, for example group_name used in the code below , add my username and www-data to that group and change owner of my username dir
    You can create group using OMV web and add your username into that group. But you need to add www-data with:

    Code
    sudo usermod -a -G group_name www-data

    after that fix permissions

    Code
    sudo chown -R username:group_name /srv/dev-diskxxx/your_home_dir_from_omv/username/

    All new files need to inherit the parent dir group ownership

    Code
    sudo chmod g+s /srv/dev-diskxxx/your_home_dir_from_omv/username/

    The group must have write permissions

    Code
    sudo chmod -R 775 /srv/dev-diskxxxx/your_home_dir_from_omv/username/


    After that you can force nextcloud to scan files in external storage with

    Code
    docker exec --user www-data nextcloud-aio-nextcloud php occ files:scan --all


    Hope I did not forget something :)

  • Nextcloud AIO with Nginx - Submit domain issue

    About the domain you are using. I guess you're using subdomain

    In DNS records, in my case, i have A record for main domain pointing to my public ip and i have CNAME records for subdomain

    What about you? Do you have maybe A record for subdomain? I see that I have different response if I use proxy or DNS only in dns record configuration

    Not sure is there a right way for this, or it doesn't metter

    Thanks

  • How to acsess omv user homes in nextcloud via local storage bin mounts

    Hi

    I found your post searching nextcloud access to user home dir

    Nextcloud is for external access, and i want to use it with omv user home dir. There is no point to have separate locations for nextcloud users to store data.


    Did you find some conf guide for this? Did you solve your problem and how?

    I just started to look for details about the best way how to handle this.

  • Nextcloud AIO with Nginx - Submit domain issue

    After replacing localhost from nginx proxy config and loopback ip from compose file my logs looked ok. Tried curl from outside and it connects. But in AIO submitting domain does not work so I put


    Code
    SKIP_DOMAIN_VALIDATION:true


    and I was able to continue AIO setup. Now I can access from outside using my domain. But from inside its not working

    localip:11000 redirect to https:domainname and ... cant reach this page

    adding records in hosts file on my local pc not working

    NAT loopback config on my old cisco router have some issues

    To try pihole dns maybe...

    What is your choice?

  • Nextcloud AIO with Nginx - Submit domain issue

    I have this info and error repeating in Nginx app log



    I did not see this before. Guess there is no need for such frequent renew?


    If you have registered domainname.net, and have A record for nextcloud.domainname.net that you want to use for Nextcloud

    When you want to configure Nginx proxy, in domain name you add only nextcloud.domainname.net, right?

    After installing AIO, and you want to continue setup on

    Quote

    https://internal.ip.of.this.server:8080

    Page should open normally with https, or you get like this? (first you get info that its not secured and if you want to continue unsecured)

  • Nextcloud AIO with Nginx - Submit domain issue

    Quote from Thormir84

    APACHE_IP_BINDING: HOST_IP


    If you have problems with 127.0.0.1 or 0.0.0.0, use the host's IP; for example, if the server running Docker is 192.168.10.33, then this is the IP you need to enter.

    I tried that settings, as I wrote.
    There is no reason to have problem with loopback address or localhost,,, i guess you need to set server ip if proxy is not one same server.
    But I can try...

    All ports forwarded

  • Nextcloud AIO with Nginx - Submit domain issue

    Quote from chente

    To perform the domain certificate verification, you must forward ports 80 and 443 to the proxy. If you're using either of these ports in the OMV GUI, change them to different ports, or the verification will fail.

    Thats what I meant here:

    "Im using different ports on Nginx but all are forwarded on my router to the server. For example -12345:81, and my nginx is available outside with mypublicip:81 or localip:12345"

    Like that i have other ports for 80 and 443

    I followed instructions, but that is older. Has anyone done installation lately according to the?:

    - Nextcloud AIO with proxy

    - nginx as proxy

    - both on same server

    - custom ports

  • Nextcloud AIO with Nginx - Submit domain issue

    Hi

    For last couple days I tried to submit domain with Nextcloud AIO
    I have domain nextcloud.domainname.net pointing to my public ip

    Nginx configured with proxy host with my domain as source and localhost:11000 as destination, and other parameters from guide
    Im using different ports on Nginx but all are forwarded on my router to the server. For example -12345:81, and my nginx is available outside with mypublicip:81 or localip:12345
    I tried lof of examples, from quick guide, docker in omv and GitHub-All-in-one , adding some parameres like

    # APACHE_IP_BINDING: 127.0.0.1 # Should be set when running behind a web server or reverse proxy

    Basically, I always have similar problems


    Quote

    The domain is not reachable on Port 443 from within this container. Have you opened port 443/tcp in your router/firewall? If yes is the problem most likely that the router or firewall forbids local access to your domain. You can work around that by setting up a local DNS-server.

    If I put in hosts inside the container line
    localip domainname
    then i have


    Quote

    NOTICE: PHP message: Info: It seems like the ip-address of domanname is set to an internal or reserved ip-address. (It was found to be set to '192.168.0.19')

    NOTICE: PHP message: The response of the connection attempt to "https://domainname:443" was:

    NOTICE: PHP message: Expected was: 1f1903faa166299a209d73xxxxxx

    NOTICE: PHP message: The error message was: SSL: no alternative certificate subject name matches target hostname 'nextcloud.irfilius.net'


    This test "https://domainname:443" does not make sense. There is no need for port after https???

    I read somewhere that need to make changes in Nextcloud config.php
    There is no file like that, but there is ConfigurationManager.php where i can see that nextcloud expects 443 ports. Tried to play with that file and changes, but nothing


    I also tried different configuration of my cisco router, becase the NAT loopback / hairpin NAT


    Anyone knows what happening?

  • [Solved] Error Nextcloud AIO "Domaincheck container is not running"

    First installation was from this guide Nextcloud AIO (All In One)

    In the last attempt my docker-compose file looks like from NEXTCLOUD AIO WITH PROXY

    But I have same error after i login with passphrase.


    here is my last log:


    What confuses me is do I need this nextcloud-aio-domaincheck? If I use reverse proxy i dont need it, right?
    Then this "could not resolve host" ....
    Before this log it was: "cURL error 6: Could not resolve host: ghcr.io" (when was different image used in yml)
    But i can ping ghcr.io even when I get into container

    Has anyone had anything similar?