Internal Error 500 when searching any User

[oscarsmendez]

Describe the bug I setup an mbin instance using docker and everything is working fine however, when searching for any user inside or outside the instance I receive the Internal error 500.

Edit: I attempted to search on localhost it doesn't spit out an error but instead the search shows up empty. It also doesn't let me login on localhost but I'm assuming that's intentional? I'm hosting it through a cloudflare tunnel so hopefully that's not the issue

In the mbin php console this seems to be where it goes wrong but I'm not too sure:

mbin-php | {"message":"Uncaught PHP Exception TypeError: \"App\Service\ActivityPub\ApHttpClient::getInstancePrivateKey(): Return value must be of type string, null returned\" at ApHttpClient.php line 398","context":{"exception":{"class":"TypeError","message":"App\Service\ActivityPub\ApHttpClient::getInstancePrivateKey(): Return value must be of type string, null returned","code":0,"file":"/var/www/mbin/src/Service/ActivityPub/ApHttpClient.php:398"}},"level":500,"level_name":"CRITICAL","channel":"request","datetime":"2024-06-23T01:58:48.073284+00:00","extra":{}}

On which Mbin instance did you find the bug? falsepanda.social

Which Mbin version was running on the instance? 1.6.0

To Reproduce Steps to reproduce the behavior:

1. Follow the steps in the docker instructions
2. Go to the search icon and enter any user from the fediverse

Expected behavior Searching to be possible

Screenshots

Desktop (please complete the following information):

• OS: MacOS/Docker
• Browser: Arc
• Browser Version: latest

[e-five256]

Try this to see if it helps https://docs.joinmbin.org/admin/FAQ#running-php-binconsole-mbinapkeysupdate-does-not-appear-to-set-keys

[melroy89]

Try to clear Redis.

[oscarsmendez]

I tried clearing redis as well as looking through rabbitmq and it did remind me I set up the docker compose command using just async, "command: 'sh -c "php bin/console messenger:consume async --time-limit=3600"'" as using the default command immediately crashed messenger, perhaps it could be because these other terms are idle then? I can try running it on bare-metal next week to see if I get the same reaction.

[BentiGorlich]

You gotta give us some log entries for us to help you :) Just have a look at the logs while trying to do what you are doing and you should see the error message there

[BentiGorlich]

And the default command is not optional. You have to use that, otherwise federation will not or only partially work

[BentiGorlich]

And the internal server error is not caused by your messengers. They do not interact that way with each other, so the queues are not the problem here. I guess you just didn't run the key generation: docker compose exec php php bin/console mbin:ap:keys:update