Hello macon,

i think it is an good idea to change in the threadname Nextcloud to linuxserver/nextcloud.

nextcloud isn't linuxserver/nextcloud

https://hub.docker.com/_/nextcloud

https://hub.docker.com/r/linuxserver/nextcloud

@Morland

You can try to use Postgres https://hub.docker.com/_/postgres

Zitat von Morlan

This is a complicated issue. Because MariaDB is not officially compiled for arm32 devices the linuxserver image is stuck on 10.1.*. I don't know if that will change. I tried to find an alternative this morning, but I have not found an easy solution .. Maybe someone else has an idea?

Thank you for your investigation.

A missing MariaDB docker version 10.2ff could be a show-stopper if nextcloud v21 will be available for my HW/SW-platform.

The Guide use "image: linuxserver/nextcloud".

Zitat

Nextcloud "image: linuxserver/nextcloud" with Letsencrypt using OMV and docker-compose - Q&A

"image: linuxserver/nextcloud" did have other problems than "image: nextclou/nextcloud"

OMV with Debian isn't the same OMV with Ubuntu.

I mean we can call it right, it simplifies support.

For me it is ok now, i know it now.

Ubuntu is Mint, it still deploys Debian irrespective of either image used.

OMV 4 is OMV 5, it still deploys OMV irrespective of either image used.

For me it is ok now, i know it now.

I want a this time only Nextcloud an no other Container.

Did you have read this:

https://www.duckdns.org/

Zitat

2. Sharing of Personal Data

Except as set forth in this Privacy Statement and as required or permitted by law, we do not share your personal information with third parties without your consent.

Service Providers. Any of the your personal information that we collect may be transferred (or otherwise made available) to our affiliates and other third parties who provide website and administrative/operational support services on our behalf. Personal information may be collected by such providers for their own use, in line with their own privacy practices. You may check the privacy statements of each of these providers to decide whether you are comfortable with their policies.

We use third parties, including Google Analytics and Google Drive, to host and manage our website, to provide analytics, to detect and combat fraud or other illegal activities, and to store data. We have reviewed Google’s privacy policies, specifically for each of these services, and we think that their standards are in-line with our own. However, you should read these privacy policies for yourself and/or contact us with any questions that you may have, to decide for yourself.

Our service providers are given the information they need to perform their designated functions, and except for the reasons stated in this Privacy Statement, are not authorized to use or disclose personal information for other purposes.

Your personal information may be maintained and processed by us, our affiliates and other third-party service providers in the US or other jurisdictions. In the event that personal information is transferred outside of the EU or Canada, to the US or other foreign jurisdiction, it may also be subject to the laws of that jurisdiction and may be disclosed to or accessed by courts, law enforcement and governmental authorities in accordance with those laws.

Third Party Websites. The DuckDNS Website may contain links to other websites that are not owned or controlled by us. We have no control over, do not review and are not responsible for the privacy policies of or content displayed on such other websites. When you click on such a link, you will leave our service and go to another website. During this process, another entity may collect personal information from you.

Legal and Compliance. DuckDNS may share personal information with our affiliates, and with companies, organizations or individuals outside of DuckDNS if we have a good-faith belief that access, use, preservation or disclosure of the information is reasonably necessary or desirable to:

• meet any applicable law, regulation, legal process or enforceable governmental request.
• enforce applicable Terms of Use, including investigation of potential violations.
• detect, prevent or otherwise address malicious, deceptive, fraudulent or illegal activity, abuse as well as security or technical issues and incidents.
• protect against harm to the rights, property or safety of DuckDNS, our users or the public as required or permitted by law.
• operate this website, including requesting contributions.
• provisioning and operating the DuckDNS service.

Other Business Purposes. Personal information may be provided to third parties in connection with a merger or sale (including transfers made as part of insolvency or bankruptcy proceedings) involving all or part of DuckDNS or as part of a reorganization or stock sale or other change in control, including for the purpose of determining whether to proceed or continue with such transaction or business relationship.

Alles anzeigen

I use Nextcloud because i don't like google.

Then you should use your own domain instead of duckdns

hi guys.... does anyone know how to update my letsencrypt Keyboard for duckdns?! I get error message that my cerrificate will expire soon.

Greets

isn't letsencrypt migrated to "swag"

I Use linuxserver/letsencrypt.

Hello macon, did you use this system as production system since Aug. 10th 2019?

Ruschi

https://docs.linuxserver.io/general/swag

Zitat

The certs are valid for 90 days. The container will check the cert expiration status every night and if they are to expire within 30 days, it will attempt to auto-renew. If your certs are about to expire in less than 30 days, check the logs under /config/log/letsencrypt to see why the auto-renewals failed.

We talk here about this GUIDE: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose

So everything gets mixed up

This GUIDE use "image: linuxserver/swag".

KM0201

Where can i get information about the container Letsencrypt/Swag?