bitPickups/friendica_2020-09-1_sharedHosting
1
0
Fork 0
Code Pull requests Activity

Style changes in doc/Install.md

Browse source 
Attempting to generalize the instructions for a broader audience.
This commit is contained in:
miqrogroove 2018-08-26 08:55:47 -04:00 committed by GitHub
parent 879348e7ff
commit 8ee5137ce1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/Install.md
View file

@ -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