Libresonic+Lets encrypt+DynDNS

    • OMV 4.x
    • Resolved
    • Morlan wrote:

      Alex831212 wrote:

      Morlan wrote:

      Alex831212 wrote:

      not even typing my address (e.g. nextcloud.mydomain.duckdns.org) it does not work the page tells me: this page does not work (myserver.duckdns.org) did not return any data
      Which trusted domains are written in your config.php in the /config/www/nextcloud/config/ of your nextcloud container ?My trusted domains are :


      0 => 'IPLOCAL:444',
      1 => 'myserver.duckdns.org',



      But i just found this:


      "yes, I notice this behabiour only if recreate container to load a new version of the used docker, I need to select bridge as network to avoid this problem.

      For your actual problem: try to use the "modify" button and change network mode to bridge ( and revise port assing that probably are lost), this time must work.

      If not, you need to recreate the docker ( easy because your config files are safe in your own path)."


      What do you think of that ?

      Give it a try .. remapping the ports is done quite fast. My config.php says the same exect the IPLOCAL ist specified to my omv machine.
      for port remapping I just have to modify the docker, put in bridge?


      I'm afraid of losing my configuration and I have no access to nextcloud from outside.
    • Alex831212 wrote:

      for port remapping I just have to modify the docker, put in bridge?

      I'm afraid of losing my configuration and I have no access to nextcloud from outside.
      Yes just modify. Choose bridge and reenter the ports.


      ieronymous wrote:

      Morlan wrote:

      When getting the certs works, then your port forwarding is fine. Which error message do you get? The standart nginx Welcome to our page?
      Unable to connect (in the airsonic.subdomain.conf.sample file i tried every possible way to type the server_name airsonic.....airsonic.mysubdomain....mysubdomain...)The only thing I couldnt follow from both guides was to nano /sharedfolders/Appdata/airsonic to nano a custom.cnf because ther isnt any
      Did you remove the .sample at the end? server_name airsonic.*
      Are the containers joined in a network?
    • ieronymous wrote:

      Morlan wrote:

      Did you remove the .sample at the end? server_name airsonic.*
      Are the containers joined in a network?
      Yes I did now leaving as server_name my_subdomain only name created in duckdns siteContainers are joined in the netwrok i made with the command docker network create name_of_network
      Also I have the arguments as well mentioned in the video
      My airsonic.subdomains.conf looks like this:

      Source Code

      1. server {
      2. listen 443 ssl;
      3. listen [::]:443 ssl;
      4. server_name airsonic.*;
      5. include /config/nginx/ssl.conf;
      6. client_max_body_size 0;
      7. location / {
      8. include /config/nginx/proxy.conf;
      9. resolver 127.0.0.11 valid=30s;
      10. set $upstream_airsonic airsonic;
      11. proxy_pass http://$upstream_airsonic:4040;
      12. }
      13. }
      Display All
      Dont forget to restart the letsencrypt container after you change a config
    • ieronymous wrote:

      F@@@@ck i m getting there probably....... I am an epic Ash@@@@@@ All that time I was trying to access the airsoft form another tab from my same internal network ahahahahaahahah. Just now I tried from a phone using cellular data and by airsonic.my_subdomain.duckdns.org I was able to see the message welcome to our server....what else am I missing now?
      That should probably work too. You should clear your browser cache once in a while. Sometimes the changes work but your browser is too lazy reloading the information.
      When you get the welcome to our server your nginx reverse proxy works. So now you need to get the conf - files right.
    • ok it looks like now I can also access locally after changing to bridge.
      Only I had to delete the docker nextcloud and redo it. now he tells me "your directory is invalid make sure that the data directory contains a" .occdata "file at its root.

      How do you recreate this file and put it back in the right place ?

      Edit : I managed to put back the data file but now again I have access from outside but still not locally ...

      The post was edited 1 time, last by Alex831212 ().

    • ieronymous wrote:

      Morlan wrote:

      conf - files right.
      files? how many are there?Also do I have to change the network mode from however_i_named_the _network to bridge in both containers? airsonic and letsencrypt

      Do I need the arguments? --cap-add=NET_ADMIN --network however_i_named_the _network ??
      No need to change the container if you build it according to TDL video ...


      Alex831212 wrote:

      ok it looks like now I can also access locally after changing to bridge.
      Only I had to delete the docker nextcloud and redo it. now he tells me "your directory is invalid make sure that the data directory contains a" .occdata "file at its root.

      How do you recreate this file and put it back in the right place ?

      Edit : I managed to put back the data file but now again I have access from outside but still not locally ...
      :/

      The post was edited 1 time, last by Morlan ().