

This pilot explored the use of two new applications that can be used together to provide federated access to both file management and office document creation and collaborative editing. Office documents are usually created offline. Federated access management has been widely used to control access to published documents, but its use in collaborative creation has usually been limited to wikis and content management systems. * Connection #0 to host left intactīut not when trying to connect to my Collabora container: curl -v are at the heart of most projects: people create and share text, spreadsheets, presentations and images.

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.Second time I changed the cert type from LetsEncrypt wildcard to LetsEncrypt prod.First time it essentially ran a check but didn't change anything because it saw the certs were fine.green lock on all browsers on both and.
