Skip to main content

No Mastodon connection after update to 2021.07

After the upgrade to 2021.07 using the full zip files, I came across a bug which I could fix with help from annando on github.

After that I do not see any php errors but I also do not get any messages from all my mastodon contacts. Can anyone give me a hint about this?

I'm using nginx as webserver and also nginx as reverse proxy in front of it. PHP is 7.3.

!Friendica Support
You should have some POST to something withinbox, comparable to this one: - - [14/Jul/2021:13:05:55 +0000] "POST /inbox HTTP/1.1" 202 4881 "-" "Friendica 'Siberian Iris' 2021.07-1424"
You said something about using nginx as reverse proxy, haven't you? We had a support case where a reverse proxy had removed the authentication header information. Please have a look at this.
I will have a look later or tomorrow and come back to you, but I updated the last ~6 versions of friendica with this nginx/proxy/php/mysql setup. And as I said with 2021.04 everything was doing fine.
Do you get the "compacting error" all the time? This slightly looks like this issue:

But this was only some glitch and we have a workaround now.
Do you get the "compacting error" all the time?
Yes this messages is all over the place.
This is exactly what I see. Thanks for the link.

Do I understand correctly, that this change is merged into dev but not available in 2021.07?
This is part of the current stable version as well. Possibly your system has no read access to the files "identity-v1.jsonld" and "security-v1.jsonld" in the "static" folder.
This entry was edited (2 months ago)
Access doesn't seam to be the problem:

root@serverpi:/var/www/friendica/static# ll -d
drwxr-xr-x 2 www-data www-data 4096 Jul  4 20:50 .
root@serverpi:/var/www/friendica/static# ll *v1*
-rw-r--r-- 1 www-data www-data 3622 Jul  4 20:50 identity-v1.jsonld
-rw-r--r-- 1 www-data www-data 2059 Jul  4 20:50 security-v1.jsonld

But I think I'll try to switch to dev using git clone anyway. Until now I used the zip files to upgrade.

Also I'm on Raspberry pi OS 32bit (raspi 4) if this information has anything to with it.
A Raspi is fine.
Ok. Got it. The static files could not be accessed with my old nginx config. It is the sample from github but don't ask me how old exactly.

This is the "old" rewrite to front controller (I had a quick look in the history: 3+ years ago) which rewrites access to the folder /static also to the front controller:
  # rewrite to front controller as default rule
  location / {
    if ($is_args != "") {
        rewrite ^/(.*) /index.php?pagename=$uri&$args last;
    rewrite ^/(.*) /index.php?pagename=$uri last;

This is the latest rewrite which tries available files first:
  # rewrite to front controller as default rule
  location / {
    try_files $uri /index.php?pagename=$uri&$args;

Thanks again for your fast help @Michael Vogel.
In the future I need to check the nginx config more frequently.
Could you check whether our sample nginx configuration in our repository is fine?
BTW: a post from my system came through:
2021-07-14T13:07:00Z worker [INFO]: Transmit to returned 202 {"worker_id":"2f27a52","worker_cmd":"APDelivery"} - {"file":"HTTPSignature.php","line":305,"function":"transmit","uid":"7635fd","process_id":3485}

Please check your access log from that timestamp.