• 1 Post
  • 14 Comments
Joined 1 year ago
cake
Cake day: October 1st, 2023

help-circle

  • but it doesn’t worked

    So many details.

    Why not use some type of “network info tool” app to find out which DNS servers are actually being used and what their replies are?

    Android is well known of often sneaking in the Google DNS servers (8.8.8.8 and 8.8.4.4 for IPv4) if you only enter one DNS server in the network options of your WLAN. Place your own DNS into both fields. Some Android ROMs complain then that they are identical, in that case try to enter 127.0.0.1 or 0.0.0.0 for example as one, if that also doesnt work then just make up another IP that fits your network. It will send requests into nowhere but since the other one is working, it doesnt matter much.

    A lot of Android ROMs also have “Private DNS” enabled by default. Disable that, it might be the reason its bypassing your local DNS (Pihole, Adguard Home, whatever).

    And some users mistakenly enter their own local DNS (like a Pihole) into the “Private DNS” option.

    What is also possible is that some apps have their own builtin “by-pass”, for example they might use DNS-over-TLS or DNS-over-HTTPS (DoT/DoH) to make encrypted DNS requests to fixed servers, completely ignoring whatever you set in the OS network config.

    /r/Android and /r/HomeNetworking can help.





  • 8080 in the case of NC AiO is for not for Nextcloud but for the AiO Container via https.

    The Apache port is not internal, but accessible via IP:11000. But it is exclusively for use via reverse proxy.

    NC AiO dies things differently than pure NC.

    I know NC AiO is a bit weird and unique. But i can only go by what OP is sharing as the compose they are attempting. And none of that makes sense as i said.

    to be blunt, and maybe a bit of a jerk, but i think OP did not read the documentation that is linked right in the compose file or the github page. NC AiO has excellent documentation of how to set it up. Thats it, i said it :/

    A lot of people are allergic to properly reading documentation and instead they come to places like here and ask others to fix their mistakes.


  • ports:
    
      # - 1080:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - 8080:8080
      # - 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
    environment: # Is needed when using any of the options below
      - APACHE_PORT=11000
    

    Whatever you are trying to do there doesnt make sense.

    You are telling the Apache webserver that runs inside the container to listen on port 11000, fine. But then you are mapping 8080 to 8080 on the Docker host, how is that supposed to work? And you also mention using NPM, but there is nothing about that visible in the shared compose bit.

    Why not simply follow the documentation of Nextcloud, and if you want to combine it with NPM, follow their documentation too?

    /r/Nextcloud and /r/NginxProxyManager also exist and are active. This here is not a general techsupport-for-whatever-software subreddit.

    And if you have questions about very basic Docker usage, try /r/Docker but i would suggest you simply consult the Docker documentation first.