Next cloud OMV5 RPI

  • Hi,


    I have tried to follow this guide but can't seem to get anything to work! My router GUI uses port 80 and 443 so I tried to change those.:/


    Whenever I go to my url I see my routers login page and can't get to nextcloud ;(. The error I see when I run docker logs -f swag is:


    Code
    Hint: The Certificate Authority couldn't exterally verify that the standalone plugin completed the required http-01 challenges. Ensure the plugin is configured correctly and that the changes it makes are accessible from the internet.
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Some challenges have failed.
    Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
    ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

    I have no idea how to fix this or if this is even my main problem

  • Reply here, click the "code" button, and inside the code box, paste your docker-compose/stack file. Edit out any personal info (passwords, domain names, email addresses)..


    It sounds like you have a DNS issue if you're getting your router login page.

    Air Conditioners are a lot like PC's... They work great until you open Windows.


  • The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

    Also check this link (also available in the guide)

    https://blog.linuxserver.io/20…t-mapping-and-forwarding/

  • I think it is my ports . I know my router doesn't allow 80 or 443 bcause they are used by the gui. I thought i'd opened ports 81 and 444 :/


  • I think it is my ports . I know my router doesn't allow 80 or 443 bcause they are used by the gui. I thought i'd opened ports 81 and 444 :/

    Which Router do you have? Never heard/saw a Router access page using port 80/443.

    Although some FritzBoxes need some permissions to allow the portforwarding for the service of http/https.


    And the portforwarding is from External 80 to Internal 81 and the same for 443 to 444.


    Also, there's some snags on your YML.

    If you have a duckdns, it's better to change the auth and you need some "SUBDOMAINS".

    Also, be sure that your DUCKDNS is constantly updated.


    Try this YML:


    As for the update of DUCKDNS, see how to do it on their page:

    https://www.duckdns.org/install.jsp#linux-cron

  • Thanks Soma, Everything in docker seems to be running now but I still cant access nextcloud localy or externally?


    My router is a Huawei DG8041W

  • You should be able to access Nextcloud locally with https:\\IPofTHEpi:450


    As for the external access, I can't find any info on that specific model but in general, Huawei Routers allow to forward ports.


    See here if it's similar to yours:

    Fastest Huawei DR814 Router Port Forwarding

  • Can you post your:


    SWAG logs (hide your sensible data)


    How are you accessing Nextcloud? Via subdomain or subfolder?


    Post you config.php of nextcloud (hide the sensible data)

  • I tried to access nextcloud locally with https:\\IPofTHEpi:450

  • The SWAG is working fine.

    Acessing Nextcloud via internal IP can be done without SWAG (that is why on the YML part of Nextcloud, the port is set to "450")


    You have to open a browser on another computer on the same network and put the INTERNAL IP of your server (in this case, the internal IP of your Pi, something like https://192.168.x.x:450 Change the x to the proper numbers)


    Click on "Advance" and then there's a "Proceed anyway"


    But you didn't answered the other questions.

    If you follow the guide without deviate, you'll access EXTERNALLY with something as https://www.YOURDOMAIN.duckdns.org/nextcloud


    After first login, then you can change to something as: https://nextcloud.YOURDOMAIN.duckdns.org

  • Have you done the configuration of the proxy part of the guide already?


    Quote

    Configuration of proxy

    • cd /srv/dev-disk-by-label-disk1/appdata/swag/nginx/proxy-confs /srv/dev-disk-by-label-disk1 has to be adjusted
    • cp nextcloud.subfolder.conf.sample nextcloud.subfolder.conf this will copy the sample configuration file for nextcloud and removes the .sample so that the file will become active
    • nano /srv/dev-disk-by-label-disk1/appdata/nextcloud/config/www/nextcloud/config/config.php and insert the text from the box below at the end, but befor the ");" - change "your.url" to your domain

    Code

    Code
    'trusted_proxies' => array (
    0 => 'swag',
    ),
    'overwritewebroot' => '/nextcloud',
    'overwrite.cli.url' => 'https://your.url/nextcloud',
    'trusted_domains' => array (
    0 => 'your.url:443',
    ),
    • docker restart swag to restart the swag container
    • docker logs -f swag to check for errors
    • docker restart nextcloud
  • I've made sure the proxy config is there and SWAG appears to be running fine. I can't find a nextcloud config that actually contains data though?

  • I can't find a nextcloud config that actually contains data though?

    As stated in @macom  Guide (in your case will be):

    nano /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/nextcloud/config/www/nextcloud/config/config.php


    Post it here in a "Code Box" but hide sensible data

  • Thanks, here's whats in my config file

  • Thanks, here's whats in my config file

    You need to edit it (there's errors on the commas and semi-commas):


    And you also should have previously renamed the subfolder file (in your case):


    cd /srv/dev-disk-by-uuid-20A00CCAA00CA7FC/Appdata/appdata/swag/nginx/proxy-confs/

    cp nextcloud.subfolder.conf.sample nextcloud.subfolder.conf


    Then restart swag and Nextcloud and you should be able to, at least, access it via Internal IP.

  • Ok so now I'm getting:


    Code
    Internal Server Error
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the webserver log.


    via internal IP and the router login page via my domain :/. Is there a way to remove everything and start again? ;(

  • Is there a way to remove everything and start again?

    You can delete all the folders there are/were created from the stack and just redeploy again and they will be recreated.

  • I've found the error log and its showign this:

    Code
    [tt]2021/06/13 21:52:02 [error] 388#388: *2 FastCGI sent in stderr: "PHP message: PHP Parse error: syntax error, unexpected '=>' (T_DOUBLE_ARROW) in /config/www/nextcloud/config/config.php on line 53" while reading upstream, client: 192.168.1.11, server: _, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24:450"
    2021/06/13 21:52:02 [error] 388#388: *2 FastCGI sent in stderr: "PHP message: PHP Parse error: syntax error, unexpected '=>' (T_DOUBLE_ARROW) in /config/www/nextcloud/config/config.php on line 53" while reading upstream, client: 192.168.1.11, server: _, request: "GET /favicon.ico HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24:450"

    I also found a different config file to before?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!