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.

3
  • I tried using port 443 and got the same results, but good catch. I have the server certificate and key specified in the virtual host (updated answer with ellipsis for clarification). How would I check what nextcloud.hostname.home.lan resolves to since this is only on the internal network? Thanks!
    – Kyle
    Commented May 4, 2020 at 1:16
  • @Kyle you can ping it (ping nextcloud.hostname.home.lan) from a command prompt / terminal / shell and see what it comes back with.
    – g491
    Commented May 4, 2020 at 3:05
  • I get Name or service not known, likely because I don't have the proper DNS set up on the router as mentioned in the comments to the question. For some reason, none of the guides mention this step.
    – Kyle
    Commented May 4, 2020 at 14:41