Beiträge von VoxT3R

  • Libresonic+Lets encrypt+DynDNS

    Zitat von Morlan

    Another user reported the same issue.
    @VoxT3R Did you find a solution?

    Hi Guys.


    I think I did. If you go to the config.php file located at sharedfolders/AppData/Nextcloud/www/nextcloud/config, and edit the config.php, I just commented out the first two line of the three added lines like this:


    // 'overwrite.cli.url' => 'https://**********.duckdns.org',
    // 'overwritehost' => '**********.duckdns.org',[/i]
    'overwriteprotocol' => 'https',



    (NB: Replaced my dns name above with **********)


    If your editing via putty or shellinabox, just Ctrl + X, then press Y, then press Enter.


    I can now access locally, and remote access is still working. The above lines commented stop the ip from being redirected in the url bar of the browser. I still cannot access via my dns if I'm connected to my network. I just VPN it if I want to test, or I just use my mobile when Wifi is off and I'm on my 4G.


    Once this is done, it allowed me to access things locally as well as remotely. Just remember to un-comment these two lines once local file transfer is done.


    Hope this helps guys.

  • Issue with Remote access to Nextcloud on Raspberry pi 3B using Letsencrypt and DuckDNS

    In the nextcloud.subdomain.conf code is below:


    # make sure that your dns has a cname set for nextcloud
    # assuming this container is called "letsencrypt", edit your nextcloud container's config
    # located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
    # 'trusted_proxies' => ['letsencrypt'],
    # 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
    # 'overwritehost' => 'nextcloud.your-domain.com',
    # 'overwriteprotocol' => 'https',
    #
    # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
    # array (
    # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
    # 1 => 'nextcloud.your-domain.com',
    # ),


    server {
    listen 443 ssl;
    listen [::]:443 ssl;


    server_name *********.*;


    include /config/nginx/ssl.conf;


    client_max_body_size 0;


    location / {
    include /config/nginx/proxy.conf;
    resolver 127.0.0.11 valid=30s;
    set $upstream_nextcloud nextcloud;
    proxy_max_temp_file_size 1024m;
    proxy_pass https://$upstream_nextcloud:443;
    }
    }

  • Issue with Remote access to Nextcloud on Raspberry pi 3B using Letsencrypt and DuckDNS

    Zitat von Morlan

    I assume getting the letsencrypt certificates worked for you?
    If yes, your port forwarding should be fine.
    Then the issue probably lies in the nc config and the letsencrypt nginx config.
    Try this thread. Maybe one of the tips helps you. For me it was changing the nextcloud.subdomains.conf in Appdata/letsencrypt/nginx/proxy-confs/


    Code
    proxy_max_temp_file_size 2048m;   to   proxy_max_temp_file_size 1024m;

    Holy crap... that was it. Changed the nextcloud.subdomains.conf in Appdata/letsencrypt/nginx/proxy-confs/ as per your source code and it sprang into life.


    Thanks ever so much for this. You really made my day, I mean week... no lets say month!

  • Issue with Remote access to Nextcloud on Raspberry pi 3B using Letsencrypt and DuckDNS

    Thanks for the response.


    Everything works fine with the install side of Nextcloud. I can access things locally just fine using 192.168.1.5:444


    After local access being fine, during the remote setup video of TDL using Letsencrypt and DuckDNS, we add the following 3 lines of code to the config.php file located at sharedfolders/AppData/Nextcloud/www/nextcloud/config/config.php


    'overwrite.cli.url' => 'https://*******.duckdns.org',
    'overwritehost' => '*******.duckdns.org',
    'overwriteprotocol' => 'https',


    To answer your questions:


    Are you able to touch the server from the wan side at all?
    After setting up the remote access as per TDL's video, the local connection to Nextcloud doesn't work as it seems to redirect from local ip of pi to DuckDNS url. If I comment out the three lines of code above in the config.php file, I have local access again.


    Does DuckDNS have your correct public IP? If so then let's go one step forward.
    Yes, DuckDNS has my correct IP. This was set automatically by DuckDNS, but I can confirm that it is correct.


    Is your router correctly redirecting the ports to your server?
    Yes I believe it is. I attached a screenshot of the config on my router that forwards 443 to 450, and 80 to 90. Here is my router port forwarding config.


    I understand that your services are listening on ports 90 and 450?
    Yes they are as per TDL vids.


    First, make sure that the packets are actually getting up from wan to get to your omv at 192.168.1.5
    Not too sure what you mean here as I'm not to well up on networking, but I can ping 192.168.1.5 with cmd as admin, with the three lines of code active and not commented out. (if that makes sense)


    Ironically, I have just tried to connect remotely using my DuckDNS url without the pi switched on, and I get the same ERR_CONNECTION_CLOSED error.

  • Issue with Remote access to Nextcloud on Raspberry pi 3B using Letsencrypt and DuckDNS

    Hi all.


    I have installed OMV with Docker and Nextcloud using Techno Dad Life's videos on a Rasbperry pi 3 model B. I used all lsioarmhf repos. Access from within my network is fine so far..


    I then tried to set up remote access to my Nextcloud server using DuckDNS and Letsencrypt as per Techno Dad Life's video also. I have followed everything right down to the last full stop in all his videos, but I am having issues connecting remotely. All port forwarding has been set up on my router. I have a D-Link router provided by TalkTalk (UK). See config below:


















    I have tried to connect to my duckdns via a device outside of my home network, but I get the an error saying This site can't be reached. ***********.duckdns.org unexpectedly closed the connection. ERR_CONNECTION_CLOSED:





















    I've restarted everything, but no joy. All docker ports and all instructions have been set up as Techno Dad Life's videos.


    Does anyone have any idea what the issue might be? If so, please can you help?


    TIA everyone.