NextCloud successfully installed from my PC 🥳

NextCloud successfully installed from my PC 🥳

Hi

​

I think I need to apologize because I thought I couldn't install NextCloud on my PC with Docker now it has changed, I successfully managed to install it by simply using a different method. I simply created a customized guide using an AI and made it work with the help of Ngrok. What said is this a good alternative to the DuckDNS Fritzbox port release and so on.

​

I'm very happy that I've done the whole thing now.

▲ 0 r/docker

Nextcloud, DuckDNS, Fritzbox, Docker

Hello,

​

I have a problem with my Nextcloud because I'm not quite familiar with it yet. I managed to activate port forwarding on my Fritzbox and share it with my PC for Internet access, which also works to some extent. My real problem is that I use Windows, more specifically the NextDNS AIO version. I can easily access the AIO dashboard, but not my own Nextcloud. I use DuckDNS, but it doesn't get detected, and I get network errors all the time. I have assigned port 8080 to AIO, but the Nextcloud itself does not start; only an error message appears. How can I fix the problem with my Fritzbox, my Nextcloud, and my DuckDNS domain? I also use Docker, so I'm really desperate.

​

Problem description

​

"When setting up Nextcloud AIO on an Internet connection with DS-Lite (without public IPv4) using DuckDNS, a critical error occurs during domain validation. Although the FritzBox successfully set up manual port sharing for the ports assigned by the ISP (external 12652 to internal 8443 for HTTPS and 12653 to 80 for HTTP), automated validation within the Nextcloud AIO interface consistently fails. The error message 'Domain cannot be validated' appears because the process rigidly searches for the domain on standard ports 80 and 443 and does not recognize that the instance can be reached via the manually configured custom ports. A key problem here is that although the Nextcloud AIO master container successfully starts via Docker and is accessible via the local IP address of the Windows PC, the actual Nextcloud instance remains functionless because the validation process acts as a 'Blocker' and prevents the initialization of the downstream containers (database, Redis, etc.). Attempting to bypass validation using the environment variables SKIP_DOMAIN_VALIDATION=true and DISABLE_IPV6=true also does not result in a stable installation, as the validation step within the installation process seems imperative to create the cloud services. In addition, error messages regularly occur during the execution of the Docker command, indicating a conflict situation during container designation if the master container is to be restarted after a failed validation attempt."

reddit.com
u/Schnecke_Schneck2007 — 2 days ago
▲ 0 r/docker

Nextcloud, DuckDNS, Fritzbox, Dogger

Hi

​

Ich habe ein Problem mit meiner Nextcloud, da ich mich damit noch nicht so gut auskenne. Ich habe es geschafft, die Portweiterleitung auf meiner Fritzbox zu aktivieren und sie für den Internetzugang mit meinem PC zu teilen, was auch einigermaßen funktioniert. Mein eigentliches Problem ist, dass ich Windows nutze, genauer gesagt die NextDNS AIO-Version. Ich kann problemlos auf das AIO-Dashboard zugreifen, aber nicht auf meine eigene Nextcloud. Ich verwende DuckDNS, aber es wird nicht erkannt und ich erhalte ständig Netzwerkfehler. Ich habe Port 8080 für AIO zugewiesen, aber die Nextcloud selbst startet nicht; es wird nur eine Fehlermeldung angezeigt. Wie kann ich das Problem mit meiner Fritzbox, meiner Nextcloud und meiner DuckDNS-Domain beheben? Ich nutze auch Docker, daher bin ich wirklich verzweifelt.

reddit.com
u/Schnecke_Schneck2007 — 3 days ago
▲ 1 r/nextdns+1 crossposts

Nextcloud DuckDNS Fritzbox Dogger

Hi,

​

I have a problem with my Nextcloud because I'm new to this topic. I've managed to activate port forwarding on my Fritzbox and share it with my PC for internet access, which works reasonably well. My real problem is that I'm using Windows, specifically the NextDNS AIO version. I can easily access the AIO dashboard, but I can't access my own Nextcloud. I use DuckDNS, but it's not recognized and always gives me network errors. I have port 8080 for AIO, but the actual Nextcloud doesn't start; it just shows an error. How do I fix this with my Fritzbox, my Nextcloud, and my DuckDNS domain? I also use Docker, so I'm really desperate.

u/Schnecke_Schneck2007 — 3 days ago
▲ 209 r/nextdns+2 crossposts

Enjoying Spotify Ad-Free with NextDNS

Hallo zusammen, ich möchte euch meine Methode vorstellen, wie man Werbung auf Spotify minimieren kann, indem man gezieltes DNS-Filtering über NextDNS nutzt. Wenn eure DNS-Einstellungen richtig konfiguriert sind, gibt es bei der Nutzung von Spotify einen interessanten Effekt: Die App versucht ständig, im Hintergrund verschiedene Werbe- und Analyse-Server anzusprechen. Da euer DNS-Filter diese Anfragen blockiert, kommt es beim Start kurz zu einem Verbindungsfehler, weil die App die Werbeinhalte nicht laden kann. Das ist das gewünschte Ergebnis der Blockade. Sobald ihr diesen anfänglichen Fehler überwunden habt, startet die App ordnungsgemäß und ihr könnt Musik ohne die üblichen Werbeunterbrechungen abspielen.

Um mit der Einrichtung zu beginnen, loggt euch in euer NextDNS-Dashboard ein und aktiviert im Bereich "Block Lists" verschiedene Filter. Eine solide Grundlage bilden die "NextDNS Ads & Trackers Blocklist" und der "AdGuard DNS Filter", der grundlegende, Social-Media-, Tracking- und Mobile-Werbe-Filter bündelt. Ebenfalls unerlässlich für die gezielte Blockade von Spotify-Werbung ist die Spotify-Werbefilterliste von CHEF-KOCH's HOSTS. Zusätzlich empfehle ich, die Filterlisten "AdGuard Mobile Ads", "Goodbye Ads", "HaGeZi - Multi PRO++", "OISD" und "Steven Black" zu aktivieren, um einen umfassenden Schutz vor Werbung, Tracking, Telemetrie und Malware zu gewährleisten.

Im nächsten Schritt müsst ihr bestimmte Domains auf eure Blacklist setzen, damit die Werbeserver dauerhaft blockiert werden. Fügt bitte folgende Einträge eurer Blacklist hinzu:

  • ***.payments.spotify.com**

  • ***.checkout.spotifycdn.com**

  • ***.api.spotify.com**

  • ***.g2.spotify.com**

  • ***.desktop.spotify.com**

  • ***.ads.spotify.com**

  • .spclient.wg.spotify.com

  • .audio-ak-spotify-com.akamaized.net

  • .audio2.spotify.com

  • .analytics.spotify.com

  • .adstats.spotify.com

  • .adeventtracker.spotify.com

firebaseinstallations.googleapis.com

dealer.g2.spotify.com

gew-dealer.g2.spotify.com

Damit die App trotz dieser strengen Sperren korrekt startet und ihr euch problemlos einloggen könnt, müsst ihr zusätzlich folgende Domain auf eure Whitelist setzen: Wenn eine Domain in NextDNS auf der Whitelist steht, hat dies immer Vorrang vor allen anderen Sicherheitsfunktionen und gewährt automatisch Zugriff auf alle zugehörigen Subdomains:

  • **.login5.spotify.com

gew4-dealer.g2.spotify.com

Wenn Spotify anfangs eine Fehlermeldung anzeigt, ist das ein Zeichen für aktives Filtering. Um das Problem zu beheben, deaktiviere ich kurz den DNS-Server oder den aktiven Schutz, öffne Spotify und logge mich normal ein. Sobald die App erfolgreich gestartet und die Verbindung aufgebaut ist, reaktiviere ich den DNS-Schutz. Nach kurzem Warten, bis die Filter wieder greifen, solltet ihr dann werbefrei Musik streamen können.

Quellen u/Michaeljohn2306

u/Schnecke_Schneck2007 — 8 days ago
▲ 369 r/nextdns+1 crossposts

Spotify Ad Blocking

Hi people, so I've got this alternative for the Mod ad blocking functionality and I just want to share it with you:>>>

I used NextDNS as the Ad blocker and it's been minutes and there were no Ads that have gotten through the Ad blocker while I was listening to Spotify. I hope it works for the other people here:]

NextDNS

*My configurations are in the photo's btw, so feel free to copy them^^.

u/Schnecke_Schneck2007 — 13 days ago

Galaxy Ring Alternative

Unfortunately, I am also affected by the massive battery problem that thousands of you and others have also had. What alternative do you have to the Galaxy Ring? And why? I'm looking for one that is without a subscription model.

reddit.com
u/Schnecke_Schneck2007 — 15 days ago

Galaxy Ring battery drains extremely quickly ("battery block detected") - Known hardware fault?

Hello everyone,

I need your experience with the Galaxy Ring (model SM-Q509). My ring has recently started to cause massive problems: The battery discharges extremely quickly and goes empty almost in time lapse. In addition, he constantly loses his connection. I then ran the official in-app diagnosis, and it throws me the error message "Accurable battery block detected / Action required."

Of course, I contacted Samsung support directly, but the customer service has not been able to help me so far. After the conversation in the chat only went in circles, I was comforted at the end that there were internal system problems and that I should just report back next week. But since the ring still has full guarantee, I don't want to sit out the problem.

So my questions to you are: Have any of you ever had this exact fault where the battery suddenly loses capacity so rapidly? Is this a known hardware failure of the battery cells or could a faulty firmware update be the cause here?

If this is a total loss and I have to send the device in, I am seriously considering looking for alternatives. What smart ring alternatives are there that offer similar features but do best without an expensive monthly subscription model? By the way, I use ring size 9.

Thank you for your help and assessments!

u/Schnecke_Schneck2007 — 15 days ago