Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Oh yea, I wasn't using password. Just obfuscated it so it wasn't posted on a public forum. :) I appreciate your response. I have my server behind a firewall and I port forward everything by having one ipv4 ip. I do have an ipv6 /64 block of addresses I could use. This way, collabora.X.com would point to a different IP. I wouldnt think this would matter much though? I will post my apache config in the original question. Thank you
    – Kyle H
    Commented Jun 29, 2017 at 12:01
  • I think my dns could be an issue here possibly? I have all public services in my network port forwarded through 1 ip address, like above. I use collaboraonline.X.com for a subdomain for the docker image and I now have it in the hosts file to resolve to 127.0.0.1. I believe this is a step in the right direction, and when I get some more time I can retry some of the mods I have done to try and fix it. You sound pretty knowledgeable about nextcloud/collabora, what is your opinion? Thank you again.
    – Kyle H
    Commented Jun 29, 2017 at 13:27
  • In that case, i probably misinterpreted your initial question. Your configs imply you do use the apache forwarding as recommended. IPs dont matter, since you are expected to use a browser which does proper SNI anyway. You can host the two domains on the same IP and let apache figure that out.
    – user475162
    Commented Jun 29, 2017 at 14:40
  • run the docker with -e 'domain=example\.com' (not cert_domain, thats irrelevant if you add a proxy anyway) and post the output of curl https://collaboraonline.example.com from the machine you will be accessing the whole thing from. That should answer the question of whether there is something wrong with your certificate setup.
    – user475162
    Commented Jun 29, 2017 at 14:59
  • thank you for your detailed, helpful post. unfortunately, I do not have it working yet as it is giving me a weird curl error now. stackoverflow.com/questions/44872711/… (if you could please take a look?) :) Nextcloud can see the docker image attached to the port, it denies the connection attempt. however, this post was very helpful in teaching me a bit about the circumstances surrounding the issue and I keep coming back to it in my troubleshooting.
    – Kyle H
    Commented Jul 3, 2017 at 13:23