nextcloud compose.yml question

    I was trying to not use duckdns, after a bit of reading and reviews i decided on cloudflare. seems cloudflare has a few extra requirments. like adding namedservers to your system so cloudflare knows it's you. there is a cloudfared app but not for docker.

    i also have a unifi network. which can add challenges as well.


    could i use duckdns for swag only?

    then dyndns for nextcloud, as i have dyndns setup on my unif network?

    so using duckdns and dyndns did not work.

    so i tried my orignal yml using cloudflare.

    i was able to load the page on my local nextwork using 192.168.1.100:444.

    i then went in and change the url inconfig.php to


    now i get a 522 error page thats indicates my host is the issue.

    i'm currently trying to get help over at cloudflare.

    just sharing my journey, as ill post the fix if any here.

    You're moving too fast.

    Take 1 step at a time.


    Launch only a swag container pointing to your duckdns domain.


    Use:

    Code
    URL=<your duckdns url>
VALIDATION=duckdns
DUCKDNSTOKEN=<your token>
SUBDOMAINS=wildcard

    Start SWAG and wait for the certificate.

    docker logs -f swag


    Post the output.


    If it ends with Server ready, open on a browser:

    www.your domain.duckdns.org


    You should see the SWAG Park page secured.

    i currently have went back to cloudflare. if i run

    Code
    docker logs -f swag

    it ends with server ready,

    my url lands on a 522 error page. which seems to be an issue with cloudflare.

    i have been looking for help on cloudflare and they suggested i turns off proxies on my domaion and use dns only. i tried this. when i load my url it goes straight to my router setup page. so cloudflare said it's an issue with my router.

    i have a unifi network. i'm also looking for help there.


    i'll ask again, could i not use duckdns for swag and go back to using dyndns for nextcloud? my brain is so tired after hours of messing with this.

    Truth is i run a small construction company. we use nextcloud for our guys to share everything. i'm getting alot of flack for screwing this all up. LOL

    if i load my local ip https://192.168.1.100:444 i get this message.

    Code
    Welcome to your SWAG instance
A webserver and reverse proxy solution brought to you by linuxserver.io with php support and a built-in Certbot client.

We have an article on how to use swag here: docs.linuxserver.io

For help and support, please visit: linuxserver.io/support

    when i try my url https://my.url.xyz:444

    this site can't be reached

    when i load my url https://my.url.xyz

    i end with a 522 error page

    Go slowly step by step:

    1. Can you access the same page from outside the network using your public ip (use your phone, switch off wlan, https:<my_external_ip>)
    2. Does the same ip exist in the DNS nslookup <my_dns_name> and is it equal to the one you used in 1
    3. Can you access the same page from outside your local network using the DNS name

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Zitat von Zoki

    Go slowly step by step:

    1. Can you access the same page from outside the network using your public ip (use your phone, switch off wlan, https:<my_external_ip>)
    2. Does the same ip exist in the DNS nslookup <my_dns_name> and is it equal to the one you used in 1
    3. Can you access the same page from outside your local network using the DNS name

    1. https://<my_public_ip>

    this site cant be reached

    2. dns lookup on my phone?

    3. waiting to complete step 2

    Check your router if it accepts traffic on port 443 and forwards to the omv port 444

    Repeat steps 1 to 3

    nslookup on any device is ok.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Your router does not answer properly to requests on port 443, eigther

    1. someone (your ISP?) is blocking port 443
    2. port 443 is not open on your router
    3. the router forwards the traffic to a non existing entity / port.

    Check for 1.) forward a different port (8443) to omv port 444 and try https://your_ip:8443 Keep the Network tab open in the browser (hit F12, choose network) before loading the page or reload the page if it is already open. This has to be done from outside your network.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    It would be enough if you see the swag page., so leave nextcloud alone for now. Focus on the router.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    ok, tnx. my brain is melting. LOL. i have read reports that in 2021 my provider blocked ports 80 and 443.

    so i did forward 8443 to 444. same error this site cant be reached.

    that was using my public ip


    ignore above, i was able to load the swag page. i miss typed the port forward on my router.

    If you dont show what you are configuring, it is hard to help.

    Does the router have a function to ping / telnet, ... some device inside the lan?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Offizieller Beitrag
    Zitat von HackitZ

    thanks for the help, i had to leave and sort out some issue's for work. i'm so limited on time. anyways here is the port forward.


    so if i load my url https://my.url.xyz i get a 522 error page

    if i load 192.168.1.100:444 i get the swag page

    Where is that pic from? Your router?


    The full IP like that in port forwarding seems weird (I've never done that on any router I have). Again this is from my router.


    Zitat von HackitZ

    thanks for the help, i had to leave and sort out some issue's for work. i'm so limited on time. anyways here is the port forward.


    so if i load my url https://my.url.xyz i get a 522 error page

    if i load 192.168.1.100:444 i get the swag page

    522 means, your swag is not rechable from the outside (connection timeout). Check what KM0201 wrote, your port forwarding does not work.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    swag is the only container running

    here's the output of

    docker logs -f swag

    if i load my_url.xyz

    i get the 522 error page from cloudflare

    if i load 192.168.1.100:444

    i get the swag page

    if i load my public ip from outside my network

    i get nothing

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden