![]() ![]() Und den entsprechenden Docker Container starten: docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=nextcloud\\.deine-domain\\.tld' -e 'username=Benutzername' -e 'password=Dein-Passwort' -restart always -cap-add MKNOD collabora/code Jetzt wollen wir das ganze ohne Plesk und auf dem gleichen VPS bereitstellen, auf dem auch unsere Nextcloud läuft.Īls erstes müssen wir Docker installieren: sudo apt-get install docker.io * Connection #0 to host left intactīut not when trying to connect to my Collabora container: curl -v meinem ersten Beitrag Collabora Online Office mit Docker in Plesk bereitstellen und an Nextcloud anbinden, habe ich Euch gezeigt, wie man Collabora Online Office in Plesk bereitstellt. Is there a similar internal DNS trick with Unbound I could try? Thanks!Ĭurl from within my Nextcloud container works with external hosts. I do not have access to update any routing settings external to my host server. The Nextcloud container cannot access the host's external IP (loopback issue?), thus it cannot reach the Collabora container by DNS name. Any ideas on what I could try Similar problem here with a new Cloudron installation on a dedicated server with a public IPv4. (I've only been trying to connect 1 instance to Collabora.)Īgain, I appreciate you sticking in there with me on this one. I've got two Nextcloud instances on the same Cloudron.Are there ever cert issues related to new TLDs like the.Green lock still appeared on all my Cloudron sites and Nextcloud still couldn't contact Cloudron server.įind / -iname "*letsencrypt*" returned zero rows Those actions had absolutely no effect on anything. I removed all the gazillion certs that were in /etc/ssl/certs and also deleted all lines in /etc/ssl/certs/ca-certificates.crt in advance of renewing my domain certs in the Cloudron domains admin page. I ran the curl to Collabora after each time that I renewed the certs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |