friendica.mbbit.de

Could not acces .well-known/host-meta

Hello @Friendica Support after pulling from dev at 27th November, I receive this message on the admin page, complaining about the system has no access to .well-known/host-meta which indicates a severe misconfiguration. What has changed? :-)
1 1
Roland Häder friendica (via ActivityPub)
@Marek Bachmann I guess you have to check what is written in your eror.log and also friendica.log (if you have it enabled). When I call https://friendica.mbbit.de/.well-known/host-meta I get an empty page which could mean that there is an error in a PHP script.
1
Hypolite Petovan friendica (via ActivityPub)
@Marek Bachmann :friendica: Nothing specific, but this could be an issue with URL rewriting.
1
Roland Häder friendica (via ActivityPub)

@Hypolite Petovan https://friendica.mbbit.de/display/b25b9f4f-1063-829a-e632-d5d599335141 works perfectly fine.


Could not acces .well-known/host-meta


Hello @Friendica Support after pulling from dev at 27th November, I receive this message on the admin page, complaining about the system has no access to .well-known/host-meta which indicates a severe misconfiguration. What has changed? :-)


1
Here is the error from log corresponding to this message:


2022-11-30T17:30:14Z index [ERROR]: Uncaught Exception Error: "Class 'phpseclib3\Crypt\RSA' not found" at /home/friendica/live/src/Protocol/Salmon.php line 248 {"exception":"Error: Class 'phpseclib3\\Crypt\\RSA' not found in /home/friendica/live/src/Protocol/Salmon.php:248
Stack trace:
#0 /home/friendica/live/src/Module/WellKnown/HostMeta.php(96): Friendica\\Protocol\\Salmon::salmonKey()
#1 /home/friendica/live/src/BaseModule.php(238): Friendica\\Module\\WellKnown\\HostMeta->rawContent()\n#2 /home/friendica/live/src/App.php(739): Friendica\\BaseModule->run()
#3 /home/friendica/live/index.php(44): Friendica\\App->runFrontend()
#4 {main}"} - {"file":null,"line":null,"function":null,"uid":"14c663","process_id":568081}
1
Hypolite Petovan friendica (via ActivityPub)
@Marek Bachmann :friendica: Ah, you need to run bin/composer install --no-dev whenever the composer.lock file changes.
1 1
Thx, that fixed it. Nice! Was pulling the last times without worrying about that ;-)
1 1