From 879348e7ffafc61eee558dd90634dce6d46d6c1c Mon Sep 17 00:00:00 2001 From: miqrogroove Date: Sat, 25 Aug 2018 16:48:50 -0400 Subject: [PATCH 1/2] Update Install.md --- doc/Install.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/Install.md b/doc/Install.md index 79747c083..bd8a0ad74 100644 --- a/doc/Install.md +++ b/doc/Install.md @@ -145,6 +145,16 @@ Example: *Note*: Do **not** rename the .htaccess-dist file as it is tracked by GIT and renaming will cause a dirty working directory. +### Verify the "host-meta" page is working + +Friendica should respond automatically to an important address named /.well-known/host-meta This URL would look like, for example, https://example.com/.well-known/host-meta It must be visible to the public and must respond with an XML file that is automatically customized to your site. + +If that URL is not working, it is possible that some other software is using the /.well-known/ path and is not configured correctly to work with Friendica. Other symptoms may include an error message in the Admin settings that says "host-meta is not reachable on your system. This is a severe configuration issue that prevents communication." Another common error related to host-meta is the, "Invalid profile URL." + +Check for a .well-known directory that did not come with Friendica. Any /.well-known/.htaccess file could interfere with this core requirement. You should remove any RewriteRules from that file, or remove that whole file if appropriate. + +It may be necessary to chmod the /.well-known/.htaccess file if you were not given write permissions by default. + ### Set up the worker Set up a cron job or scheduled task to run the worker once every 5-10 minutes in order to perform background processing. From 8ee5137ce1bb10dc4464b856dce743fd3650396c Mon Sep 17 00:00:00 2001 From: miqrogroove Date: Sun, 26 Aug 2018 08:55:47 -0400 Subject: [PATCH 2/2] Style changes in doc/Install.md Attempting to generalize the instructions for a broader audience. --- doc/Install.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/doc/Install.md b/doc/Install.md index bd8a0ad74..300a9c82d 100644 --- a/doc/Install.md +++ b/doc/Install.md @@ -147,12 +147,19 @@ Example: ### Verify the "host-meta" page is working -Friendica should respond automatically to an important address named /.well-known/host-meta This URL would look like, for example, https://example.com/.well-known/host-meta It must be visible to the public and must respond with an XML file that is automatically customized to your site. +Friendica should respond automatically to important addresses under the /.well-known/ rewrite path. +One critical URL would look like, for example, https://example.com/.well-known/host-meta +It must be visible to the public and must respond with an XML file that is automatically customized to your site. -If that URL is not working, it is possible that some other software is using the /.well-known/ path and is not configured correctly to work with Friendica. Other symptoms may include an error message in the Admin settings that says "host-meta is not reachable on your system. This is a severe configuration issue that prevents communication." Another common error related to host-meta is the, "Invalid profile URL." - -Check for a .well-known directory that did not come with Friendica. Any /.well-known/.htaccess file could interfere with this core requirement. You should remove any RewriteRules from that file, or remove that whole file if appropriate. +If that URL is not working, it is possible that some other software is using the /.well-known/ path. +Other symptoms may include an error message in the Admin settings that says "host-meta is not reachable on your system. +This is a severe configuration issue that prevents server to server communication." +Another common error related to host-meta is the "Invalid profile URL." +Check for a .well-known directory that did not come with Friendica. +The preferred configuration is to remove the directory, however this is not always possible. +If there is any /.well-known/.htaccess file, it could interfere with this Friendica core requirement. +You should remove any RewriteRules from that file, or remove that whole file if appropriate. It may be necessary to chmod the /.well-known/.htaccess file if you were not given write permissions by default. ### Set up the worker